From: "Zhiguang Liu" <zhiguang.liu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"Ni, Ray" <ray.ni@intel.com>
Cc: "Liming Gao" <gaoliming@byosoft.com.cn>,
"László Érsek" <lersek@redhat.com>,
"Oliver Steffen" <osteffen@redhat.com>
Subject: Re: [edk2-devel] [PATCH v2 1/2] MdeModulePkg: rename PcdUse5LevelPageTable to PcdEnable5LevelPageTable
Date: Fri, 26 Jan 2024 02:49:13 +0000 [thread overview]
Message-ID: <SJ0PR11MB505337F759EC2ACAE377588390792@SJ0PR11MB5053.namprd11.prod.outlook.com> (raw)
In-Reply-To: <yr4cjvnzr4ljv32ctw37pw2sdrok4alxntfmxon7t6m3q7kdgf@eivnhofnu5fa>
Hi Gerd,
For the PCD, it current has below usage.
1) for 32-bit PEI and 64-bit DXE, this PCD will decide if use 5 level paging in DXE.
2) for 64-bit PEI and DXE, reset vector chooses if use 5 level paging in early phase. But BIOS can still switch paging mode based on this PCD later.
Since this PCD can be dynamic, we can let user to choose different paging mode in BIOS setup menu, and use this paging mode on reboot.
You may want to use one BIOS to support machine with different la57 capability, I assume two possible ways:
1) make the PCD as dynamic, and set it based on la57 capability.
2) Remove the ASSERT in DxeIpl
Both are fine for me.
Thanks
Zhiguang
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Gerd
> Hoffmann
> Sent: Thursday, January 25, 2024 8:17 PM
> To: Ni, Ray <ray.ni@intel.com>
> Cc: devel@edk2.groups.io; Liming Gao <gaoliming@byosoft.com.cn>; László
> Érsek <lersek@redhat.com>; Oliver Steffen <osteffen@redhat.com>
> Subject: Re: [edk2-devel] [PATCH v2 1/2] MdeModulePkg: rename
> PcdUse5LevelPageTable to PcdEnable5LevelPageTable
>
> On Thu, Jan 25, 2024 at 12:01:46PM +0000, Ni, Ray wrote:
> > Rename an existing PCD might break lots of platform builds.
> >
> > When 5-level paging capability was added to ResetVector, I also
> > considered to remove the PcdUse5LevelPageTable reference from C code.
> >
> > Let me think about it...
>
> Purging this completely from the source code is fine with me too.
>
> From OVMF point of view this is not needed, all backward compatibility
> concerns for old guests without 5-level paging support can be solved by just
> removing la57 capability from the vCPU (qemu -cpu host,la57=off).
>
> take care,
> Gerd
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114491): https://edk2.groups.io/g/devel/message/114491
Mute This Topic: https://groups.io/mt/103950404/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-01-26 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 8:20 [edk2-devel] [PATCH v2 0/2] MdeModulePkg: 5-level paging fixes Gerd Hoffmann
2024-01-25 8:20 ` [edk2-devel] [PATCH v2 1/2] MdeModulePkg: rename PcdUse5LevelPageTable to PcdEnable5LevelPageTable Gerd Hoffmann
2024-01-25 12:01 ` Ni, Ray
2024-01-25 12:17 ` Gerd Hoffmann
2024-01-26 2:49 ` Zhiguang Liu [this message]
2024-01-26 13:19 ` Gerd Hoffmann
2024-01-25 8:20 ` [edk2-devel] [PATCH v2 2/2] MdeModulePkg/VirtualMemory: fix 5-level paging assert Gerd Hoffmann
2024-01-25 23:22 ` [edk2-devel] [PATCH v2 0/2] MdeModulePkg: 5-level paging fixes Laszlo Ersek
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=SJ0PR11MB505337F759EC2ACAE377588390792@SJ0PR11MB5053.namprd11.prod.outlook.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