From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Dongjiu Geng <gengdongjiu@huawei.com>,
Xiang Zheng <zhengxiang9@huawei.com>,
qemu-arm <qemu-arm@nongnu.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Igor Mammedov <imammedo@redhat.com>,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH v3] hw/arm: Restrict APEI tables generation to the 'virt' machine
Date: Mon, 19 Oct 2020 16:26:06 +0100 [thread overview]
Message-ID: <CAFEAcA-O847-ATWLYKfFDoDWapeFfLy-CH1Fg0G0E8PVq0xYng@mail.gmail.com> (raw)
In-Reply-To: <20201008161414.2672569-1-philmd@redhat.com>
On Thu, 8 Oct 2020 at 17:14, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
> While APEI is a generic ACPI feature (usable by X86 and ARM64), only
> the 'virt' machine uses it, by enabling the RAS Virtualization. See
> commit 2afa8c8519: "hw/arm/virt: Introduce a RAS machine option").
>
> Restrict the APEI tables generation code to the single user: the virt
> machine. If another machine wants to use it, it simply has to 'select
> ACPI_APEI' in its Kconfig.
>
> Fixes: aa16508f1d ("ACPI: Build related register address fields via hardware error fw_cfg blob")
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> Reviewed-by: Dongjiu Geng <gengdongjiu@huawei.com>
> Acked-by: Laszlo Ersek <lersek@redhat.com>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
Applied to target-arm.next, thanks.
-- PMM
prev parent reply other threads:[~2020-10-19 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 16:14 [PATCH v3] hw/arm: Restrict APEI tables generation to the 'virt' machine Philippe Mathieu-Daudé
2020-10-19 15:26 ` Peter Maydell [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=CAFEAcA-O847-ATWLYKfFDoDWapeFfLy-CH1Fg0G0E8PVq0xYng@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=gengdongjiu@huawei.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhengxiang9@huawei.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).