public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Santosh Sivaraj <santosh-b8Fn+pY0OfAdnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Michael Ellerman <mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
Subject: Re: [PATCH] vdso.7: __kernel_clock_gettime *_COARSE clock support in PPC64
Date: Fri, 22 Dec 2017 10:36:53 +0100	[thread overview]
Message-ID: <31d5abc7-d314-d4da-175f-b402e14678f0@gmail.com> (raw)
In-Reply-To: <20171222002659.1930-1-santosh-b8Fn+pY0OfAdnm+yROfE0A@public.gmane.org>

Hi Santosh

On 12/22/2017 01:26 AM, Santosh Sivaraj wrote:
> *_COARSE clocks are now supported in the __kernel_clock_gettime interface in
> PPC64. No longer falls back to the real system call.

Can you tell me the kernel version where this change was 
made? It would be useful to include that in the text, I think.
In fact, if you knew the kernel commit that made the change,
that would also be of interest.

Also, your patch changes just the entry for ppc/64. Does
the same statement hold true for ppc/32?

Thanks,

Michael


> CC: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> CC: Michael Ellerman <mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
> Signed-off-by: Santosh Sivaraj <santosh-b8Fn+pY0OfAdnm+yROfE0A@public.gmane.org>
> ---
>  man7/vdso.7 | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/man7/vdso.7 b/man7/vdso.7
> index 9af02a8aa..c7399939c 100644
> --- a/man7/vdso.7
> +++ b/man7/vdso.7
> @@ -438,9 +438,7 @@ clocks are
>  .I not
>  supported by the
>  .I __kernel_clock_getres
> -and
> -.I __kernel_clock_gettime
> -interfaces;
> +interface;
>  the kernel falls back to the real system call.
>  .SS s390 functions
>  .\" See linux/arch/s390/kernel/vdso32/vdso32.lds.S
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-12-22  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22  0:26 [PATCH] vdso.7: __kernel_clock_gettime *_COARSE clock support in PPC64 Santosh Sivaraj
     [not found] ` <20171222002659.1930-1-santosh-b8Fn+pY0OfAdnm+yROfE0A@public.gmane.org>
2017-12-22  9:36   ` Michael Kerrisk (man-pages) [this message]
     [not found]     ` <31d5abc7-d314-d4da-175f-b402e14678f0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-12-23  3:13       ` Santosh Sivaraj
     [not found]         ` <20171223031312.k5x4hbytlm7wwfzn-lCJRWkM8CScA+286u2LMdEEOCMrvLtNR@public.gmane.org>
2017-12-30  8:47           ` Michael Kerrisk (man-pages)
     [not found]             ` <afd1b494-57f2-8e83-a0e5-f8b1a304f9c0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-02-05  6:22               ` Santosh Sivaraj

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=31d5abc7-d314-d4da-175f-b402e14678f0@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org \
    --cc=santosh-b8Fn+pY0OfAdnm+yROfE0A@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox