[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230123205009.790550642@infradead.org>
Date: Mon, 23 Jan 2023 21:50:09 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: mingo@...nel.org
Cc: will@...nel.org, peterz@...radead.org, boqun.feng@...il.com,
mark.rutland@....com, tglx@...utronix.de, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
seanjc@...gle.com, pbonzini@...hat.com, jgross@...e.com,
srivatsa@...il.mit.edu, amakhalov@...are.com,
pv-drivers@...are.com, rostedt@...dmis.org, mhiramat@...nel.org,
wanpengli@...cent.com, vkuznets@...hat.com,
boris.ostrovsky@...cle.com, rafael@...nel.org,
daniel.lezcano@...aro.org, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
bsegall@...gle.com, mgorman@...e.de, bristot@...hat.com,
vschneid@...hat.com, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
linux-trace-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: [PATCH 0/6] A few cpuidle vs rcu fixes
0-day robot reported graph-tracing made the cpuidle-vs-rcu rework go splat.
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(-)
Powered by blists - more mailing lists