From: Igor Mammedov <imammedo@redhat.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Dongjiu Geng <gengdongjiu1@gmail.com>,
linux-kernel@vger.kernel.org, qemu-arm@nongnu.org,
qemu-devel@nongnu.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v2 04/15] acpi/ghes: better handle source_id and notification
Date: Wed, 2 Oct 2024 15:28:09 +0200 [thread overview]
Message-ID: <20241002152809.0dcc4013@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <1b6ddd0bdfc9ac32a35fa7d85692e635bb76da11.1727766088.git.mchehab+huawei@kernel.org>
On Tue, 1 Oct 2024 09:03:41 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> GHES has two fields that are stored on HEST error source
> blocks:
>
> - notification type, which is a number defined at the ACPI spec
> containing several arch-specific synchronous and assynchronous
> types;
> - source id, which is a HW/FW defined number, used to distinguish
> between different implemented hardware report mechanisms.
there could be several sources with the same
hardware report mechanisms /aka notification type/
s/between different implemented hardware report mechanisms/
different implemented sources.
> Cleanup the logic to fill those, as they should be handled
> independently.
above doesn't really say/describe the patch's intent
> This is a preparation for a future patch that will shift
> those fields to the HEST init function call.
not relevant in this series
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> ---
>
> Chenges from v10:
>
> - Some changes got moved to the previous patch.
>
> Changes from v8:
> - Non-rename/cleanup changes merged altogether;
> - source ID is now more generic, defined per guest target.
> That should make easier to add support for 86.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> hw/acpi/ghes.c | 23 +++++++++--------------
> 1 file changed, 9 insertions(+), 14 deletions(-)
>
> diff --git a/hw/acpi/ghes.c b/hw/acpi/ghes.c
> index 4a6c45bcb4be..29cd7e4d8171 100644
> --- a/hw/acpi/ghes.c
> +++ b/hw/acpi/ghes.c
> @@ -284,9 +284,13 @@ static void build_ghes_error_table(GArray *hardware_errors, BIOSLinker *linker)
> }
>
> /* Build Generic Hardware Error Source version 2 (GHESv2) */
> -static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker)
> +static void build_ghes_v2(GArray *table_data,
> + BIOSLinker *linker,
> + enum AcpiGhesNotifyType notify,
> + uint16_t source_id)
> {
> uint64_t address_offset;
> +
> /*
> * Type:
> * Generic Hardware Error Source version 2(GHESv2 - Type 10)
> @@ -316,18 +320,8 @@ static void build_ghes_v2(GArray *table_data, int source_id, BIOSLinker *linker)
> address_offset + GAS_ADDR_OFFSET, sizeof(uint64_t),
> ACPI_GHES_ERRORS_FW_CFG_FILE, source_id * sizeof(uint64_t));
>
> - switch (source_id) {
> - case ACPI_HEST_SRC_ID_SEA:
> - /*
> - * Notification Structure
> - * Now only enable ARMv8 SEA notification type
> - */
> - build_ghes_hw_error_notification(table_data, ACPI_GHES_NOTIFY_SEA);
> - break;
> - default:
> - error_report("Not support this error source");
> - abort();
> - }
> + /* Notification Structure */
> + build_ghes_hw_error_notification(table_data, notify);
>
> /* Error Status Block Length */
> build_append_int_noprefix(table_data, ACPI_GHES_MAX_RAW_DATA_LENGTH, 4);
> @@ -369,7 +363,8 @@ void acpi_build_hest(GArray *table_data, GArray *hardware_errors,
>
> /* Error Source Count */
> build_append_int_noprefix(table_data, ACPI_GHES_ERROR_SOURCE_COUNT, 4);
> - build_ghes_v2(table_data, ACPI_HEST_SRC_ID_SEA, linker);
> + build_ghes_v2(table_data, linker,
> + ACPI_GHES_NOTIFY_SEA, ACPI_HEST_SRC_ID_SEA);
>
> acpi_table_end(linker, &table);
> }
next prev parent reply other threads:[~2024-10-02 13:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 7:03 [PATCH v2 00/15] Prepare GHES driver to support error injection Mauro Carvalho Chehab
2024-10-01 7:03 ` [PATCH v2 01/15] acpi/ghes: get rid of ACPI_HEST_SRC_ID_RESERVED Mauro Carvalho Chehab
2024-10-01 7:03 ` [PATCH v2 02/15] acpi/ghes: simplify acpi_ghes_record_errors() code Mauro Carvalho Chehab
2024-10-01 7:03 ` [PATCH v2 03/15] acpi/ghes: simplify the per-arch caller to build HEST table Mauro Carvalho Chehab
2024-10-02 13:30 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 04/15] acpi/ghes: better handle source_id and notification Mauro Carvalho Chehab
2024-10-02 13:28 ` Igor Mammedov [this message]
2024-10-01 7:03 ` [PATCH v2 05/15] acpi/ghes: Fix acpi_ghes_record_errors() argument Mauro Carvalho Chehab
2024-10-02 13:21 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 06/15] acpi/ghes: Remove a duplicated out of bounds check Mauro Carvalho Chehab
2024-10-01 7:03 ` [PATCH v2 07/15] acpi/ghes: Change the type for source_id Mauro Carvalho Chehab
2024-10-02 12:27 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 08/15] acpi/ghes: Prepare to support multiple sources on ghes Mauro Carvalho Chehab
2024-10-02 12:57 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 09/15] acpi/ghes: make the GHES record generation more generic Mauro Carvalho Chehab
2024-10-02 13:14 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 10/15] acpi/ghes: move offset calculus to a separate function Mauro Carvalho Chehab
2024-10-02 13:20 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 11/15] acpi/ghes: better name GHES memory error function Mauro Carvalho Chehab
2024-10-01 7:03 ` [PATCH v2 12/15] acpi/ghes: don't crash QEMU if ghes GED is not found Mauro Carvalho Chehab
2024-10-02 12:46 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 13/15] acpi/ghes: rename etc/hardware_error file macros Mauro Carvalho Chehab
2024-10-01 7:03 ` [PATCH v2 14/15] acpi/ghes: better name the offset of the hardware error firmware Mauro Carvalho Chehab
2024-10-02 12:38 ` Igor Mammedov
2024-10-01 7:03 ` [PATCH v2 15/15] docs: acpi_hest_ghes: fix documentation for CPER size 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=20241002152809.0dcc4013@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anisinha@redhat.com \
--cc=gengdongjiu1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mst@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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 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).