Hi Peter, On Mon, Jan 23, 2023 at 09:50:09PM +0100, Peter Zijlstra wrote: > 0-day robot reported graph-tracing made the cpuidle-vs-rcu rework go splat. Do you have a link toe the splat somewhere? I'm assuming that this is partially generic, and I'd like to make sure I test the right thing on arm64. I'll throw my usual lockdep options at the ftrace selftests... Thanks, Mark. > > These patches appear to cure this, the ftrace selftest now runs to completion > without spamming scary messages to dmesg. > > --- > arch/x86/include/asm/atomic64_32.h | 44 +++++++++++++++++++------------------- > arch/x86/include/asm/atomic64_64.h | 36 +++++++++++++++---------------- > arch/x86/include/asm/kvmclock.h | 2 +- > arch/x86/include/asm/paravirt.h | 2 +- > arch/x86/include/asm/pvclock.h | 3 ++- > arch/x86/kernel/cpu/vmware.c | 2 +- > arch/x86/kernel/ftrace.c | 3 +++ > arch/x86/kernel/kvmclock.c | 6 +++--- > arch/x86/kernel/pvclock.c | 22 +++++++++++++------ > arch/x86/kernel/tsc.c | 7 +++--- > arch/x86/xen/time.c | 12 +++++++++-- > drivers/cpuidle/cpuidle.c | 2 +- > drivers/cpuidle/poll_state.c | 2 -- > include/linux/math64.h | 4 ++-- > include/linux/sched/clock.h | 8 +++---- > kernel/sched/clock.c | 27 +++++++++++++++++------ > 16 files changed, 107 insertions(+), 75 deletions(-) > >
