From: Koba Ko <kobak@nvidia.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Matt Ochs <mochs@nvidia.com>, James Morse <james.morse@arm.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhang Rui <rui.zhang@intel.com>,
linux-efi@vger.kernel.org
Subject: Re: [PATCH V9] acpi/prmt: find block with specific type
Date: Sun, 13 Oct 2024 03:49:56 +0800 [thread overview]
Message-ID: <6a08b06b-5672-473a-9a0a-7068da5db0d1@nvidia.com> (raw)
In-Reply-To: <CAMj1kXH6Q2t6ER3kZDtiAFmk6QKj24_LtV9gjfq3bjQCBAVSww@mail.gmail.com>
On 10/13/24 03:46, Ard Biesheuvel wrote:
> External email: Use caution opening links or attachments
>
>
> On Sat, 12 Oct 2024 at 21:42, KobaK <kobak@nvidia.com> wrote:
>> From: Koba Ko <kobak@nvidia.com>
>>
>> PRMT needs to find the correct type of block to
>> translate the PA-VA mapping for EFI runtime services.
>>
>> The issue arises because the PRMT is finding a block of
>> type EFI_CONVENTIONAL_MEMORY, which is not appropriate for
>> runtime services as described in Section 2.2.2 (Runtime
>> Services) of the UEFI Specification [1]. Since the PRM handler is
>> a type of runtime service, this causes an exception
>> when the PRM handler is called.
>>
>> [Firmware Bug]: Unable to handle paging request in EFI runtime service
>> WARNING: CPU: 22 PID: 4330 at drivers/firmware/efi/runtime-wrappers.c:341
>> __efi_queue_work+0x11c/0x170
>> Call trace:
>>
>> Find a block with specific type to fix this.
>> PRMT find a block with EFI_MEMORY_RUNTIME for PRM handler and PRM context.
>> If no suitable block is found, a warning message will be prompted
>> but the procedure continues to manage the next PRM handler.
>> However, if the PRM handler is actually called without proper allocation,
>> it would result in a failure during error handling.
>>
>> By using the correct memory types for runtime services,
>> ensure that the PRM handler and the context are
>> properly mapped in the virtual address space during runtime,
>> preventing the paging request error.
>>
>> The issue is really that only memory that has been remapped for
>> runtime by the firmware can be used by the PRM handler, and so the
>> region needs to have the EFI_MEMORY_RUNTIME attribute.
>>
>> [1] https://uefi.org/sites/default/files/resources/UEFI_Spec_2_10_Aug29.pdf
>> Fixes: cefc7ca46235 ("ACPI: PRM: implement OperationRegion handler for the PlatformRtMechanism subtype")
>> cc: stable@vger.kernel.org
>> Signed-off-by: Koba Ko <kobak@nvidia.com>
>> Reviewed-by: Matthew R. Ochs <mochs@nvidia.com>
>> Reviewed-by: Zhang Rui <rui.zhang@intel.com>
>> Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
>> ---
>> V2:
>> 1. format the changelog and add more about error handling.
>> 2. replace goto
>> V3: Warn if parts of handler are missed during va-pa translating.
>> V4: Fix the 0day
>> V5: Fix typo and pr_warn warning
>> V6: use EFI_MOMOERY_RUNTIME to find block and split goto refactor as a single
>> patch
>> V7:
>> 1. refine the codes and commit description as per comments
>> 2. drop goto refacotr
>> V8: Fix 0day and cc to stable
>> V9: Describe 0day fix
>> cast PA as (void *) in pr_warn
> Sigh.
>
> Please read to the end of my previous email and fix the other thing too.
Sorry, I lost that.
prev parent reply other threads:[~2024-10-12 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 19:42 KobaK
2024-10-12 19:46 ` Ard Biesheuvel
2024-10-12 19:49 ` Koba Ko [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-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=6a08b06b-5672-473a-9a0a-7068da5db0d1@nvidia.com \
--to=kobak@nvidia.com \
--cc=ardb@kernel.org \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.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®