[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1862275b-e7ca-4fa0-bdea-f739e90d9d22@linux.intel.com>
Date: Mon, 12 May 2025 17:24:21 +0800
From: Jiaqing Zhao <jiaqing.zhao@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, Bernhard Kaindl <bk@...e.de>,
Andi Kleen <ak@...ux.intel.com>, Li Fei <fei1.li@...el.com>,
stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] x86/mtrr: Check if fixed-range MTRR exists in
mtrr_save_fixed_ranges()
On 2025-05-12 16:46, Borislav Petkov wrote:
> On May 12, 2025 10:31:23 AM GMT+02:00, Jiaqing Zhao <jiaqing.zhao@...ux.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
Powered by blists - more mailing lists