From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"kraxel@redhat.com" <kraxel@redhat.com>,
"lixianglai@loongson.cn" <lixianglai@loongson.cn>
Subject: Re: [edk2-devel] [PATCH] OvmfPkg-EmuVariableFvbRuntimeDxe: Support Access To Memory Above 4G
Date: Sat, 11 Dec 2021 15:36:28 +0000 [thread overview]
Message-ID: <MW4PR11MB5872BAEC50E19D3C65DEB75F8C729@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211206121859.vqw2jfpxdagi5hvw@sirius.home.kraxel.org>
Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Gerd
> Hoffmann
> Sent: Monday, December 6, 2021 8:19 PM
> To: devel@edk2.groups.io; lixianglai@loongson.cn
> Subject: Re: [edk2-devel] [PATCH] OvmfPkg-EmuVariableFvbRuntimeDxe:
> Support Access To Memory Above 4G
>
> On Mon, Dec 06, 2021 at 12:00:33PM +0800, xianglai wrote:
> > In FvbInitialize Function,
> > PcdFlashNvStorageVariableBase64 PcdFlashNvStorageFtwWorkingBase
> > PcdFlashNvStorageFtwSpareBase will not exceed 0x100000000,
> > Due to truncation and variable type limitations.
> > That leads to the NV variable cannot be saved to the memory above 4G.
> >
> > Modify as follows:
> > 1.Remove the forced type conversion of UINT32.
> > 2.Use UINT64 type variables.
> >
> > Signed-off-by: xianglai li <lixianglai@loongson.cn>
>
> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com>
>
>
>
>
>
next prev parent reply other threads:[~2021-12-11 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1638759596.git.lixianglai@loongson.cn>
2021-12-06 4:00 ` [edk2-devel] [PATCH] OvmfPkg-EmuVariableFvbRuntimeDxe: Support Access To Memory Above 4G xianglai
2021-12-06 12:18 ` Gerd Hoffmann
2021-12-11 15:36 ` Yao, Jiewen [this message]
[not found] ` <16BFBD5C8AF150FF.19089@groups.io>
2021-12-11 16:13 ` Yao, Jiewen
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=MW4PR11MB5872BAEC50E19D3C65DEB75F8C729@MW4PR11MB5872.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