From: Mark Rutland <mark.rutland@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: juri.lelli@redhat.com, daniel.lezcano@linaro.org,
wanpengli@tencent.com, kvm@vger.kernel.org, rafael@kernel.org,
pv-drivers@vmware.com, dave.hansen@linux.intel.com,
virtualization@lists.linux-foundation.org, bsegall@google.com,
amakhalov@vmware.com, will@kernel.org, vschneid@redhat.com,
hpa@zytor.com, x86@kernel.org, mingo@kernel.org, mgorman@suse.de,
linux-trace-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
boqun.feng@gmail.com, rostedt@goodmis.org, bp@alien8.de,
vincent.guittot@linaro.org, boris.ostrovsky@oracle.com,
dietmar.eggemann@arm.com, jgross@suse.com, seanjc@google.com,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mhiramat@kernel.org, pbonzini@redhat.com, bristot@redhat.com
Subject: Re: [PATCH 0/6] A few cpuidle vs rcu fixes
Date: Tue, 24 Jan 2023 16:34:23 +0000 [thread overview]
Message-ID: <Y9AIj1s5iPPki3dK@FVFF77S0Q05N> (raw)
In-Reply-To: <20230123205009.790550642@infradead.org>
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(-)
>
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-01-24 16:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 20:50 [PATCH 0/6] A few cpuidle vs rcu fixes Peter Zijlstra
2023-01-23 20:50 ` [PATCH 1/6] x86: Always inline arch_atomic64 Peter Zijlstra
2023-01-23 20:50 ` [PATCH 2/6] x86/pvclock: improve atomic update of last_value in pvclock_clocksource_read Peter Zijlstra
2023-01-23 20:50 ` [PATCH 3/6] ftrace/x86: Warn and ignore graph tracing when RCU is disabled Peter Zijlstra
2023-01-23 21:53 ` Steven Rostedt
2023-01-23 22:07 ` Steven Rostedt
2023-01-24 14:44 ` Peter Zijlstra
2023-01-24 17:12 ` Mark Rutland
2023-01-25 9:37 ` Peter Zijlstra
2023-01-25 10:47 ` Peter Zijlstra
2023-01-25 11:32 ` Mark Rutland
[not found] ` <20230125184658.GL2948950@paulmck-ThinkPad-P17-Gen-1>
2023-01-26 9:28 ` Peter Zijlstra
2023-01-23 20:50 ` [PATCH 4/6] x86: Mark sched_clock() noinstr Peter Zijlstra
2023-01-23 20:50 ` [PATCH 5/6] sched/clock: Make local_clock() noinstr Peter Zijlstra
2023-01-23 20:50 ` [PATCH 6/6] cpuidle: Fix poll_idle() noinstr annotation Peter Zijlstra
2023-01-24 14:24 ` Rafael J. Wysocki
2023-01-24 16:34 ` Mark Rutland [this message]
2023-01-24 17:30 ` [PATCH 0/6] A few cpuidle vs rcu fixes Mark Rutland
2023-01-24 18:39 ` Mark Rutland
2023-01-25 9:35 ` Peter Zijlstra
2023-01-25 9:40 ` Peter Zijlstra
2023-01-25 10:23 ` Mark Rutland
2023-01-25 9:31 ` Peter Zijlstra
2023-01-25 9:36 ` Mark Rutland
2023-01-25 15:20 ` Mark Rutland
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=Y9AIj1s5iPPki3dK@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=amakhalov@vmware.com \
--cc=boqun.feng@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=juri.lelli@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=pv-drivers@vmware.com \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=vschneid@redhat.com \
--cc=wanpengli@tencent.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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