From: Igor Mammedov <imammedo@redhat.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Shiju Jose" <shiju.jose@huawei.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Ani Sinha" <anisinha@redhat.com>,
"Dongjiu Geng" <gengdongjiu1@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Shannon Zhao" <shannon.zhaosl@gmail.com>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/5] Change ghes driver to use HEST-based offsets
Date: Tue, 3 Dec 2024 13:03:10 +0100 [thread overview]
Message-ID: <20241203130310.0bde48c0@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <cover.1732281080.git.mchehab+huawei@kernel.org>
On Fri, 22 Nov 2024 14:14:10 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> This series was part of the previous PR to add generic error injection
> support on GHES. It depends on a cleanup patch series sent earlier
> today:
>
> https://lore.kernel.org/qemu-devel/cover.1732266152.git.mchehab+huawei@kernel.org/T/#t
>
> It contains the changes of the math used to calculate offsets at HEST table
> and hardware_error firmware file. It prepares for the addition of GHES
> error injection.
>
> The first patch was previously at the cleanup series. It prepares
> the logic to support multiple sources.
>
> The second patch adds a new firmware file to store HEST address.
>
> The third patch use the new firmware to calculate offsets using
> HEST table.
>
> Patches 4 and 5 add migration support. They assume that this
> series will be merged for qemu 9.2 (maybe it is too late for that,
> as QEMU is now on soft freeze).
>
> I tested migration using both virt-9.1 and virt-9.2 machines
> on qemu 9.2.
>
> I also tested migration with:
>
> qemu-9.1 -M virt-9.1 -cpu cortex-a57 => qemu-9.2 -M virt-9.1 -cpu cortex-a57
> qemu-9.2 -M virt-9.1 -cpu cortex-a57 => qemu-9.1 -M virt-9.1 -cpu cortex-a57
was that with HEST enabled (it's 'ras' machine option),
It would be better to provide full CLI used
>
> ---
>
> v2:
> - some whitespace and comment changes
> - patch 3/6 (acpi/ghes: rename the function which gets hw error offsets)
> was merged on the cleanup series.
>
> Mauro Carvalho Chehab (5):
> acpi/ghes: Prepare to support multiple sources on ghes
> acpi/ghes: add a firmware file with HEST address
> acpi/ghes: Use HEST table offsets when preparing GHES records
> acpi/generic_event_device: Update GHES migration to cover hest addr
> acpi/generic_event_device: add logic to detect if HEST addr is
> available
>
> hw/acpi/generic_event_device.c | 30 +++++++
> hw/acpi/ghes.c | 156 +++++++++++++++++++++++++++++----
> hw/arm/virt-acpi-build.c | 33 ++++++-
> hw/core/machine.c | 2 +
> include/hw/acpi/ghes.h | 23 +++--
> 5 files changed, 216 insertions(+), 28 deletions(-)
>
next prev parent reply other threads:[~2024-12-03 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 13:14 [PATCH v2 0/5] Change ghes driver to use HEST-based offsets Mauro Carvalho Chehab
2024-11-22 13:14 ` [PATCH v2 1/5] acpi/ghes: Prepare to support multiple sources on ghes Mauro Carvalho Chehab
2024-11-22 13:14 ` [PATCH v2 2/5] acpi/ghes: add a firmware file with HEST address Mauro Carvalho Chehab
2024-11-22 13:14 ` [PATCH v2 3/5] acpi/ghes: Use HEST table offsets when preparing GHES records Mauro Carvalho Chehab
2024-11-25 12:00 ` Jonathan Cameron via
2024-11-22 13:14 ` [PATCH v2 4/5] acpi/generic_event_device: Update GHES migration to cover hest addr Mauro Carvalho Chehab
2024-11-25 12:00 ` Jonathan Cameron via
2024-11-22 13:14 ` [PATCH v2 5/5] acpi/generic_event_device: add logic to detect if HEST addr is available Mauro Carvalho Chehab
2024-11-25 12:08 ` Jonathan Cameron via
2024-12-03 12:03 ` Igor Mammedov [this message]
2024-12-03 13:59 ` [PATCH v2 0/5] Change ghes driver to use HEST-based offsets Mauro Carvalho Chehab
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=20241203130310.0bde48c0@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anisinha@redhat.com \
--cc=gengdongjiu1@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhaosl@gmail.com \
--cc=shiju.jose@huawei.com \
--cc=wangyanan55@huawei.com \
--cc=zhao1.liu@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;
as well as URLs for NNTP newsgroup(s).