public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chao Li" <lichao@loongson.cn>
To: devel@edk2.groups.io, kraxel@redhat.com,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Jiewen Yao <jiewen.yao@intel.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	Sami Mujawar <sami.mujawar@arm.com>,
	Sunil V L <sunilvl@ventanamicro.com>,
	Andrei Warkentin <andrei.warkentin@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 0/4] Adjust the QemuFwCfgLibMmio and add PEI stage
Date: Mon, 22 Apr 2024 17:21:32 +0800	[thread overview]
Message-ID: <c3db04be-2543-4b6c-bd3f-7064b1a02170@loongson.cn> (raw)
In-Reply-To: <17C70907D38C479B.20815@groups.io>

[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]

Hi Ard,

Could you take a look at this patch set and give you some suggestions?


Thanks,
Chao
On 2024/4/17 18:01, Chao Li wrote:
>
> Hi Gerd,
>
> On 2024/4/17 17:35, Gerd Hoffmann wrote:
>> On Wed, Apr 17, 2024 at 04:12:56PM +0800, Chao Li wrote:
>>> Patch1: Added three PCDs for QemuFwCfgLibMmio
>>> Patch2: Sparate QemuFwCfgLibMmio.c into two files and default as DXE
>>> stage library.
>>> Patch3: Added QemuFwCfgMmiLib PEI version
>>> Patch4: Rename QemuFwCfgLibMmio.inf to QemuFwCfgMmioDxeLib.inf and
>>> enable it in AARCH64 and RISCV64.
>> Ok, I see, you are using the PCDs because global variables don't work
>> in PEI.
> Yes. :)
>> Alternative approach would be to create a HOB for that (see
>> EFI_HOB_PLATFORM_INFO used by X64).  Not sure this is a good idea
>> though given that we have three different architectures using that code.
>> Ard, any advise?
> I think HOB might be heavy, and the dynamically PCD is also uses the 
> HOB, so this I think this way is more simpler. I'm also looking 
> forward Ard's suggestions. :)
>>>    OvmfPkg: Add three PCDs for QemuFwCfgLib
>>>    OvmfPkg: Separate QemuFwCfgLibMmio.c into two files
>> This patch should be splitted into two, one doing the code split without
>> functional change, and one which switches from global variables to PCDs
>> (or HOB).
> OK, I will split it in V2.
>> Otherwise this looks good to me (and I'd suggest to keep and merge this
>> as separate patch series).
> Sure!
>> take care,
>>    Gerd
>>
>>
>>
>>
>>
> 


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118079): https://edk2.groups.io/g/devel/message/118079
Mute This Topic: https://groups.io/mt/105573103/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 4265 bytes --]

  parent reply	other threads:[~2024-04-22  9:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  8:12 [edk2-devel] [PATCH v1 0/4] Adjust the QemuFwCfgLibMmio and add PEI stage Chao Li
2024-04-17  8:13 ` [edk2-devel] [PATCH v1 1/4] OvmfPkg: Add three PCDs for QemuFwCfgLib Chao Li
2024-04-17  8:13 ` [edk2-devel] [PATCH v1 2/4] OvmfPkg: Separate QemuFwCfgLibMmio.c into two files Chao Li
2024-04-17  8:13 ` [edk2-devel] [PATCH v1 3/4] OvmfPkg: Add the QemuFwCfgMmioLib PEI stage version Chao Li
2024-04-17  8:13 ` [edk2-devel] [PATCH v1 4/4] OvmfPkg: Rename QemuFwCfgLibMmio.inf and enable new name in AARCH64 and RISCV64 virtual machines Chao Li
2024-04-17  9:35 ` [edk2-devel] [PATCH v1 0/4] Adjust the QemuFwCfgLibMmio and add PEI stage Gerd Hoffmann
2024-04-17 10:01   ` Chao Li
     [not found]   ` <17C70907D38C479B.20815@groups.io>
2024-04-22  9:21     ` Chao Li [this message]
     [not found]     ` <17C88FBD6FF53AEF.31749@groups.io>
2024-04-24  1:57       ` Chao Li
2024-04-24 11:19         ` Gerd Hoffmann
2024-04-24 16:23           ` Ard Biesheuvel
2024-04-25  1:25             ` Chao Li
2024-04-25  1:23           ` Chao Li

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=c3db04be-2543-4b6c-bd3f-7064b1a02170@loongson.cn \
    --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