From: "Nhi Pham via groups.io" <nhi=os.amperecomputing.com@groups.io>
To: "ardb+tianocore@kernel.org" <ardb+tianocore@kernel.org>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
discuss@edk2.groups.io
Subject: Re: [edk2-devel] Memory Attribute for depex section
Date: Wed, 10 Jan 2024 07:48:43 +0700 [thread overview]
Message-ID: <0cc39cfd-0d00-49db-9b56-872588da6445@os.amperecomputing.com> (raw)
In-Reply-To: <44ca139f-4d78-4322-b5b6-8e9788bb7486@os.amperecomputing.com>
++ discuss@edk2.groups.io
On 1/8/2024 5:11 PM, Nhi Pham wrote:
> Hi Ard, all,
>
> Could you please help explain how the depex section in an image is
> mapped in terms of memory attribute?
>
> As my observation, dispatcher locates[1] the depex section inside the
> module image and write[2] an evaluated data to the depex if necessary
> for scheduled boot order. The problem that the depex section is now in
> RO+X memory due to a part of the module image, so a writing to depex
> would cause data abort. I'm unsure whether this issue is generic in EDK2
> or not.
>
> I think of two approaches:
>
> #1 Relocate the depex section to heap memory for dependency evaluation?
>
> #2 EDK2 build tool to support granting write permission for depex section.
>
> [1] StandaloneMmPkg/Core/FwVol.c:236
> [2] StandaloneMmPkg/Core/Dependency.c:256
>
> Thanks,
> Nhi
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#113497): https://edk2.groups.io/g/devel/message/113497
Mute This Topic: https://groups.io/mt/103594587/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-01-10 0:49 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 [this message]
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
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=0cc39cfd-0d00-49db-9b56-872588da6445@os.amperecomputing.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