From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH 2/2] OvmfPkg/PlatformPei: prefer etc/e820 for memory detection
Date: Thu, 26 Aug 2021 09:12:53 +0200 [thread overview]
Message-ID: <20210826071253.jiy7y4fklridfzqi@sirius.home.kraxel.org> (raw)
In-Reply-To: <PH0PR11MB4885565C9F822976B8872CB78CC69@PH0PR11MB4885.namprd11.prod.outlook.com>
On Wed, Aug 25, 2021 at 03:15:04PM +0000, Yao, Jiewen wrote:
> Thanks for the detail info.
> We do have process for handle compatibility.
>
> My recommendation is:
> 1) Please send out RFC email about removing CMOS support in QEMU.
> To see if someone still need support old version before qemu version 1.7 (released Nov 2013).
> 2) Let's wait for 1 WW.
> 3) If no people need this, we can file a bugzilla to remove CMOS. Then we can follow up to submit patch to remove.
>
>
> Please help me understand another thing: Is that any plan in QEMU to *remove* CMOS interface ?
For the microvm machine type several legacy devices are optional (pic,
pit, rtc). cmos is provided by the rtc, so turning off rtc will also
remove the cmos.
There is no microvm support in ovmf yet, I have some experimental
patches but its incomplete + low priority right now.
There are no plans to drop cmos for 'pc' and 'q35' machine types.
> That could be a good indicator to remove the problem - we have two ways to get one data.
Can hardly be avoided long-term. It happens now and then that some
interface turns out to be insufficient and can't be easily extended.
So adding a new, better one while keeping the old working for
compatibility is the only way out ...
> I am worried the logic below to add "LowerMemorySize > 0".
>
> =====================
> GetSystemMemorySizeBelow4gb()
> {
> EFI_STATUS Status;
> UINT64 LowerMemorySize;
> UINT8 Cmos0x34;
> UINT8 Cmos0x35;
>
> Status = ScanOrAdd64BitE820Ram (FALSE, &LowerMemorySize, NULL);
> if (Status == EFI_SUCCESS || LowerMemorySize > 0) {
> return LowerMemorySize;
> }
Oops, yes, that logic is wrong. LowerMemorySize must be initialized and
it should be "&&" not "||". I'll fix it for v2.
take care,
Gerd
prev parent reply other threads:[~2021-08-26 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 8:11 [PATCH 0/2] OvmfPkg/PlatformPei: prefer etc/e820 for memory detection Gerd Hoffmann
2021-08-19 8:11 ` [PATCH 1/2] OvmfPkg/PlatformPei: ScanOrAdd64BitE820Ram improvements Gerd Hoffmann
2021-08-25 5:22 ` [edk2-devel] " Philippe Mathieu-Daudé
2021-08-19 8:11 ` [PATCH 2/2] OvmfPkg/PlatformPei: prefer etc/e820 for memory detection Gerd Hoffmann
2021-08-19 9:28 ` [edk2-devel] " Philippe Mathieu-Daudé
2021-08-25 9:24 ` Yao, Jiewen
2021-08-25 13:13 ` Gerd Hoffmann
2021-08-25 15:15 ` Yao, Jiewen
2021-08-26 7:12 ` Gerd Hoffmann [this message]
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=20210826071253.jiy7y4fklridfzqi@sirius.home.kraxel.org \
--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