From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, kraxel@redhat.com,
"Brian J. Johnson" <brian.johnson@hpe.com>
Cc: "West, Catharine" <catharine.west@intel.com>,
"Xu, Min M" <min.m.xu@intel.com>, "Ni, Ray" <ray.ni@intel.com>,
"Wu, MingliangX" <mingliangx.wu@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Xue, Shengfeng" <xueshengfeng@byosoft.com.cn>,
"Dong, Eric" <eric.dong@intel.com>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>,
"De, Debkumar" <debkumar.de@intel.com>
Subject: Re: [edk2-devel] [PATCH V1 1/1] UefiCpuPkg/ResetVector: Cache Disable should not be set by default in CR0
Date: Tue, 23 Jan 2024 15:13:22 +0100 [thread overview]
Message-ID: <1708ba2b-c969-ee8a-2cbe-fdc9acd31998@redhat.com> (raw)
In-Reply-To: <3lxerlg6g5gbzsxyh2v4qqqxru34ewytbge2wm6s7quyx3itx6@xlajojgm73qe>
On 1/23/24 11:52, Gerd Hoffmann wrote:
> On Mon, Jan 22, 2024 at 01:11:52PM -0600, Brian J. Johnson wrote:
>> On 1/18/24 09:46, Gerd Hoffmann wrote:
>>> On Wed, Jan 10, 2024 at 04:43:47PM +0000, West, Catharine wrote:
>>>> Disabling cache by default results in violation of BTG protections (if BTG enabled).
>>>> BIOS cannot assume that cache is disabled before it executes as ACM may be required to enable NEM.
>>>>
>>>> Whatever solution needs to be done here cannot evict ACM-enabled NEM.
>>>
>>> Well, it's OVMF in a virtual machine. No boot guard involved.
>>> So we could probably go for a OVMF-specific patch here.
>>>
>>> But I'd prefer to figure what exactly is happening here before going
>>> down that route. An extreme slowdown just because we flip that bit
>>> doesn't make sense to me.
>>>
>>>> Why is boot time increasing?
>>>
>>> Not clear. It seems to be the lzma uncompress of the firmware volume
>>> in rom / pflash which is very slow. Also it is apparently only
>>> triggered in case pci device assignment is used.
>>
>> I've seen extreme slowness on physical platforms when we've mixed up the
>> MTRRs or page tables, causing code to be mapped uncached.
>>
>> Lzma uncompress of ROM could be pretty slow as well, if the ROM is being
>> read uncached. Lzma probably reads the data a byte at a time, which is the
>> worst case for uncached accesses. Since this is a VM, it's not actually
>> uncached at the hardware level, but I don't know how QEMU/KVM handles
>> uncached guest mappings.... It may be doing a VMEXIT for every byte.
>>
>> Anyway, I suggest double-checking your page tables and MTRRs.
>
> It happens very early at boot, before MTRRs are setup, running on the
> initial page tables created by the OVMF reset vector. The initial page
> tables have just 'accessed', 'dirty', 'read/write' and 'present' bits
> set for the 0-4G identity mapping.
>
> It seems to have something to do with EPT. It does not happen on AMD
> processors. It also does not happen when disabling EPT support in kvm
> on the host machine.
>
> looked at kvm kernel traces, I don't see excessive vmexits.
This discussion evokes vague memories in me. I'll dump them here, but I
have no idea if they will be useful. (They probably won't.)
- edk2 commit 98f378a7be12 ("OvmfPkg/ResetVector: enable caching in
initial page tables", 2013-09-24)
- Linux (host) commit 879ae1880449 ("KVM: x86: obey
KVM_X86_QUIRK_CD_NW_CLEARED in kvm_set_cr0()", 2015-11-04)
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114202): https://edk2.groups.io/g/devel/message/114202
Mute This Topic: https://groups.io/mt/100367559/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-01-23 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 9:47 [edk2-devel] [PATCH V1 1/1] UefiCpuPkg/ResetVector: Cache Disable should not be set by default in CR0 xueshengfeng via groups.io
2023-07-26 9:55 ` Ni, Ray
[not found] ` <177562550EF0534C.27380@groups.io>
2023-08-03 8:14 ` Ni, Ray
2024-01-10 7:51 ` Min Xu
2024-01-10 16:43 ` West, Catharine
2024-01-18 15:46 ` Gerd Hoffmann
2024-01-22 19:11 ` Brian J. Johnson
2024-01-23 5:01 ` Min Xu
2024-01-23 10:52 ` Gerd Hoffmann
2024-01-23 14:13 ` Laszlo Ersek [this message]
2024-01-23 16:11 ` Gerd Hoffmann
2024-01-24 3:06 ` Min Xu
2024-01-24 12:49 ` Laszlo Ersek
2024-01-24 13:26 ` Gerd Hoffmann
2024-01-24 14:45 ` Laszlo Ersek
2024-01-24 17:11 ` Gerd Hoffmann
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-list 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=1708ba2b-c969-ee8a-2cbe-fdc9acd31998@redhat.com \
--to=devel@edk2.groups.io \
/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