From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Valentin Schneider <valentin.schneider@arm.com>,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
linuxppc-dev@lists.ozlabs.org, linux-kbuild@vger.kernel.org
Cc: Marco Elver <elver@google.com>,
Michal Marek <michal.lkml@markovi.net>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <frederic@kernel.org>,
Mike Galbraith <efault@gmx.de>,
Nick Desaulniers <ndesaulniers@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH v2 2/5] preempt/dynamic: Introduce preempt mode accessors
Date: Tue, 16 Nov 2021 14:29:51 +0100 [thread overview]
Message-ID: <2f22c57d-9bf0-3cc1-f0f1-61ecdf5dfa52@csgroup.eu> (raw)
In-Reply-To: <20211110202448.4054153-3-valentin.schneider@arm.com>
Le 10/11/2021 à 21:24, Valentin Schneider a écrit :
> CONFIG_PREEMPT{_NONE, _VOLUNTARY} designate either:
> o The build-time preemption model when !PREEMPT_DYNAMIC
> o The default boot-time preemption model when PREEMPT_DYNAMIC
>
> IOW, using those on PREEMPT_DYNAMIC kernels is meaningless - the actual
> model could have been set to something else by the "preempt=foo" cmdline
> parameter.
>
> Introduce a set of helpers to determine the actual preemption mode used by
> the live kernel.
>
> Suggested-by: Marco Elver <elver@google.com>
> Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
> ---
> include/linux/sched.h | 16 ++++++++++++++++
> kernel/sched/core.c | 11 +++++++++++
> 2 files changed, 27 insertions(+)
>
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 5f8db54226af..0640d5622496 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -2073,6 +2073,22 @@ static inline void cond_resched_rcu(void)
> #endif
> }
>
> +#ifdef CONFIG_PREEMPT_DYNAMIC
> +
> +extern bool is_preempt_none(void);
> +extern bool is_preempt_voluntary(void);
> +extern bool is_preempt_full(void);
Those are trivial tests supposed to be used in fast pathes. They should
be static inlines in order to minimise the overhead.
> +
> +#else
> +
> +#define is_preempt_none() IS_ENABLED(CONFIG_PREEMPT_NONE)
> +#define is_preempt_voluntary() IS_ENABLED(CONFIG_PREEMPT_VOLUNTARY)
> +#define is_preempt_full() IS_ENABLED(CONFIG_PREEMPT)
Would be better to use static inlines here as well instead of macros.
> +
> +#endif
> +
> +#define is_preempt_rt() IS_ENABLED(CONFIG_PREEMPT_RT)
> +
> /*
> * Does a critical section need to be broken due to another
> * task waiting?: (technically does not depend on CONFIG_PREEMPTION,
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 97047aa7b6c2..9db7f77e53c3 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -6638,6 +6638,17 @@ static void __init preempt_dynamic_init(void)
> }
> }
>
> +#define PREEMPT_MODE_ACCESSOR(mode) \
> + bool is_preempt_##mode(void) \
> + { \
> + WARN_ON_ONCE(preempt_dynamic_mode == preempt_dynamic_undefined); \
Not sure using WARN_ON is a good idea here, as it may be called very
early, see comment on powerpc patch.
> + return preempt_dynamic_mode == preempt_dynamic_##mode; \
> + }
I'm not sure that's worth a macro. You only have 3 accessors, 2 lines of
code each. Just define all 3 in plain text.
CONFIG_PREEMPT_DYNAMIC is based on using strategies like static_calls in
order to minimise the overhead. For those accessors you should use the
same kind of approach and use things like jump_labels in order to not
redo the test at each time and minimise overhead as much as possible.
> +
> +PREEMPT_MODE_ACCESSOR(none)
> +PREEMPT_MODE_ACCESSOR(voluntary)
> +PREEMPT_MODE_ACCESSOR(full)
> +
> #else /* !CONFIG_PREEMPT_DYNAMIC */
>
> static inline void preempt_dynamic_init(void) { }
>
next prev parent reply other threads:[~2021-11-16 13:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:24 [PATCH v2 0/5] preempt: PREEMPT vs PREEMPT_DYNAMIC configs fixup Valentin Schneider
2021-11-10 20:24 ` [PATCH v2 1/5] preempt: Restore preemption model selection configs Valentin Schneider
2021-11-11 8:58 ` Marco Elver
2021-11-10 20:24 ` [PATCH v2 2/5] preempt/dynamic: Introduce preempt mode accessors Valentin Schneider
2021-11-11 3:16 ` Mike Galbraith
2021-11-11 3:35 ` Mike Galbraith
2021-11-11 3:47 ` Mike Galbraith
2021-11-11 3:55 ` Mike Galbraith
2021-11-11 9:36 ` Marco Elver
2021-11-11 10:32 ` Mike Galbraith
2021-11-11 10:56 ` Valentin Schneider
2021-11-11 11:09 ` Mike Galbraith
2021-11-11 8:54 ` Marco Elver
2021-11-11 10:56 ` Valentin Schneider
2021-11-16 13:29 ` Christophe Leroy [this message]
2021-11-22 16:37 ` Valentin Schneider
2021-11-10 20:24 ` [PATCH v2 3/5] powerpc: Use preemption model accessors Valentin Schneider
2021-11-11 4:55 ` Michael Ellerman
2021-11-15 15:29 ` Valentin Schneider
2021-11-16 13:41 ` Christophe Leroy
2021-11-22 16:44 ` Valentin Schneider
2021-11-10 20:24 ` [PATCH v2 4/5] kscan: " Valentin Schneider
2021-11-11 9:11 ` Marco Elver
2021-11-11 9:39 ` Marco Elver
2021-11-11 10:57 ` Valentin Schneider
2021-11-10 20:24 ` [PATCH v2 5/5] ftrace: Use preemption model accessors for trace header printout Valentin Schneider
2021-11-10 20:36 ` Steven Rostedt
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=2f22c57d-9bf0-3cc1-f0f1-61ecdf5dfa52@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=dvyukov@google.com \
--cc=efault@gmx.de \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=valentin.schneider@arm.com \
/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).