public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Shiju Jose <shiju.jose@huawei.com>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org,
	Ani Sinha <anisinha@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 05/13] acpi/generic_event_device: Update GHES migration to cover hest addr
Date: Wed, 29 Jan 2025 15:17:47 +0100	[thread overview]
Message-ID: <20250129151747.4b8a7691@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <e0a95da158091e77642eaad9cdbbd7377d257980.1738137123.git.mchehab+huawei@kernel.org>

On Wed, 29 Jan 2025 09:04:11 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:

> The GHES migration logic at GED should now support HEST table
                           ^^
typo?? Should've it been 'as'?


> location too.
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
>  hw/acpi/generic_event_device.c | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
> 
> diff --git a/hw/acpi/generic_event_device.c b/hw/acpi/generic_event_device.c
> index c85d97ca3776..5346cae573b7 100644
> --- a/hw/acpi/generic_event_device.c
> +++ b/hw/acpi/generic_event_device.c
> @@ -386,6 +386,34 @@ static const VMStateDescription vmstate_ghes_state = {
>      }
>  };
>  
> +static const VMStateDescription vmstate_hest = {
> +    .name = "acpi-hest",
> +    .version_id = 1,
> +    .minimum_version_id = 1,
> +    .fields = (const VMStateField[]) {
> +        VMSTATE_UINT64(hest_addr_le, AcpiGhesState),
> +        VMSTATE_END_OF_LIST()
> +    },
> +};
> +
> +static bool hest_needed(void *opaque)
> +{
> +    AcpiGedState *s = opaque;
> +    return s->ghes_state.hest_addr_le;
> +}
> +
> +static const VMStateDescription vmstate_hest_state = {
> +    .name = "acpi-ged/hest",
> +    .version_id = 1,
> +    .minimum_version_id = 1,
> +    .needed = hest_needed,
> +    .fields = (const VMStateField[]) {
> +        VMSTATE_STRUCT(ghes_state, AcpiGedState, 1,
> +                       vmstate_hest, AcpiGhesState),
> +        VMSTATE_END_OF_LIST()
> +    }
> +};
> +
>  static const VMStateDescription vmstate_acpi_ged = {
>      .name = "acpi-ged",
>      .version_id = 1,
> @@ -398,6 +426,7 @@ static const VMStateDescription vmstate_acpi_ged = {
>          &vmstate_memhp_state,
>          &vmstate_cpuhp_state,
>          &vmstate_ghes_state,
> +        &vmstate_hest_state,
>          NULL
>      }
>  };


  reply	other threads:[~2025-01-29 14:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29  8:04 [PATCH v2 00/13] Change ghes to use HEST-based offsets and add support for error inject Mauro Carvalho Chehab
2025-01-29  8:04 ` [PATCH v2 01/13] acpi/ghes: Prepare to support multiple sources on ghes Mauro Carvalho Chehab
2025-01-29 13:15   ` Igor Mammedov
2025-01-29  8:04 ` [PATCH v2 02/13] tests/acpi: virt: allow acpi table changes for a new table: HEST Mauro Carvalho Chehab
2025-01-29 15:03   ` Igor Mammedov
2025-01-30 13:03     ` Mauro Carvalho Chehab
2025-01-30 14:38       ` Igor Mammedov
2025-01-31 16:18         ` Mauro Carvalho Chehab
2025-01-29  8:04 ` [PATCH v2 03/13] acpi/ghes: add a firmware file with HEST address Mauro Carvalho Chehab
2025-01-29 15:23   ` Igor Mammedov
2025-01-31 16:13     ` Mauro Carvalho Chehab
2025-01-29  8:04 ` [PATCH v2 04/13] acpi/ghes: Use HEST table offsets when preparing GHES records Mauro Carvalho Chehab
2025-01-29 14:14   ` Igor Mammedov
2025-01-29  8:04 ` [PATCH v2 05/13] acpi/generic_event_device: Update GHES migration to cover hest addr Mauro Carvalho Chehab
2025-01-29 14:17   ` Igor Mammedov [this message]
2025-01-29  8:04 ` [PATCH v2 06/13] acpi/generic_event_device: add logic to detect if HEST addr is available Mauro Carvalho Chehab
2025-01-29 14:46   ` Igor Mammedov
2025-01-29  8:04 ` [PATCH v2 07/13] acpi/ghes: add a notifier to notify when error data is ready Mauro Carvalho Chehab
2025-01-29  8:04 ` [PATCH v2 08/13] acpi/ghes: Cleanup the code which gets ghes ged state Mauro Carvalho Chehab
2025-01-29 14:55   ` Igor Mammedov
2025-01-30 13:44     ` Mauro Carvalho Chehab
2025-01-30 14:48       ` Igor Mammedov
2025-01-29  8:04 ` [PATCH v2 09/13] acpi/generic_event_device: add an APEI error device Mauro Carvalho Chehab
2025-01-29 14:58   ` Igor Mammedov
2025-01-29  8:04 ` [PATCH v2 10/13] arm/virt: Wire up a GED error device for ACPI / GHES Mauro Carvalho Chehab
2025-01-29  8:04 ` [PATCH v2 11/13] qapi/acpi-hest: add an interface to do generic CPER error injection Mauro Carvalho Chehab
2025-01-29  8:04 ` [PATCH v2 12/13] tests/acpi: virt: add a HEST table to aarch64 virt and update DSDT Mauro Carvalho Chehab
2025-01-29 15:29   ` Igor Mammedov
2025-01-31 15:49     ` Mauro Carvalho Chehab
2025-01-31 16:32       ` Igor Mammedov
2025-01-29  8:04 ` [PATCH v2 13/13] scripts/ghes_inject: add a script to generate GHES error inject Mauro Carvalho Chehab
2025-01-29 15:11   ` Igor Mammedov

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=20250129151747.4b8a7691@imammedo.users.ipa.redhat.com \
    --to=imammedo@redhat.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=anisinha@redhat.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 \
    --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