[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.20.1609151355290.14769@knanqh.ubzr>
Date: Thu, 15 Sep 2016 13:56:23 -0400 (EDT)
From: Nicolas Pitre <nicolas.pitre@...aro.org>
To: John Stultz <john.stultz@...aro.org>
cc: Thomas Gleixner <tglx@...utronix.de>,
Josh Triplett <josh@...htriplett.org>,
Richard Cochran <richardcochran@...il.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3) posix-timers: make it configurable
On Thu, 15 Sep 2016, John Stultz wrote:
> On Wed, Sep 14, 2016 at 8:47 PM, Nicolas Pitre <nicolas.pitre@...aro.org> wrote:
> > Many embedded systems typically don't need them. This removes about
> > 22KB from the kernel binary size on ARM 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.
> >
> > 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.
>
> Thanks for re-sending. I'm happier that you're keeping some basic
> functionality here. No real objections at this point.
>
> I need to apply it for testing and take a closer look, but its on my
> to-queue list. However, with an upcoming conference, as being a little
> later in the cycle I can't promise it will make it for the 4.9 merge
> window. But we'll see.
Thanks. I'll buy you a beer in 2 weeks. :-)
Nicolas
Powered by blists - more mailing lists