From: Markus Armbruster <armbru@redhat.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Shiju Jose <shiju.jose@huawei.com>,
Cleber Rosa <crosa@redhat.com>, Eric Blake <eblake@redhat.com>,
John Snow <jsnow@redhat.com>,
linux-kernel@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v6 08/10] scripts/ghes_inject: add a script to generate GHES error inject
Date: Thu, 08 Aug 2024 15:21:21 +0200 [thread overview]
Message-ID: <87ed6zup4e.fsf@pond.sub.org> (raw)
In-Reply-To: <e9f2011095facb566815ccac13c9c87be710fa5e.1723119423.git.mchehab+huawei@kernel.org> (Mauro Carvalho Chehab's message of "Thu, 8 Aug 2024 14:26:34 +0200")
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> Using the QMP GHESv2 API requires preparing a raw data array
> containing a CPER record.
>
> Add a helper script with subcommands to prepare such data.
>
> Currently, only ARM Processor error CPER record is supported.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
[...]
> diff --git a/qapi/ghes-cper.json b/qapi/ghes-cper.json
> index 3cc4f9f2aaa9..d650996a7150 100644
> --- a/qapi/ghes-cper.json
> +++ b/qapi/ghes-cper.json
> @@ -36,8 +36,8 @@
> ##
> # @ghes-cper:
> #
> -# Inject ARM Processor error with data to be filled according with
> -# ACPI 6.2 GHESv2 spec.
> +# Inject a CPER error data to be filled according with ACPI 6.2
> +# spec via GHESv2.
> #
> # @cper: a single CPER record to be sent to the guest OS.
> #
Accident? Drop, or squash into PATCH 04 instead?
[...]
next prev parent reply other threads:[~2024-08-08 13:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1723119423.git.mchehab+huawei@kernel.org>
2024-08-08 12:26 ` [PATCH v6 01/10] acpi/generic_event_device: add an APEI error device Mauro Carvalho Chehab
2024-08-12 11:20 ` Igor Mammedov
2024-08-08 12:26 ` [PATCH v6 02/10] arm/virt: Wire up a GED error device for ACPI / GHES Mauro Carvalho Chehab
2024-08-12 11:27 ` Igor Mammedov
2024-08-08 12:26 ` [PATCH v6 03/10] acpi/ghes: Add support for GED error device Mauro Carvalho Chehab
2024-08-12 11:28 ` Igor Mammedov
2024-08-08 12:26 ` [PATCH v6 04/10] qapi/ghes-cper: add an interface to do generic CPER error injection Mauro Carvalho Chehab
2024-08-08 13:23 ` Markus Armbruster
2024-08-12 11:57 ` Igor Mammedov
2024-08-13 22:52 ` Mauro Carvalho Chehab
2024-08-08 12:26 ` [PATCH v6 05/10] acpi/ghes: rework the logic to handle HEST source ID Mauro Carvalho Chehab
2024-08-08 12:26 ` [PATCH v6 06/10] acpi/ghes: add support for generic error injection via QAPI Mauro Carvalho Chehab
2024-08-08 12:26 ` [PATCH v6 07/10] docs: acpi_hest_ghes: fix documentation for CPER size Mauro Carvalho Chehab
2024-08-12 11:59 ` Igor Mammedov
2024-08-08 12:26 ` [PATCH v6 08/10] scripts/ghes_inject: add a script to generate GHES error inject Mauro Carvalho Chehab
2024-08-08 13:21 ` Markus Armbruster [this message]
2024-08-08 12:26 ` [PATCH v6 09/10] target/arm: add an experimental mpidr arm cpu property object Mauro Carvalho Chehab
2024-08-12 12:02 ` Igor Mammedov
2024-08-08 12:26 ` [PATCH v6 10/10] scripts/arm_processor_error.py: retrieve mpidr if not filled 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=87ed6zup4e.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=shiju.jose@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