[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLW2KE8FwTzPJDhTA3x1gKTfoaCH5Vw=ZPr8tp3Y1VsD4A@mail.gmail.com>
Date: Tue, 15 Nov 2016 16:48:17 -0800
From: John Stultz <john.stultz@...aro.org>
To: Nicolas Pitre <nicolas.pitre@...aro.org>
Cc: Michal Marek <mmarek@...e.com>,
Richard Cochran <richardcochran@...il.com>,
Paul Bolle <pebolle@...cali.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Josh Triplett <josh@...htriplett.org>,
Edward Cree <ecree@...arflare.com>, netdev@...r.kernel.org,
linux-kbuild@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 6/6] posix-timers: make it configurable
On Thu, Nov 10, 2016 at 9:10 PM, Nicolas Pitre <nicolas.pitre@...aro.org> wrote:
> Some embedded systems have no use for them. This removes about
> 25KB from the kernel binary size when configured out.
>
> Corresponding syscalls are routed to a stub logging the attempt to
> use those syscalls which should be enough of a clue if they were
> disabled without proper consideration. They are: timer_create,
> timer_gettime: timer_getoverrun, timer_settime, timer_delete,
> clock_adjtime, setitimer, getitimer, alarm.
>
> The clock_settime, clock_gettime, clock_getres and clock_nanosleep
> syscalls are replaced by simple wrappers compatible with CLOCK_REALTIME,
> CLOCK_MONOTONIC and CLOCK_BOOTTIME only which should cover the vast
> majority of use cases with very little code.
>
> Signed-off-by: Nicolas Pitre <nico@...aro.org>
> Reviewed-by: Josh Triplett <josh@...htriplett.org>
> Acked-by: Richard Cochran <richardcochran@...il.com>
> Acked-by: Thomas Gleixner <tglx@...utronix.de>
Ok.. ran the series through the kselftest/timers series and the results look ok.
Acked-by: John Stultz <john.stultz@...aro.org>
thanks
-john
Powered by blists - more mailing lists