From: "Sunil V L" <sunilvl@ventanamicro.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Andrei Warkentin <andrei.warkentin@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg/RiscVVirt: Check "no-map" and mark EfiReservedMemoryType
Date: Tue, 18 Jul 2023 09:39:22 +0530 [thread overview]
Message-ID: <ZLYQcknNXosEBgHw@sunil-laptop> (raw)
In-Reply-To: <CAKbZUD3_iR+mSphWkjbpA8ktj7cJL=wxNbC6xW4EHXJ_n6jRUQ@mail.gmail.com>
On Mon, Jul 17, 2023 at 07:03:28PM +0100, Pedro Falcato wrote:
> On Mon, Jul 17, 2023 at 5:59 PM Sunil V L <sunilvl@ventanamicro.com> wrote:
> >
> > OpenSBI now marks PMP regions with "no-map" attribute.
> > So, remove the workaround and add the ReservedMemory only
> > when no-map is set so that it follows DT spec.
>
> Isn't there a concern for supporting older OpenSBI versions? Is there
> no guarantee that it will work?
>
> This change looks like it should break older OpenSBI versions.
>
Hi Pedro,
You are right, but it is OK because this workaround was mainly required
for RISC-V ACPI. Currently, ACPI is not fully enabled for RISC-V. So,
there are no practical users who get affected.
Thanks,
Sunl
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#106977): https://edk2.groups.io/g/devel/message/106977
Mute This Topic: https://groups.io/mt/100198972/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:[~2023-07-18 4:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 16:59 [edk2-devel] [PATCH 1/1] OvmfPkg/RiscVVirt: Check "no-map" and mark EfiReservedMemoryType Sunil V L
2023-07-17 18:03 ` Pedro Falcato
2023-07-18 4:09 ` Sunil V L [this message]
2023-07-19 5:59 ` Ranbir Singh
2023-07-21 4:54 ` Sunil V L
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=ZLYQcknNXosEBgHw@sunil-laptop \
--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