Re: [RFC PATCH v3 08/15] sched/clock, x86: Make __sched_clock_stable forceful

2024-11-21 Thread Peter Zijlstra
On Wed, Nov 20, 2024 at 05:34:32PM +0100, Valentin Schneider wrote: > On 20/11/24 15:59, Peter Zijlstra wrote: > > On Tue, Nov 19, 2024 at 04:34:55PM +0100, Valentin Schneider wrote: > >> Later commits will cause objtool to warn about non __ro_after_init static > >> keys being used in .noinstr sect

Re: [RFC PATCH v3 08/15] sched/clock, x86: Make __sched_clock_stable forceful

2024-11-20 Thread Valentin Schneider
On 20/11/24 15:59, Peter Zijlstra wrote: > On Tue, Nov 19, 2024 at 04:34:55PM +0100, Valentin Schneider wrote: >> Later commits will cause objtool to warn about non __ro_after_init static >> keys being used in .noinstr sections in order to safely defer instruction >> patching IPIs targeted at NOHZ_

Re: [RFC PATCH v3 08/15] sched/clock, x86: Make __sched_clock_stable forceful

2024-11-20 Thread Peter Zijlstra
On Tue, Nov 19, 2024 at 04:34:55PM +0100, Valentin Schneider wrote: > Later commits will cause objtool to warn about non __ro_after_init static > keys being used in .noinstr sections in order to safely defer instruction > patching IPIs targeted at NOHZ_FULL CPUs. > > __sched_clock_stable is used i

[RFC PATCH v3 08/15] sched/clock, x86: Make __sched_clock_stable forceful

2024-11-19 Thread Valentin Schneider
Later commits will cause objtool to warn about non __ro_after_init static keys being used in .noinstr sections in order to safely defer instruction patching IPIs targeted at NOHZ_FULL CPUs. __sched_clock_stable is used in .noinstr code, and can be modified at runtime (e.g. KVM module loading). Sup