All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 213419] Outdated limitation for powerpc in vdso(7)
Date: Sat, 03 Jul 2021 16:50:43 +0000	[thread overview]
Message-ID: <bug-213419-11311-Eyuf2mj5ki@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213419-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=213419

Alejandro Colomar (man-pages) (alx.manpages@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |alx.manpages@gmail.com
         Resolution|---                         |DOCUMENTED

--- Comment #1 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
Hi Christophe,

Thanks for the report.
I applied the following patch.

Thanks,

Alex

---
Author: Alejandro Colomar <alx.manpages@gmail.com>
Date:   Sat Jul 3 18:43:16 2021 +0200

    vdso.7: Remove outdated limitation for powerpc

    Christophe Leroy via Bugzilla:

    [
    https://man7.org/linux/man-pages/man7/vdso.7.html
    (as of today, flagged 2021-03-22)

    ppc/32 and ppc/64 sections both have the following note:

           The CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE clocks
           are not supported by the __kernel_clock_getres and
           __kernel_clock_gettime interfaces; the kernel falls back to
           the real system call

    This note has been wrong from quite some time now,
    since commit 654abc69ef2e
    ("powerpc/vdso32: Add support for CLOCK_{REALTIME/MONOTONIC}_COARSE")
    and commit 5c929885f1bb
    ("powerpc/vdso64: Add support for CLOCK_{REALTIME/MONOTONIC}_COARSE")
    ]

    Reported-by: Christophe Leroy <christophe.leroy@csgroup.eu>
    Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>

diff --git a/man7/vdso.7 b/man7/vdso.7
index ef6bef5bd..1d527c38e 100644
--- a/man7/vdso.7
+++ b/man7/vdso.7
@@ -385,19 +385,6 @@ __kernel_sync_dicache_p5   LINUX_2.6.15
 .in
 .ft P
 \}
-.PP
-The
-.B CLOCK_REALTIME_COARSE
-and
-.B CLOCK_MONOTONIC_COARSE
-clocks are
-.I not
-supported by the
-.I __kernel_clock_getres
-and
-.I __kernel_clock_gettime
-interfaces;
-the kernel falls back to the real system call.
 .SS ppc/64 functions
 .\" See linux/arch/powerpc/kernel/vdso64/vdso64.lds.S
 The table below lists the symbols exported by the vDSO.
@@ -423,19 +410,6 @@ __kernel_sync_dicache_p5   LINUX_2.6.15
 .in
 .ft P
 \}
-.PP
-The
-.B CLOCK_REALTIME_COARSE
-and
-.B CLOCK_MONOTONIC_COARSE
-clocks are
-.I not
-supported by the
-.I __kernel_clock_getres
-and
-.I __kernel_clock_gettime
-interfaces;
-the kernel falls back to the real system call.
 .SS riscv functions
 .\" See linux/arch/riscv/kernel/vdso/vdso.lds.S
 The table below lists the symbols exported by the vDSO.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      reply	other threads:[~2021-07-03 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  6:47 [Bug 213419] New: Outdated limitation for powerpc in vdso(7) bugzilla-daemon
2021-07-03 16:50 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-213419-11311-Eyuf2mj5ki@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.