From: "Michael S. Tsirkin" <mst@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: peter.maydell@linaro.org, eric.auger@redhat.com,
lersek@redhat.com, qemu-devel@nongnu.org,
shannon.zhaosl@gmail.com, qemu-arm@nongnu.org,
ard.biesheuvel@arm.com, Igor Mammedov <imammedo@redhat.com>,
philmd@redhat.com
Subject: Re: [PATCH 3/4] hw/arm/virt-acpi-build: Only expose flash on older machine types
Date: Tue, 14 Jul 2020 04:57:50 -0400 [thread overview]
Message-ID: <20200714045537-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200714055109.owrlob6m53notzh3@kamzik.brq.redhat.com>
On Tue, Jul 14, 2020 at 07:51:09AM +0200, Andrew Jones wrote:
> On Mon, Jul 13, 2020 at 10:49:07AM +0200, Igor Mammedov wrote:
> > On Mon, 29 Jun 2020 16:09:37 +0200
> > Andrew Jones <drjones@redhat.com> wrote:
> >
> > > The flash device is exclusively for the host-controlled firmware, so
> > > we should not expose it to the OS. Exposing it risks the OS messing
> > > with it, which could break firmware runtime services and surprise the
> > > OS when all its changes disappear after reboot.
> > >
> > > As firmware needs the device and uses DT, we leave the device exposed
> > > there. It's up to firmware to remove the nodes from DT before sending
> > > it on to the OS. However, there's no need to force firmware to remove
> > > tables from ACPI (which it doesn't know how to do anyway), so we
> > > simply don't add the tables in the first place. But, as we've been
> > > adding the tables for quite some time and don't want to change the
> > > default hardware exposed to versioned machines, then we only stop
> > > exposing the flash device tables for 5.1 and later machine types.
> > >
> > > Suggested-by: Ard Biesheuvel <ard.biesheuvel@arm.com>
> > > Suggested-by: Laszlo Ersek <lersek@redhat.com>
> > > Signed-off-by: Andrew Jones <drjones@redhat.com>
> > > ---
> > > hw/arm/virt-acpi-build.c | 5 ++++-
> > > hw/arm/virt.c | 3 +++
> > > include/hw/arm/virt.h | 1 +
> > > 3 files changed, 8 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
> > > index 1384a2cf2ab4..91f0df7b13a3 100644
> > > --- a/hw/arm/virt-acpi-build.c
> > > +++ b/hw/arm/virt-acpi-build.c
> > > @@ -749,6 +749,7 @@ static void build_fadt_rev5(GArray *table_data, BIOSLinker *linker,
> > > static void
> > > build_dsdt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
> > > {
> > > + VirtMachineClass *vmc = VIRT_MACHINE_GET_CLASS(vms);
> > > Aml *scope, *dsdt;
> > > MachineState *ms = MACHINE(vms);
> > > const MemMapEntry *memmap = vms->memmap;
> > > @@ -767,7 +768,9 @@ build_dsdt(GArray *table_data, BIOSLinker *linker, VirtMachineState *vms)
> > > acpi_dsdt_add_cpus(scope, vms->smp_cpus);
> > > acpi_dsdt_add_uart(scope, &memmap[VIRT_UART],
> > > (irqmap[VIRT_UART] + ARM_SPI_BASE));
> > > - acpi_dsdt_add_flash(scope, &memmap[VIRT_FLASH]);
> > > + if (vmc->acpi_expose_flash) {
> > > + acpi_dsdt_add_flash(scope, &memmap[VIRT_FLASH]);
> > > + }
> > > acpi_dsdt_add_fw_cfg(scope, &memmap[VIRT_FW_CFG]);
> > > acpi_dsdt_add_virtio(scope, &memmap[VIRT_MMIO],
> > > (irqmap[VIRT_MMIO] + ARM_SPI_BASE), NUM_VIRTIO_TRANSPORTS);
> > > diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> > > index cd0834ce7faf..5adc9ff799ef 100644
> > > --- a/hw/arm/virt.c
> > > +++ b/hw/arm/virt.c
> > > @@ -2482,9 +2482,12 @@ DEFINE_VIRT_MACHINE_AS_LATEST(5, 1)
> > >
> > > static void virt_machine_5_0_options(MachineClass *mc)
> > > {
> > > + VirtMachineClass *vmc = VIRT_MACHINE_CLASS(OBJECT_CLASS(mc));
> > > +
> > > virt_machine_5_1_options(mc);
> > > compat_props_add(mc->compat_props, hw_compat_5_0, hw_compat_5_0_len);
> > > mc->numa_mem_supported = true;
> > > + vmc->acpi_expose_flash = true;
> >
> > we usually do not version ACPI tables changes
> > (unless we have a good reason to do so)
>
> Even when the change is to remove the exposure of hardware from the guest?
> Before this change, if a guest looked, it had a flash, after this change,
> if a guest looks, it doesn't.
It's up to the relevant maintainers who know what the semantics are.
FYI ACPI tables only change across a reset though.
So it's a question of whether guests get confused even if this
changes after a reboot.
Versioning is generally safer, but it's a good idea to document
the motivation for it.
> I'd feel much better versioning a change
> like that, than not.
>
> Thanks,
> drew
>
> >
> > > }
> > > DEFINE_VIRT_MACHINE(5, 0)
> > >
> > > diff --git a/include/hw/arm/virt.h b/include/hw/arm/virt.h
> > > index 31878ddc7223..c65be5fe0bb6 100644
> > > --- a/include/hw/arm/virt.h
> > > +++ b/include/hw/arm/virt.h
> > > @@ -119,6 +119,7 @@ typedef struct {
> > > bool no_highmem_ecam;
> > > bool no_ged; /* Machines < 4.2 has no support for ACPI GED device */
> > > bool kvm_no_adjvtime;
> > > + bool acpi_expose_flash;
> > > } VirtMachineClass;
> > >
> > > typedef struct {
> >
> >
next prev parent reply other threads:[~2020-07-14 8:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 14:09 [PATCH 0/4] hw/arm/virt-acpi-build: Only expose flash on older machine types Andrew Jones
2020-06-29 14:09 ` [PATCH 1/4] tests/acpi: remove stale allowed tables Andrew Jones
2020-06-29 15:06 ` Michael S. Tsirkin
2020-06-29 14:09 ` [PATCH 2/4] tests/acpi: virt: allow DSDT acpi table changes Andrew Jones
2020-06-29 14:09 ` [PATCH 3/4] hw/arm/virt-acpi-build: Only expose flash on older machine types Andrew Jones
2020-06-29 14:18 ` Philippe Mathieu-Daudé
2020-07-02 9:48 ` Laszlo Ersek
2020-07-02 9:53 ` Michael S. Tsirkin
2020-07-02 10:16 ` Peter Maydell
2020-07-02 11:13 ` Michael S. Tsirkin
2020-07-13 8:49 ` Igor Mammedov
2020-07-14 5:51 ` Andrew Jones
2020-07-14 8:57 ` Michael S. Tsirkin [this message]
2020-07-14 9:23 ` Andrew Jones
2020-07-14 9:31 ` Michael S. Tsirkin
2020-07-14 14:41 ` Igor Mammedov
2020-07-15 6:36 ` Andrew Jones
2020-07-15 9:37 ` Andrew Jones
2020-07-15 12:26 ` Laszlo Ersek
2020-07-15 13:05 ` Andrew Jones
2020-06-29 14:09 ` [PATCH 4/4] tests/acpi: virt: update golden masters for DSDT Andrew Jones
2020-07-02 9:49 ` Laszlo Ersek
2020-06-29 15:21 ` [PATCH 0/4] hw/arm/virt-acpi-build: Only expose flash on older machine types Michael S. Tsirkin
2020-07-02 19:26 ` Auger Eric
2020-07-03 13:02 ` Peter Maydell
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=20200714045537-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ard.biesheuvel@arm.com \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.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;
as well as URLs for NNTP newsgroup(s).