From: Marco Elver <elver@google.com> To: Valentin Schneider <valentin.schneider@arm.com> Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linuxppc-dev@lists.ozlabs.org, linux-kbuild@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>, Frederic Weisbecker <frederic@kernel.org>, Mike Galbraith <efault@gmx.de>, Dmitry Vyukov <dvyukov@google.com>, Michael Ellerman <mpe@ellerman.id.au>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Paul Mackerras <paulus@samba.org>, Steven Rostedt <rostedt@goodmis.org>, Masahiro Yamada <masahiroy@kernel.org>, Michal Marek <michal.lkml@markovi.net>, Nick Desaulniers <ndesaulniers@google.com> Subject: Re: [PATCH v2 2/5] preempt/dynamic: Introduce preempt mode accessors Date: Thu, 11 Nov 2021 09:54:05 +0100 [thread overview] Message-ID: <YYzaLTtf1tFbqDSn@elver.google.com> (raw) In-Reply-To: <20211110202448.4054153-3-valentin.schneider@arm.com> On Wed, Nov 10, 2021 at 08:24PM +0000, Valentin Schneider wrote: [...] > +#ifdef CONFIG_PREEMPT_DYNAMIC > + > +extern bool is_preempt_none(void); > +extern bool is_preempt_voluntary(void); > +extern bool is_preempt_full(void); > + > +#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) > + > +#endif > + > +#define is_preempt_rt() IS_ENABLED(CONFIG_PREEMPT_RT) > + Can these callables be real functions in all configs, making the !DYNAMIC ones just static inline bool ones? That'd catch invalid use in #if etc. in all configs. > /* > * 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); \ > + return preempt_dynamic_mode == preempt_dynamic_##mode; \ > + } This needs an EXPORT_SYMBOL, so it's usable from modules like the kcsan_test module.
WARNING: multiple messages have this Message-ID (diff)
From: Marco Elver <elver@google.com> To: Valentin Schneider <valentin.schneider@arm.com> Cc: Michal Marek <michal.lkml@markovi.net>, linux-kbuild@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>, Frederic Weisbecker <frederic@kernel.org>, Mike Galbraith <efault@gmx.de>, Nick Desaulniers <ndesaulniers@google.com>, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, Paul Mackerras <paulus@samba.org>, Steven Rostedt <rostedt@goodmis.org>, Masahiro Yamada <masahiroy@kernel.org>, linuxppc-dev@lists.ozlabs.org, Ingo Molnar <mingo@kernel.org>, Dmitry Vyukov <dvyukov@google.com> Subject: Re: [PATCH v2 2/5] preempt/dynamic: Introduce preempt mode accessors Date: Thu, 11 Nov 2021 09:54:05 +0100 [thread overview] Message-ID: <YYzaLTtf1tFbqDSn@elver.google.com> (raw) In-Reply-To: <20211110202448.4054153-3-valentin.schneider@arm.com> On Wed, Nov 10, 2021 at 08:24PM +0000, Valentin Schneider wrote: [...] > +#ifdef CONFIG_PREEMPT_DYNAMIC > + > +extern bool is_preempt_none(void); > +extern bool is_preempt_voluntary(void); > +extern bool is_preempt_full(void); > + > +#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) > + > +#endif > + > +#define is_preempt_rt() IS_ENABLED(CONFIG_PREEMPT_RT) > + Can these callables be real functions in all configs, making the !DYNAMIC ones just static inline bool ones? That'd catch invalid use in #if etc. in all configs. > /* > * 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); \ > + return preempt_dynamic_mode == preempt_dynamic_##mode; \ > + } This needs an EXPORT_SYMBOL, so it's usable from modules like the kcsan_test module.
next prev parent reply other threads:[~2021-11-11 8:54 UTC|newest] Thread overview: 55+ 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 ` Valentin Schneider 2021-11-10 20:24 ` [PATCH v2 1/5] preempt: Restore preemption model selection configs Valentin Schneider 2021-11-10 20:24 ` Valentin Schneider 2021-11-11 8:58 ` Marco Elver 2021-11-11 8:58 ` Marco Elver 2021-11-11 12:22 ` [tip: sched/urgent] " tip-bot2 for Valentin Schneider 2021-11-10 20:24 ` [PATCH v2 2/5] preempt/dynamic: Introduce preempt mode accessors Valentin Schneider 2021-11-10 20:24 ` Valentin Schneider 2021-11-11 3:16 ` Mike Galbraith 2021-11-11 3:16 ` Mike Galbraith 2021-11-11 3:35 ` Mike Galbraith 2021-11-11 3:35 ` Mike Galbraith 2021-11-11 3:47 ` Mike Galbraith 2021-11-11 3:47 ` Mike Galbraith 2021-11-11 3:55 ` Mike Galbraith 2021-11-11 3:55 ` Mike Galbraith 2021-11-11 9:36 ` Marco Elver 2021-11-11 9:36 ` Marco Elver 2021-11-11 10:32 ` Mike Galbraith 2021-11-11 10:32 ` Mike Galbraith 2021-11-11 10:56 ` Valentin Schneider 2021-11-11 10:56 ` Valentin Schneider 2021-11-11 11:09 ` Mike Galbraith 2021-11-11 11:09 ` Mike Galbraith 2021-11-11 8:54 ` Marco Elver [this message] 2021-11-11 8:54 ` Marco Elver 2021-11-11 10:56 ` Valentin Schneider 2021-11-11 10:56 ` Valentin Schneider 2021-11-16 13:29 ` Christophe Leroy 2021-11-16 13:29 ` Christophe Leroy 2021-11-22 16:37 ` Valentin Schneider 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-10 20:24 ` Valentin Schneider 2021-11-11 4:55 ` Michael Ellerman 2021-11-11 4:55 ` Michael Ellerman 2021-11-15 15:29 ` Valentin Schneider 2021-11-15 15:29 ` Valentin Schneider 2021-11-16 13:41 ` Christophe Leroy 2021-11-16 13:41 ` Christophe Leroy 2021-11-22 16:44 ` Valentin Schneider 2021-11-22 16:44 ` Valentin Schneider 2021-11-10 20:24 ` [PATCH v2 4/5] kscan: " Valentin Schneider 2021-11-10 20:24 ` Valentin Schneider 2021-11-11 9:11 ` Marco Elver 2021-11-11 9:11 ` Marco Elver 2021-11-11 9:39 ` Marco Elver 2021-11-11 9:39 ` Marco Elver 2021-11-11 10:57 ` Valentin Schneider 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:24 ` Valentin Schneider 2021-11-10 20:36 ` Steven Rostedt 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=YYzaLTtf1tFbqDSn@elver.google.com \ --to=elver@google.com \ --cc=benh@kernel.crashing.org \ --cc=dvyukov@google.com \ --cc=efault@gmx.de \ --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=mpe@ellerman.id.au \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.