From: "Laszlo Ersek" <lersek@redhat.com>
To: Nhi Pham <nhi@os.amperecomputing.com>, Ard Biesheuvel <ardb@kernel.org>
Cc: "Andrew (EFI) Fish" <afish@apple.com>,
edk2-devel-groups-io <devel@edk2.groups.io>,
"ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] Memory Attribute for depex section
Date: Fri, 19 Jan 2024 14:54:58 +0100 [thread overview]
Message-ID: <c2c5ada1-41f8-4b42-11db-35d1b80ec408@redhat.com> (raw)
In-Reply-To: <6e09ed4a-53b0-45e1-a070-b4086986876b@os.amperecomputing.com>
On 1/19/24 05:43, Nhi Pham wrote:
> On 1/18/2024 9:49 PM, Laszlo Ersek wrote:
>>>>> but I'd prefer to just remove this
>>>>> optimization from standalone MM, given that not only a) it shouldn't
>>>>> have to deal with a large number of protocol GUIDs, but also b) the
>>>>> driver dispatch is much more straight-forward. (Typically, StMM
>>>>> drivers can be dispatched in the order they appear in the firmware
>>>>> volume, in which case each DEPEX is evaluated only once anyway)
>>>>
>>>> Sounds like a promising basis for removing the optimization indeed!
>>>>
>>>
>>> Your patch suggested earlier works for me. And I don't see significant
>>> performance reduction compared with keeping optimization.
>>>
>>> I don't have strong reason on removing the optimization, but I think it
>>> would be simply good for now. Could you post your patch to edk2-devel
>>> for review and merge?
>>
>> That wouldn't be correct; I don't have any platform for testing StMM. I
>> proposed the patch purely based on code analysis. I prefer not to post
>> untested patches, if I can avoid it.
>
> I got it, thanks!
>
> I thought I could give Tested-by tag when you post the patch since I
> already verified the patch on a StMM platform
Oh, that seems to have eluded me, sorry -- it's not uncommon that a
patch submitter needs help with testing (external testing) on *some*
platforms, beside his or her main platform(s) of interest. What's quite
uncommon though is total untestability for the submitter; I admit I drew
a blank there. What you mention would have been viable.
Thank you for posting the patch, ultimately!
Laszlo
>
>>
>> You can however post my patch; simply add your S-o-b at the bottom. You
>> can also preserve my authorship on the patch with --author=... on
>> git-commit; but even that is unnecessary for such a simple patch (you
>> don't even have to pick the patch up from the email, it's trivial to
>> reimplement from scratch, just reading the email).
>
> I'm going to send the patch to edk2-devel and keep your authorship on
> the patch because there is no change compared with your suggestion in
> the email.
>
> Thanks,
> Nhi
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114048): https://edk2.groups.io/g/devel/message/114048
Mute This Topic: https://groups.io/mt/103594587/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-01-19 13:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:11 [edk2-devel] Memory Attribute for depex section Nhi Pham via groups.io
2024-01-10 0:48 ` Nhi Pham via groups.io
2024-01-10 13:09 ` Laszlo Ersek
2024-01-10 13:45 ` Laszlo Ersek
2024-01-10 21:50 ` Pedro Falcato
2024-01-11 8:46 ` Laszlo Ersek
2024-01-11 11:03 ` Laszlo Ersek
2024-01-12 2:10 ` Pedro Falcato
2024-01-12 9:35 ` Laszlo Ersek
2024-01-12 14:46 ` Pedro Falcato
2024-01-12 16:37 ` Michael D Kinney
2024-01-12 18:56 ` Andrew Fish via groups.io
2024-01-12 19:04 ` Michael D Kinney
2024-01-12 19:26 ` Andrew Fish via groups.io
2024-01-12 18:50 ` Andrew Fish via groups.io
2024-01-12 2:44 ` Andrew Fish via groups.io
2024-01-12 9:45 ` Laszlo Ersek
2024-01-15 13:07 ` Nhi Pham via groups.io
2024-01-15 14:04 ` Ard Biesheuvel
2024-01-15 19:00 ` Laszlo Ersek
2024-01-18 6:00 ` Nhi Pham via groups.io
2024-01-18 14:49 ` Laszlo Ersek
2024-01-19 4:43 ` Nhi Pham via groups.io
2024-01-19 13:54 ` Laszlo Ersek [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=c2c5ada1-41f8-4b42-11db-35d1b80ec408@redhat.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