mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Li,Rongqing" <lirongqing@baidu.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
	"bp@alien8.de" <bp@alien8.de>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"jpoimboe@kernel.org" <jpoimboe@kernel.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"david.kaplan@amd.com" <david.kaplan@amd.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: [????] Re: [PATCH] x86/bugs: Fix GDS mitigation check for CPUs without ARCH_CAP_GDS_CTRL
Date: Sat, 16 Aug 2025 00:15:20 +0000	[thread overview]
Message-ID: <2a53cf1c48b44ea4b12debeed7521d50@baidu.com> (raw)


> 
> How is that a problem? That is how it was originally implemented.
> 
> Infact, the following checks are required for the correct behavior:


You are right, I will resend this patch

Thanks

-Li

> 
>          if (mcu_ctrl & GDS_MITG_LOCKED) {
>                  if (gds_mitigation == GDS_MITIGATION_OFF)
>                          pr_warn("Mitigation locked. Disable failed.\n");
> 	...
>                  gds_mitigation = GDS_MITIGATION_FULL_LOCKED;
>          }
> 
> If the GDS microcode mitigation is locked before the kernel boot, MSR write for
> OFF will not take effect anyways. And you report OFF when the mitigation is
> locked to ON. While also triggering below WARN_ON_ONCE():
> 
> update_gds_msr()
> {
> ...
>          /*
>           * Check to make sure that the WRMSR value was not ignored.
> Writes to
>           * GDS_MITG_DIS will be ignored if this processor is locked but the
> boot
>           * processor was not.
>           */
>          rdmsrq(MSR_IA32_MCU_OPT_CTRL, mcu_ctrl_after);
>          WARN_ON_ONCE(mcu_ctrl != mcu_ctrl_after);

                 reply	other threads:[~2025-08-16  0:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2a53cf1c48b44ea4b12debeed7521d50@baidu.com \
    --to=lirongqing@baidu.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=david.kaplan@amd.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --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

all inboxes | Powered by JetHome®