[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.20.1609151426420.14769@knanqh.ubzr>
Date: Thu, 15 Sep 2016 14:28:40 -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:
> > diff --git a/kernel/time/Kconfig b/kernel/time/Kconfig
> > index 62824f2fe4..62504a2c9f 100644
> > --- a/kernel/time/Kconfig
> > +++ b/kernel/time/Kconfig
> > @@ -195,3 +195,21 @@ config HIGH_RES_TIMERS
> >
> > endmenu
> > endif
> > +
> > +config POSIX_TIMERS
> > + bool "Posix Clocks & timers" if EMBEDDED
> > + default y
> > + help
> > + This includes native support for POSIX timers to the kernel.
> > + Most embedded systems may have no use for them and therefore they
> > + can be configured out to reduce the size of the kernel image.
> > +
> > + When this option is disabled, the following syscalls won't be
> > + available: timer_create, timer_gettime: timer_getoverrun,
> > + timer_settime, timer_delete, clock_adjtime. Furthermore, the
> > + clock_settime, clock_gettime, clock_getres and clock_nanosleep
> > + syscalls will be limited to CLOCK_REALTIME and CLOCK_MONOTONIC
> > + only.
> > +
> > + If unsure say y.
> >
>
> One thought.. Should this go under:
> Configure standard kernel features (expert users)
> rather then a top level item under General Setup ?
Hmmm... probably yes.
Do you need that I repost the patch?
Nicolas
Powered by blists - more mailing lists