From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Igor Mammedov <imammedo@redhat.com>
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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 17/21] tests/acpi: virt: update HEST table to accept two sources
Date: Thu, 27 Feb 2025 16:51:24 +0100 [thread overview]
Message-ID: <20250227165124.221ef1b2@foz.lan> (raw)
In-Reply-To: <20250227141603.3957e78b@imammedo.users.ipa.redhat.com>
Em Thu, 27 Feb 2025 14:16:03 +0100
Igor Mammedov <imammedo@redhat.com> escreveu:
> On Thu, 27 Feb 2025 14:10:38 +0100
> Igor Mammedov <imammedo@redhat.com> wrote:
>
> > On Thu, 27 Feb 2025 12:03:47 +0100
> > Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> >
> > squash this patch into the next one
> >
> > Also at this point there is no visible HEST changes yet, so a soon as you remove
> > white-list without enabling new HEST, the tests should start failing.
> >
> > I suggest to move 20/21 before this patch,
> > as result one would see dsdt and hest diffs when running tests
> > and then you can use rebuild-expected-aml.sh to generate updated
> > tables and update them in one patch (that's what we typically do,
> > we don't split updates in increments).
>
> on top of that,
> it seems the patch doesn't apply for some reason.
Hmm... perhaps the diffstat that I place here (produced by bios-tables-test
output) is causing some confusion when you're trying to apply the patch.
Any suggestions to avoid that?
Thanks,
Mauro
next prev parent reply other threads:[~2025-02-27 15:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 11:03 [PATCH v5 00/21]Change ghes to use HEST-based offsets and add support for error inject Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 01/21] tests/acpi: virt: add an empty HEST file Mauro Carvalho Chehab
2025-02-27 12:02 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 02/21] tests/qtest/bios-tables-test: extend to also check HEST table Mauro Carvalho Chehab
2025-02-27 12:03 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 03/21] tests/acpi: virt: update HEST file with its current data Mauro Carvalho Chehab
2025-02-27 12:03 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 04/21] acpi/ghes: Cleanup the code which gets ghes ged state Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 05/21] acpi/ghes: prepare to change the way HEST offsets are calculated Mauro Carvalho Chehab
2025-02-27 13:25 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 06/21] acpi/ghes: add a firmware file with HEST address Mauro Carvalho Chehab
2025-02-27 13:23 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 07/21] acpi/ghes: Use HEST table offsets when preparing GHES records Mauro Carvalho Chehab
2025-02-27 13:27 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 08/21] acpi/ghes: don't hard-code the number of sources for HEST table Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 09/21] acpi/ghes: add a notifier to notify when error data is ready Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 10/21] acpi/ghes: create an ancillary acpi_ghes_get_state() function Mauro Carvalho Chehab
2025-02-27 11:31 ` Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 11/21] acpi/generic_event_device: Update GHES migration to cover hest addr Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 12/21] acpi/generic_event_device: add logic to detect if HEST addr is available Mauro Carvalho Chehab
2025-02-27 13:33 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 13/21] acpi/generic_event_device: add an APEI error device Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 14/21] tests/acpi: virt: allow acpi table changes at DSDT and HEST tables Mauro Carvalho Chehab
2025-02-27 13:34 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 15/21] arm/virt: Wire up a GED error device for ACPI / GHES Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 16/21] qapi/acpi-hest: add an interface to do generic CPER error injection Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 17/21] tests/acpi: virt: update HEST table to accept two sources Mauro Carvalho Chehab
2025-02-27 13:10 ` Igor Mammedov
2025-02-27 13:16 ` Igor Mammedov
2025-02-27 15:51 ` Mauro Carvalho Chehab [this message]
2025-02-27 15:56 ` Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 18/21] tests/acpi: virt: and update DSDT table to add the new GED device Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 19/21] docs: hest: add new "etc/acpi_table_hest_addr" and update workflow Mauro Carvalho Chehab
2025-02-27 13:21 ` Igor Mammedov
2025-02-27 11:03 ` [PATCH v5 20/21] acpi/generic_event_device.c: enable use_hest_addr for QEMU 10.x Mauro Carvalho Chehab
2025-02-27 11:03 ` [PATCH v5 21/21] scripts/ghes_inject: add a script to generate GHES error inject Mauro Carvalho Chehab
2025-02-27 13:30 ` [PATCH v5 00/21]Change ghes to use HEST-based offsets and add support for " Igor Mammedov
2025-02-27 15:13 ` 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=20250227165124.221ef1b2@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=imammedo@redhat.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).