public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Chao Li" <lichao@loongson.cn>
To: devel@edk2.groups.io, ardb@kernel.org, kraxel@redhat.com
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>,
	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: Thu, 25 Apr 2024 09:25:58 +0800	[thread overview]
Message-ID: <a07c5a84-3c3b-4e7f-bbb6-fa91831bb098@loongson.cn> (raw)
In-Reply-To: <CAMj1kXEhTUV0mPpXENNGKmx7XvS=ydh6H5m4wgx6iVZUgZZJfw@mail.gmail.com>

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

Hi Ard,

OK, let's go with HOBs and today I'm going to send the V2. :)


Thanks,
Chao
On 2024/4/25 00:23, Ard Biesheuvel wrote:
> On Wed, 24 Apr 2024 at 13:19, Gerd Hoffmann<kraxel@redhat.com>  wrote:
>> On Wed, Apr 24, 2024 at 09:57:50AM +0800, Chao Li wrote:
>>> Hi Gerd and Ard,
>>>
>>> Can I submit the V2 this week? I want all OvmfPkg changes to be meged before
>>> the 202405 feature freeze.
>> Yea, go ahead, lets stick to the PCD approach, given that Ard seems to
>> not have objections to that ;)
>>
> Apologies for my late response.
>
> As I have mentioned before (I think?) I strongly prefer HOBs over
> dynamic PCDs for values that are determined during PEI and not updated
> later.
>
> For other cases, I actually prefer protocols over PCDs because you can
> depex on protocols, and not on PCDs so you never know if the dispatch
> order is correct, i.e., whether PCD producers are dispatched before
> PCD consumers.
>
>
> 
>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118252): https://edk2.groups.io/g/devel/message/118252
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: 2837 bytes --]

  reply	other threads:[~2024-04-25  1:26 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
     [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 [this message]
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=a07c5a84-3c3b-4e7f-bbb6-fa91831bb098@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