From: John Stultz <john.stultz@linaro.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Josh Triplett <josh@joshtriplett.org>,
Richard Cochran <richardcochran@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3) posix-timers: make it configurable
Date: Thu, 15 Sep 2016 11:13:20 -0700 [thread overview]
Message-ID: <CALAqxLVfu3+-9Ucu4zvaeWXW3kpBeVZFhy831v31gmRFMBOCpw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1609142340540.14769@knanqh.ubzr>
> 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 ?
thanks
-john
next prev parent reply other threads:[~2016-09-15 18:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 3:47 [PATCH v3) posix-timers: make it configurable Nicolas Pitre
2016-09-15 17:48 ` John Stultz
2016-09-15 17:56 ` Nicolas Pitre
2016-09-15 18:13 ` John Stultz [this message]
2016-09-15 18:28 ` Nicolas Pitre
2016-09-15 18:35 ` John Stultz
2016-09-15 18:37 ` Nicolas Pitre
2016-09-15 18:46 ` John Stultz
2016-09-15 19:31 ` Nicolas Pitre
2016-09-15 19:58 ` John Stultz
2016-09-15 21:07 ` Richard Cochran
2016-09-15 21:15 ` Josh Triplett
2016-09-15 21:35 ` Nicolas Pitre
2016-09-15 21:56 ` Josh Triplett
2016-09-16 7:24 ` Richard Cochran
2016-09-17 2:57 ` Nicolas Pitre
2016-09-18 14:35 ` Richard Cochran
2016-09-18 16:54 ` Nicolas Pitre
2016-09-18 18:20 ` Richard Cochran
2016-09-18 18:49 ` Nicolas Pitre
2016-09-18 20:22 ` Richard Cochran
2016-09-18 20:30 ` Nicolas Pitre
2016-09-18 21:11 ` Richard Cochran
2016-09-15 21:23 ` Richard Cochran
2016-09-16 14:31 ` kbuild test robot
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=CALAqxLVfu3+-9Ucu4zvaeWXW3kpBeVZFhy831v31gmRFMBOCpw@mail.gmail.com \
--to=john.stultz@linaro.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).