[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLV8XYt5JakyqG8FVsTvBnqKHHmFi18ppiTLrwPOhQXO_w@mail.gmail.com>
Date: Fri, 6 Jan 2017 17:06:43 -0800
From: John Stultz <john.stultz@...aro.org>
To: Vitaly Kuznetsov <vkuznets@...hat.com>
Cc: "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
lkml <linux-kernel@...r.kernel.org>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Thomas Gleixner <tglx@...utronix.de>,
Alex Ng <alexng@...rosoft.com>,
Stephen Hemminger <stephen@...workplumber.org>
Subject: Re: [PATCH v2 1/4] timekeeping: export do_adjtimex() to modules
On Wed, Jan 4, 2017 at 9:24 AM, Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
> While do_adjtimex() is available to userspace via adjtimex syscall it is
> not available to modules which may want to implement in-kernel 'NTP
> clients'. Hyper-V hv_utils is going to be the first one.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@...hat.com>
> ---
> kernel/time/timekeeping.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
> index da233cd..ae4f24f 100644
> --- a/kernel/time/timekeeping.c
> +++ b/kernel/time/timekeeping.c
> @@ -2312,6 +2312,7 @@ int do_adjtimex(struct timex *txc)
>
> return ret;
> }
> +EXPORT_SYMBOL_GPL(do_adjtimex);
No real objections to this, although I do want to better understand
the benefits (and drawbacks) of doing the adjtimex in the kernel
driver rather then via userspace, to make sure the need is sane.
thanks
-john
Powered by blists - more mailing lists