From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-s390x@nongnu.org, qemu-ppc@nongnu.org,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH 0/4] hw/nmi: Remove @cpu_index argument
Date: Tue, 20 Feb 2024 21:05:20 +0100 [thread overview]
Message-ID: <9d357d62-edd7-4de7-9ada-bd0f75d32112@linaro.org> (raw)
In-Reply-To: <f4a6492b-cff4-439d-8f34-cdf04cb747ee@redhat.com>
On 20/2/24 16:19, Thomas Huth wrote:
> On 20/02/2024 16.08, Philippe Mathieu-Daudé wrote:
>> Have s390x always deliver NMI to the first CPU,
>> remove the @cpu_index argument from handler,
>> rename API as nmi_trigger() (not monitor specific).
>
> Could you please add some rationale here why this is needed / desired?
Heterogeneous machines, a NMI have to reach all NMI-aware HW.
See also "Remove cpu_interrupt() from hw/":
https://lore.kernel.org/qemu-devel/20240220192625.17944-1-philmd@linaro.org/
next prev parent reply other threads:[~2024-02-20 20:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 15:08 [PATCH 0/4] hw/nmi: Remove @cpu_index argument Philippe Mathieu-Daudé
2024-02-20 15:08 ` [PATCH 1/4] hw/nmi: Use object_child_foreach_recursive() in nmi_children() Philippe Mathieu-Daudé
2024-03-20 13:09 ` Peter Maydell
2024-02-20 15:08 ` [PATCH 2/4] hw/s390x/virtio-ccw: Always deliver NMI to first CPU Philippe Mathieu-Daudé
2024-03-20 13:16 ` Peter Maydell
2024-03-20 14:12 ` David Hildenbrand
2024-02-20 15:08 ` [PATCH 3/4] hw/nmi: Remove @cpu_index argument from NMIClass::nmi_handler() Philippe Mathieu-Daudé
2024-03-20 13:23 ` Peter Maydell
2024-03-20 16:47 ` Philippe Mathieu-Daudé
2024-03-20 19:05 ` Markus Armbruster
2024-03-20 19:39 ` Peter Maydell
2024-02-20 15:08 ` [PATCH 4/4] hw/nmi: Remove @cpu_index argument from nmi_trigger() Philippe Mathieu-Daudé
2024-03-20 13:34 ` Peter Maydell
2024-02-20 15:19 ` [PATCH 0/4] hw/nmi: Remove @cpu_index argument Thomas Huth
2024-02-20 20:05 ` Philippe Mathieu-Daudé [this message]
2024-03-20 11:19 ` Philippe Mathieu-Daudé
2024-03-20 11:44 ` Mark Burton
2024-03-20 12:00 ` Peter Maydell
2024-03-20 12:31 ` Mark Burton
2024-03-20 13:55 ` Peter Maydell
2024-03-20 14:09 ` Mark Burton
2024-03-20 15:00 ` Peter Maydell
2024-03-20 15:40 ` Mark Burton
2024-03-22 14:08 ` Cédric Le Goater
2024-03-22 14:55 ` Peter Maydell
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=9d357d62-edd7-4de7-9ada-bd0f75d32112@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).