From: Will Deacon <will@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev,
catalin.marinas@arm.com, gshan@redhat.com,
aneesh.kumar@kernel.org, sami.mujawar@arm.com,
sudeep.holla@arm.com, steven.price@arm.com,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] GHES firmware can't be readonly - Was: Re: [PATCH v3 3/3] arm64: acpi: Enable ACPI CCEL support
Date: Mon, 24 Nov 2025 13:14:24 +0000 [thread overview]
Message-ID: <aSRaME9ZO-nchE1I@willie-the-truck> (raw)
In-Reply-To: <4a750da6-7883-4afa-94c1-4806677e61c2@arm.com>
On Mon, Nov 24, 2025 at 05:21:00AM +0000, Suzuki K Poulose wrote:
> On 21/11/2025 21:46, Mauro Carvalho Chehab wrote:
> > Hi,
> >
> > Em Thu, 18 Sep 2025 13:56:18 +0100
> > Suzuki K Poulose <suzuki.poulose@arm.com> escreveu:
> >
> > > Add support for ACPI CCEL by handling the EfiACPIMemoryNVS type memory.
> > > As per UEFI specifications NVS memory is reserved for Firmware use even
> > > after exiting boot services. Thus map the region as read-only.
> > >
> > > Cc: Sami Mujawar <sami.mujawar@arm.com>
> > > Cc: Will Deacon <will@kernel.org>
> > > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > > Cc: Aneesh Kumar K.V <aneesh.kumar@kernel.org>
> > > Cc: Steven Price <steven.price@arm.com>
> > > Cc: Sudeep Holla <sudeep.holla@arm.com>
> > > Cc: Gavin Shan <gshan@redhat.com>
> > > Reviewed-by: Gavin Shan <gshan@redhat.com>
> > > Tested-by: Sami Mujawar <sami.mujawar@arm.com>
> > > Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> > > ---
> > > arch/arm64/kernel/acpi.c | 10 ++++++++++
> > > 1 file changed, 10 insertions(+)
> > >
> > > diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c
> > > index 4d529ff7ba51..b3195b3b895f 100644
> > > --- a/arch/arm64/kernel/acpi.c
> > > +++ b/arch/arm64/kernel/acpi.c
> > > @@ -357,6 +357,16 @@ void __iomem *acpi_os_ioremap(acpi_physical_address phys, acpi_size size)
> > > * as long as we take care not to create a writable
> > > * mapping for executable code.
> > > */
> > > + fallthrough;
> > > +
> > > + case EFI_ACPI_MEMORY_NVS:
> > > + /*
> > > + * ACPI NVS marks an area reserved for use by the
> > > + * firmware, even after exiting the boot service.
> > > + * This may be used by the firmware for sharing dynamic
> > > + * tables/data (e.g., ACPI CCEL) with the OS. Map it
> > > + * as read-only.
> > > + */
> > > prot = PAGE_KERNEL_RO;
> >
> > Please revert this change.
> >
> > Making area reserved to be used by firmware breaks some APEI
> > notification mechanisms:
>
> Thanks for the report. Clearly, we missed this case. I am happy for this
> patch to be reverted and we can work out the handling of NVS later.
I'll revert the change shortly.
Will
next prev parent reply other threads:[~2025-11-24 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 12:56 [PATCH v3 0/3] arm64: realm: Add support for encrypted data from firmware Suzuki K Poulose
2025-09-18 12:56 ` [PATCH v3 1/3] arm64: realm: ioremap: Allow mapping memory as encrypted Suzuki K Poulose
2025-09-18 12:56 ` [PATCH v3 2/3] arm64: Enable EFI secret area Securityfs support Suzuki K Poulose
2025-09-18 12:56 ` [PATCH v3 3/3] arm64: acpi: Enable ACPI CCEL support Suzuki K Poulose
2025-11-21 21:46 ` [REGRESSION] GHES firmware can't be readonly - Was: " Mauro Carvalho Chehab
2025-11-24 5:21 ` Suzuki K Poulose
2025-11-24 9:33 ` Mauro Carvalho Chehab
2025-11-24 13:14 ` Will Deacon [this message]
2025-09-19 18:38 ` [PATCH v3 0/3] arm64: realm: Add support for encrypted data from firmware Will Deacon
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-all 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=aSRaME9ZO-nchE1I@willie-the-truck \
--to=will@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sami.mujawar@arm.com \
--cc=steven.price@arm.com \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
/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
all inboxes | Powered by JetHome®