From: Xin Li <xin@zytor.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Dave Hansen <dave.hansen@intel.com>,
linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org,
andrew.cooper3@citrix.com
Subject: Re: [PATCH v1 1/1] x86/fred: Fix the FRED RSP0 MSR out of sync with its per CPU cache
Date: Thu, 9 Jan 2025 10:48:32 -0800 [thread overview]
Message-ID: <a132c883-8399-4936-9f28-0fc28db22641@zytor.com> (raw)
In-Reply-To: <1D01F3E8-BEFF-4938-B538-C3657AA31742@zytor.com>
On 1/9/2025 1:46 AM, H. Peter Anvin wrote:
> On January 8, 2025 12:14:18 PM PST, Dave Hansen <dave.hansen@intel.com> wrote:
>> On 1/7/25 18:36, Xin Li (Intel) wrote:
>>> + * Another option is to leave the FRED RSP0 MSR as-is, because the RESET
>>> + * state of FRED MSRs is zero and INIT does not change the value of the
>>> + * FRED MSRs in a CPU offline/online cycle. But it doesn't seem safe to
>>> + * depend on the properties of INIT as that's way too many things that
>>> + * could cause bugs.
>>
>> Wouldn't that also open us up to kexec problems? If the last kernel
>> (maybe not even Linux) left RSP0 set, then the current kernel might
>> eventually try to run userspace with the old kernel's RSP0 value.
>>
>
> Yeah, it is a nonstarter. I believe Xin was trying to document the problems with *not* doing this, so someone doesn't have the bright idea to "optimize" this later.
>
exactly ;)
next prev parent reply other threads:[~2025-01-09 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 2:36 Xin Li (Intel)
2025-01-08 3:27 ` H. Peter Anvin
2025-01-08 20:14 ` Dave Hansen
2025-01-08 21:10 ` Andrew Cooper
2025-01-08 22:31 ` Dave Hansen
2025-01-08 23:32 ` Xin Li
2025-01-09 9:46 ` H. Peter Anvin
2025-01-09 18:48 ` Xin Li [this message]
2025-01-08 23:04 ` Dave Hansen
2025-01-08 23:32 ` Xin Li
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=a132c883-8399-4936-9f28-0fc28db22641@zytor.com \
--to=xin@zytor.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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
all inboxes | Powered by JetHome®