From: "Laszlo Ersek" <lersek@redhat.com>
To: Dhaval Sharma <dhaval@rivosinc.com>
Cc: devel@edk2.groups.io, Oleksiy Yakovlev <oleksiyy@ami.com>
Subject: Re: [edk2-devel] [PATCH V3 0/4] Add New Memory Attributes
Date: Tue, 21 Nov 2023 16:03:10 +0100 [thread overview]
Message-ID: <e96f175e-6488-aaba-b1d8-9b3f831b1a50@redhat.com> (raw)
In-Reply-To: <CAAxYnhRY-HpZ4p=0mL2bgo3RNUVovF2aM0XHMbv=HS-Zfxgv5Q@mail.gmail.com>
On 11/20/23 05:59, Dhaval Sharma wrote:
> Did you mean to add it as a memory type by itself like
> EFI_MEMORY_TYPE_INFORMATION?
Yes, a new enum constant for EFI_MEMORY_TYPE.
(It wasn't a "loaded question", just wanted to understand the reasoning.)
> My interpretation of Memory Type is that it is more of SW usability
> construct while Memory Attr is more of HW behavioural construct.
> Together they define how a memory region can be used.
I guess it's hard to tell apart. The SPM definition (visible in the
context below, from your earlier email) does seem like a software
usability construct ("avoid allocating for ...").
But, I truly don't know. I guess I was only trying to gauge if I could
be a useful reviewer for this series; probably not.
Thanks!
Laszlo
>
> On Fri, Nov 17, 2023 at 1:55 PM Laszlo Ersek <lersek@redhat.com
> <mailto:lersek@redhat.com>> wrote:
>
> On 11/17/23 09:07, Dhaval Sharma wrote:
> > Hi,
> > I wanted to revisit this thread and I am maintaining the context as
> > there are a lot of details already mentioned here
> regarding EFI_MEMORY_SP.
> > Other than what has been addressed here, we also would like to have an
> > option in edk2 to *avoid* using this type of memory for its own
> > purposes. This seems like one of the motivations for original request
> > and is being honored by OS today but not edk2 as it does not have any
> > specific implementation today which takes this attribute into
> consideration.
> > I would like to add PCD based implementation which informs edk2 NOT to
> > use this memory for its own purposes and leave it alone (as still
> > available memory to OS).
> >
> > Specific-purpose memory (SPM). The memory is earmarked for
> > specific purposes such as for specific device drivers or applications.
> > The SPM attribute serves as a hint to the OS to avoid allocating this
> > memory for core OS data or code that can not be relocated.
> > Prolonged use of this memory for purposes other than the intended
> > purpose may result in suboptimal platform performance.
> >
> > Some more context:
> > https://lwn.net/Articles/784971/ <https://lwn.net/Articles/784971/>
>
> Why was EFI_MEMORY_SP introduced as a memory attribute, rather than its
> own memory type?
>
> Laszlo
>
>
>
> --
> Thanks!
> =D
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111553): https://edk2.groups.io/g/devel/message/111553
Mute This Topic: https://groups.io/mt/75267363/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:[~2023-11-21 15:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 20:50 [PATCH V3 0/4] Add New Memory Attributes Oleksiy Yakovlev
2020-07-02 20:50 ` [PATCH V3 1/4] MdePkg: " Oleksiy Yakovlev
2020-07-06 9:11 ` [edk2-devel] " Laszlo Ersek
2020-07-02 20:50 ` [PATCH V3 2/4] MdeModulePkg: " Oleksiy Yakovlev
2020-07-06 9:13 ` [edk2-devel] " Laszlo Ersek
2020-07-13 16:12 ` Laszlo Ersek
2020-07-02 20:50 ` [PATCH V3 3/4] UefiCpuPkg: Update EFI_MEMORY_CACHETYPE_MASK definition Oleksiy Yakovlev
2020-07-06 9:16 ` [edk2-devel] " Laszlo Ersek
2020-07-13 16:13 ` Laszlo Ersek
2020-07-14 0:13 ` Dong, Eric
2020-07-02 20:50 ` [PATCH V3 4/4] UefiCpuPkg: Add New Memory Attributes Oleksiy Yakovlev
2020-07-13 16:14 ` [edk2-devel] " Laszlo Ersek
2020-07-14 0:16 ` Dong, Eric
2020-07-06 9:57 ` [edk2-devel] [PATCH V3 0/4] " Laszlo Ersek
2020-07-15 15:07 ` Laszlo Ersek
2023-11-17 8:07 ` Dhaval Sharma
2023-11-17 8:25 ` Laszlo Ersek
2023-11-20 4:59 ` Dhaval Sharma
2023-11-21 15:03 ` 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=e96f175e-6488-aaba-b1d8-9b3f831b1a50@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