From: Dmytro Maluka <dmaluka@chromium.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@google.com>,
"Saurabh Sengar" <ssengar@linux.microsoft.com>,
"Usama Arif" <usamaarif642@gmail.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Frank Rowand" <frowand.list@gmail.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE"
<devicetree@vger.kernel.org>,
"Pierre-Clément Tosi" <ptosi@google.com>,
"Shikha Panwar" <shikhapanwar@google.com>,
"Will Deacon" <will@kernel.org>, "Keir Fraser" <keirf@google.com>,
"Michal Mazurek" <mazurekm@google.com>,
"Bartłomiej Grzesik" <bgrzesik@google.com>,
"Tomasz Nowicki" <tnowicki@google.com>,
"Grzegorz Jaszczyk" <jaszczyk@google.com>
Subject: Re: [PATCH] x86/of: Restore possibility to use both ACPI and FDT from bootloader
Date: Mon, 6 Jan 2025 19:51:04 +0100 [thread overview]
Message-ID: <Z3wmGIOG-ge63Hce@google.com> (raw)
In-Reply-To: <Z3u7f4goH5Hq545b@infradead.org>
On Mon, Jan 06, 2025 at 03:16:15AM -0800, Christoph Hellwig wrote:
> On Mon, Dec 23, 2024 at 06:18:03PM +0000, Dmytro Maluka wrote:
> > There are cases when the bootloader provides information to the kernel
> > in both ACPI and DTB, not interchangeably. One such use case is virtual
> > machines in Android. When running on x86, the Android Virtualization
> > Framework (AVF) boots VMs with ACPI like it is usually done on x86 (i.e.
> > the virtual LAPIC, IOAPIC, HPET, PCI MMCONFIG etc are described in ACPI)
> > but also passes various AVF-specific boot parameters in DTB. This allows
> > reusing the same implementations of various AVF components on both
> > arm64 and x86.
>
> What are these "AVF-specific boot parameters"?
Let me quote my reply to Rob:
The strictly AVF-specific properties are described in [1]. When it comes
to Linux guests, actually AFAIK currently all those properties are
consumed by the guest userspace, not the guest kernel, so the role of
the kernel is in fact just to pass them over to the userspace via sysfs.
Besides that, one important DT binding used by AVF's Linux guest
kernels, not userspace, is google,open-dice documented in
Documentation/devicetree/bindings/reserved-memory/google,open-dice.yaml.
[2] describes how it is used by the protected VM firmware (pvmfw) to
securely boot protected VMs.
Cc'ing some AVF folks to keep me honest.
(AVF used to support protected VMs on arm64 only, but now we are trying
to make them work on x86. So, taking google,open-dice as an example, we
could add an ACPI binding to the open-dice driver, however bloating
pvmfw with AML support is a no go, so we want to keep passing it via DT
on x86 as well.)
[1] https://android.googlesource.com/platform/packages/modules/Virtualization/+/refs/heads/main/docs/device_trees.md#dt-for-guests
[2] https://android.googlesource.com/platform/packages/modules/Virtualization/+/refs/heads/main/guest/pvmfw/#handover-abi
prev parent reply other threads:[~2025-01-06 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 18:18 [PATCH] x86/of: Restore possibility to use both ACPI and FDT from bootloader Dmytro Maluka
2025-01-02 18:08 ` Rob Herring
2025-01-02 22:18 ` Dmytro Maluka
2025-01-03 14:19 ` Rob Herring
2025-01-06 11:16 ` Christoph Hellwig
2025-01-06 18:51 ` Dmytro Maluka [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=Z3wmGIOG-ge63Hce@google.com \
--to=dmaluka@chromium.org \
--cc=bgrzesik@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jaszczyk@google.com \
--cc=keirf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mazurekm@google.com \
--cc=mingo@redhat.com \
--cc=ptosi@google.com \
--cc=robh@kernel.org \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
--cc=shikhapanwar@google.com \
--cc=ssengar@linux.microsoft.com \
--cc=tglx@linutronix.de \
--cc=tnowicki@google.com \
--cc=usamaarif642@gmail.com \
--cc=will@kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.