From: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Bernhard Kaindl <bk@suse.de>, Andi Kleen <ak@linux.intel.com>,
Li Fei <fei1.li@intel.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/mtrr: Check if fixed-range MTRR exists in mtrr_save_fixed_ranges()
Date: Mon, 12 May 2025 17:24:21 +0800 [thread overview]
Message-ID: <1862275b-e7ca-4fa0-bdea-f739e90d9d22@linux.intel.com> (raw)
In-Reply-To: <FFB8ACEC-7208-40D0-8B57-EBB2A57DF65F@alien8.de>
On 2025-05-12 16:46, Borislav Petkov wrote:
> On May 12, 2025 10:31:23 AM GMT+02:00, Jiaqing Zhao <jiaqing.zhao@linux.intel.com> wrote:
>> This fixes unchecked MSR access error on platform without fixed-range
>> MTRRs when doing ACPI S3 suspend.
>
> Is this happening on hw which is shipping now and users will see it or is this some new platform which is yet to see the light of day in the future?
>
Actually it is happening on virtualized platform. A recent version of
ACRN hypervisor has removed emulated fixed-range MTRRs.
Thanks,
Jiaqing
next prev parent reply other threads:[~2025-05-12 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 17:06 [PATCH v2] x86/mtrr: Check if fixed-range MTRR exists in mtrr_save_fixed_ranges() Jiaqing Zhao
2025-05-09 17:32 ` Borislav Petkov
2025-05-12 8:31 ` Jiaqing Zhao
2025-05-12 8:46 ` Borislav Petkov
2025-05-12 9:24 ` Jiaqing Zhao [this message]
2025-05-12 11:00 ` Borislav Petkov
2025-05-12 14:31 ` [tip: x86/mtrr] x86/mtrr: Check if fixed-range MTRRs exist " tip-bot2 for Jiaqing Zhao
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=1862275b-e7ca-4fa0-bdea-f739e90d9d22@linux.intel.com \
--to=jiaqing.zhao@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=bk@suse.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fei1.li@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.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