From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Igor Mammedov <imammedo@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Shiju Jose <shiju.jose@huawei.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Ani Sinha <anisinha@redhat.com>,
Dongjiu Geng <gengdongjiu1@gmail.com>,
Eduardo Habkost <eduardo@habkost.net>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Richard Henderson <richard.henderson@linaro.org>,
Shannon Zhao <shannon.zhaosl@gmail.com>
Subject: [PATCH RFC 0/3] Attempt to add GHES for x86
Date: Tue, 4 Mar 2025 14:30:55 +0100 [thread overview]
Message-ID: <cover.1741094512.git.mchehab+huawei@kernel.org> (raw)
Hi Igor,
This patch series comes after:
https://lore.kernel.org/qemu-devel/cover.1740903110.git.mchehab+huawei@kernel.org/
I'm basically trying to add support for error injection for x86,
without success so far.
On x86, the notification mechanism is different: it is via QMP.
Yet, from what I saw on Linux implementation, it works on
a similar way to GED. So, I ended implementing a notification
via GED.
HEST table build seems to be working OK on it, and the
error injection notification for x86 is called. Yet, OSPM is not
receiving any notifications.
Could you help me figuring out what are the missing bits?
PS.: there are some things at the code that require polishing,
plus there are some extra printf() there to help debugging.
Finally, we would need to add x86 CPU error event at the
ghes script, but I'd like to have at least something that the
OSPM receives before improving it further.
It can be tested with:
$ ./scripts/ghes_inject.py arm
(Ok, this would be generating an ARM processor event , but
I guess Linux would at least mark the event as read, even if
it doesn't recognize it)
Mauro Carvalho Chehab (3):
acpi/ghes: move use_hest_addr out of acpi_build_hest()
hw/i186: add support for HEST table with SCI
Add a GED device for RAS notification
hw/acpi/ghes.c | 16 ++++-----
hw/arm/virt-acpi-build.c | 12 ++++---
hw/i386/Kconfig | 1 +
hw/i386/acpi-build.c | 75 ++++++++++++++++++++++++++++++++++++++++
hw/i386/pc.c | 41 ++++++++++++++++++++++
include/hw/acpi/ghes.h | 25 +++++++-------
include/hw/i386/pc.h | 5 +++
include/hw/i386/x86.h | 2 ++
8 files changed, 153 insertions(+), 24 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-04 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 13:30 Mauro Carvalho Chehab [this message]
2025-03-04 13:30 ` [PATCH RFC 1/3] acpi/ghes: move use_hest_addr out of acpi_build_hest() Mauro Carvalho Chehab
2025-05-30 14:35 ` Igor Mammedov
2025-03-04 13:30 ` [PATCH RFC 2/3] hw/i186: add support for HEST table with SCI Mauro Carvalho Chehab
2025-03-04 13:30 ` [PATCH RFC 3/3] Add a GED device for RAS notification Mauro Carvalho Chehab
2025-04-04 12:19 ` [PATCH RFC 0/3] Attempt to add GHES for x86 Igor Mammedov
2025-05-30 14:41 ` 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=cover.1741094512.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=anisinha@redhat.com \
--cc=eduardo@habkost.net \
--cc=gengdongjiu1@gmail.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shannon.zhaosl@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.