From: Boqun Feng <boqun.feng@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-arm-kernel@vger.kernel.org, stable@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Oliver Smith-Denny <osde@linux.microsoft.com>
Subject: Re: [RFC] efi: Add ACPI_MEMORY_NVS into the linear map
Date: Mon, 19 Feb 2024 20:09:44 -0800 [thread overview]
Message-ID: <ZdQmCEepdOE2R7gS@boqun-archlinux> (raw)
In-Reply-To: <2024021718-dwindling-oval-8183@gregkh>
On Sat, Feb 17, 2024 at 08:49:32AM +0100, Greg KH wrote:
> On Thu, Feb 15, 2024 at 02:51:06PM -0800, Boqun Feng wrote:
> > Currently ACPI_MEMORY_NVS is omitted from the linear map, which causes
> > a trouble with the following firmware memory region setup:
> >
> > [..] efi: 0x0000dfd62000-0x0000dfd83fff [ACPI Reclaim|...]
> > [..] efi: 0x0000dfd84000-0x0000dfd87fff [ACPI Mem NVS|...]
> >
> > , on ARM64 with 64k page size, the whole 0x0000dfd80000-0x0000dfd8ffff
> > range will be omitted from the the linear map due to 64k round-up. And
> > a page fault happens when trying to access the ACPI_RECLAIM_MEMORY:
> >
> > [...] Unable to handle kernel paging request at virtual address ffff0000dfd80000
> >
> > To fix this, add ACPI_MEMORY_NVS into the linear map.
> >
> > Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
> > Cc: stable@vger.kernel.org # 5.15+
>
> What commit id does this fix? Can you include that as well?
>
It should be 7aff79e297ee ("Drivers: hv: Enable Hyper-V code to be built
on ARM64"), but as Ard mentioned earlier, this could be fixed at the VM
firmware, and Oliver is working on that. Should the situation change, I
will send a V2 with more information and include the commit id.
Regards,
Boqun
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2024-02-20 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 22:51 [RFC] efi: Add ACPI_MEMORY_NVS into the linear map Boqun Feng
2024-02-15 22:53 ` Boqun Feng
2024-02-15 23:21 ` Ard Biesheuvel
2024-02-15 23:40 ` Ard Biesheuvel
2024-02-17 7:49 ` Greg KH
2024-02-20 4:09 ` Boqun Feng [this message]
2024-02-20 8:27 ` Ard Biesheuvel
2024-02-20 16:28 ` Boqun Feng
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=ZdQmCEepdOE2R7gS@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=ardb@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osde@linux.microsoft.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).