public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Oliver Smith-Denny" <osde@linux.microsoft.com>
To: Taylor Beebe <taylor.d.beebe@gmail.com>,
	devel@edk2.groups.io, ardb@kernel.org
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [PATCH v1] MdeModulePkg: Fixup MAT Attributes After Splitting EFI Memory Map
Date: Wed, 17 Apr 2024 14:41:48 -0700	[thread overview]
Message-ID: <e1ae89dd-8bf8-4253-beaf-0a918b86b094@linux.microsoft.com> (raw)
In-Reply-To: <c6ed8ddd-7efa-4d9f-b7fc-cb94c2054871@gmail.com>

On 4/17/2024 7:34 AM, Taylor Beebe wrote:
> 
> On 4/17/2024 7:09 AM, Oliver Smith-Denny wrote:
>> On 4/17/2024 7:05 AM, Taylor Beebe wrote:
>>>
>>> On 4/17/2024 6:40 AM, Oliver Smith-Denny wrote:
>>>> Aside from this, I wonder if we can be more aspirational here. These
>>>> EfiRuntimeServicesCode regions without attributes set are, if I am
>>>> understanding correctly, from loaded images. 
>>> These EfiRuntimeServicesCode regions without attributes set are
>>> not part of loaded image memory. I think that's what you meant but
>>> wanted to clarify.
>>
>> Are these regions without attributes from image sections that have
>> been padded to RUNTIME_PAGE_ALLOCATION_GRANULARITY, i.e. they are
>> the pads? Or are we saying we don't know what these regions are
>> at this point? It is true in theory someone could just allocate
>> an EfiRuntimeServicesCode section.
> Good question -- I had not considered the extra padding applied
> to these allocations. It could be either. The memory map returned
> via GetMemoryMap() will merge descriptors together based on type
> so it's possible to mistake an unrelated EfiRuntimeServicesCode
> allocation with padding applied to a runtime image memory
> allocation if they are contiguous.

Taylor and I had an offline conversation and checked on this, my
recent patch moving ImagePropertiesRecordLib to use VirtualSize
instead of SizeOfRawData fixed this. So we should not see any
padding sections as without attributes.

Now, for the case of ARM64, where you have 64k runtime
granularity and often will end up with the case of many
extra pages in a code section, those pages will be marked
as RO and executable, even though they contain garbage. I think
it would be worthwhile to mark the excess garbage pages, if they
exist for a given section, as RP. Nothing should be using them
in any fashion, they are padding.

Oliver


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



  parent reply	other threads:[~2024-04-17 21:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  2:28 [edk2-devel] [PATCH v1] MdeModulePkg: Fixup MAT Attributes After Splitting EFI Memory Map Taylor Beebe
2024-04-17  6:38 ` Ard Biesheuvel
2024-04-17 13:40   ` Oliver Smith-Denny
2024-04-17 14:05     ` Taylor Beebe
2024-04-17 14:09       ` Oliver Smith-Denny
2024-04-17 14:34         ` Taylor Beebe
2024-04-17 16:52           ` Ard Biesheuvel
2024-04-17 21:53             ` Oliver Smith-Denny
2024-04-17 21:41           ` Oliver Smith-Denny [this message]
     [not found]           ` <17C72F39F4EB8845.20027@groups.io>
2024-04-17 22:12             ` Oliver Smith-Denny

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=e1ae89dd-8bf8-4253-beaf-0a918b86b094@linux.microsoft.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