From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Waiman Long <longman@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
linux-pm@vger.kernel.org, Robin Jarry <rjarry@redhat.com>,
Joe Mario <jmario@redhat.com>
Subject: Re: [PATCH v3 2/3] intel_idle: Sync up the SPEC_CTRL MSR value to x86_spec_ctrl_current
Date: Thu, 22 Jun 2023 11:38:28 +0200 [thread overview]
Message-ID: <20230622093828.GE4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230622054633.ulrurzzvzjijvdhn@treble>
On Wed, Jun 21, 2023 at 10:46:33PM -0700, Josh Poimboeuf wrote:
> On Wed, Jun 21, 2023 at 08:36:02PM -0400, Waiman Long wrote:
> > When intel_idle_ibrs() is called, it modifies the SPEC_CTRL MSR to
> > 0 in order disable IBRS. However, the new MSR value isn't reflected
> > in x86_spec_ctrl_current which is at odd with the other code that
> > keep track of its state in that percpu variable. Fix that by updating
> > x86_spec_ctrl_current percpu value to always match the content of the
> > SPEC_CTRL MSR.
>
> Is this fixing an actual bug or is there some other reason for doing
> this?
>
> >
> > Signed-off-by: Waiman Long <longman@redhat.com>
> > ---
> > drivers/idle/intel_idle.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
> > index aa2d19db2b1d..07fa23707b3c 100644
> > --- a/drivers/idle/intel_idle.c
> > +++ b/drivers/idle/intel_idle.c
> > @@ -181,13 +181,17 @@ static __cpuidle int intel_idle_ibrs(struct cpuidle_device *dev,
> > u64 spec_ctrl = spec_ctrl_current();
> > int ret;
> >
> > - if (smt_active)
> > + if (smt_active) {
> > + __this_cpu_write(x86_spec_ctrl_current, 0);
> > native_wrmsrl(MSR_IA32_SPEC_CTRL, 0);
> > + }
> >
> > ret = __intel_idle(dev, drv, index);
> >
> > - if (smt_active)
> > + if (smt_active) {
> > native_wrmsrl(MSR_IA32_SPEC_CTRL, spec_ctrl);
> > + __this_cpu_write(x86_spec_ctrl_current, spec_ctrl);
> > + }
>
> More candidates for update_spec_ctrl()?
Both this and the play_dead case can't use update_spec_ctrl() because
RCU isn't there anymore and all that is noinstr. Additionally, both
sites rely on preemption being off already, where update_spec_ctrl()
can't do that.
That said, I suppose one could write it like so:
static __always_inline __update_spec_ctrl(u64 val)
{
__this_cpu_write(x86_spec_ctrl_current, val);
native_wrmsrl(MSR_IA32_SPEC_CTRL, val);
}
static void update_spec_ctrl(u64 val)
{
preempt_disable();
__update_spec_ctrl(val);
preempt_enable();
}
And then you can use __update_spec_ctrl(). But that would need a wee
audit of using native_wrmsrl() in all places, probably ok, IIRC Xen
wasn't using our IBRS stuff anyway.
next prev parent reply other threads:[~2023-06-22 9:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 0:36 [PATCH v3 0/3] x86/speculation: Disable IBRS when idle Waiman Long
2023-06-22 0:36 ` [PATCH v3 1/3] x86/idle: Disable IBRS when cpu is offline Waiman Long
2023-06-22 2:05 ` Randy Dunlap
2023-06-22 2:13 ` Waiman Long
2023-06-22 5:40 ` Josh Poimboeuf
2023-06-22 12:27 ` Waiman Long
2023-06-22 0:36 ` [PATCH v3 2/3] intel_idle: Sync up the SPEC_CTRL MSR value to x86_spec_ctrl_current Waiman Long
2023-06-22 5:46 ` Josh Poimboeuf
2023-06-22 9:38 ` Peter Zijlstra [this message]
2023-06-22 12:43 ` Waiman Long
2023-06-22 13:08 ` Peter Zijlstra
2023-06-22 9:40 ` Peter Zijlstra
2023-06-22 12:34 ` Waiman Long
2023-06-22 12:31 ` Waiman Long
2023-06-22 0:36 ` [PATCH v3 3/3] intel_idle: Add ibrs_off module parameter to force disable IBRS Waiman Long
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=20230622093828.GE4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jmario@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=rjarry@redhat.com \
--cc=tglx@linutronix.de \
--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