hw/nmi: Disconnect of vCPU and disentangle Monitor code
v3 cover hw/nmi: Disconnect of vCPU and disentangle Monitor code
- Have s390x always deliver NMI to the first CPU.
- Remove the @cpu_index / @errp arguments from handler.
- Rename API as nmi_trigger() (since not monitor specific).
- Only deliver NMI once
Rationale described by Peter in v1 [*]:
Quoted 10 lines
The current
hw/core/nmi.ccode is a bit odd because it's partly working with acpu_indexand partly not: the code passescpu_indexaround, but in practice for the QMP command the user can't set which CPU to operate on, and for everything except s390 the implementation doesn't care anyway. My impression from the IRC discussion is that it's not really necessary for the S390 that the monitor user be able to specify which CPU to NMI (and in any case you can only do that from the HMP command, not the QMP command, AIUI), so getting rid of that weird inconsistency makes sense to me: and that's what this patchset is doing.
Philippe Mathieu-Daudé (7):
hw/nmi: Use object_child_foreach_recursive() in nmi_children() hw/s390x/virtio-ccw: Always deliver NMI to first CPU hw/nmi: Remove @cpu_index argument from
NMIClass::nmi_monitor_handler()
hw/nmi: Remove @cpu_index argument from nmi_trigger() hw/nmi: Rename nmi_monitor_handler() -> deliver_nmi() hw/nmi: Remove unused @errp argument from deliver_nmi() hw/nmi: Deliver NMI only once
qapi/run-state.json | 6 +++-- include/hw/core/nmi.h | 32 +++++++++++++++++++++++++-- hw/core/nmi.c | 45 ++++++++++---------------------------- hw/hppa/machine.c | 4 ++-- hw/i386/x86.c | 4 ++-- hw/intc/m68k_irqc.c | 4 ++-- hw/ipmi/ipmi.c | 3 +-- hw/m68k/q800-glue.c | 4 ++-- hw/misc/macio/gpio.c | 4 ++-- hw/ppc/pnv.c | 4 ++-- hw/ppc/spapr.c | 4 ++-- hw/s390x/s390-virtio-ccw.c | 8 +++---- hw/watchdog/watchdog.c | 2 +- system/cpus.c | 2 +- hmp-commands.hx | 2 +- 15 files changed, 66 insertions(+), 62 deletions(-)
Signature · 1 line
2.53.0
PATCH v3 1/7 hw/nmi: Use object_child_foreach_recursive() in nmi_children()
From: Philippe Mathieu-Daudé <[email protected]>
Replace object_child_foreach() and recursion by a single object_child_foreach_recursive() call. Propagate the returned value so callers can check it.
--- hw/core/nmi.c | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-)
hw/core/nmi.c +4 -8
@@ -31,8 +31,6 @@ struct do_nmi_s {bool handled; }; -static void nmi_children (Object *o,struct do_nmi_s *ns); -static int do_nmi (Object *o,void *opaque) {struct do_nmi_s *ns = opaque;
@@ -47,14 +45,13 @@ static int do_nmi(Object *o, void *opaque)return -1 ; } } -nmi_children (o, ns);return 0 ; } -static void nmi_children (Object *o,struct do_nmi_s *ns) +static int nmi_children (Object *o,struct do_nmi_s *ns) { -object_child_foreach (o, do_nmi, ns); +return object_child_foreach_recursive (o, do_nmi, ns); }void nmi_monitor_handle (int cpu_index,Error **errp)
@@ -65,10 +62,9 @@ void nmi_monitor_handle(int cpu_index, Error **errp) .handled = false }; -nmi_children (object_get_root (), &ns); -if (ns.handled) { +if (nmi_children (object_get_root (), &ns)) {error_propagate (errp, ns.err); - }else { + }else if (!ns.handled) {error_setg (errp,"machine does not provide NMIs" ); } }
Signature · 1 line
2.53.0
PATCH v3 2/7 hw/s390x/virtio-ccw: Always deliver NMI to first CPU
In reply to Philippe Mathieu-DaudéFrom: Philippe Mathieu-Daudé <[email protected]>
We can trigger NMI from HMP or QMP.
QEMU maps the NMI to the s390x per-CPU 'RESTART' interrupt. Linux guests usually setup this interrupt to trigger kdump or crash. Such crashdump can be triggered in QEMU by HMP "nmi" or QMP "inject-nmi" commands.
Using QMP, since we can not select a particular CPU, the first CPU is used (CPU#0). See the documentation from commit 795dc6e4 ("watchdog: Add new Virtual Watchdog action INJECT-NMI"):
@inject-nmi: a non-maskable interrupt is injected into the
first VCPU (all VCPUS on x86) (since 2.4)
While we can select a particular CPU on HMP, the guest behavior is expected to be the same if using CPU #N or CPU #0. Since always using CPU#0 simplifies API maintainance, update s390_nmi() to deliver NMI to the first CPU.
--- qapi/run-state.json | 6 ++++-- hw/s390x/s390-virtio-ccw.c | 4 +--- hmp-commands.hx | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-)
qapi/run-state.json +4 -2
@@ -317,8 +317,10 @@ # # @none: nothing is done # -# @inject-nmi: a non-maskable interrupt is injected into the first -# VCPU (all VCPUS on x86) (since 2.4) +# @inject-nmi: a non-maskable interrupt is injected (machine +# specific: for example on s390x CCW only the first vCPU +# receives the NMI, but on x86 machines all vCPUs receive +# it). (since 2.4) # # Since: 2.1 ##
hw/s390x/s390-virtio-ccw.c +1 -3
@@ -727,9 +727,7 @@ static HotplugHandler *s390_get_hotplug_handler(MachineState *machine,static void s390_nmi (NMIState *n,int cpu_index,Error **errp) { -CPUState *cs =qemu_get_cpu (cpu_index); - -s390_cpu_restart (S390_CPU (cs)); +s390_cpu_restart (S390_CPU (first_cpu)); }static inline bool machine_get_aes_key_wrap (Object *obj,Error **errp)
hmp-commands.hx +1 -1
@@ -870,7 +870,7 @@ ERST }, SRST ``nmi`` *cpu* - Inject an NMI on the default CPU (x86/s390) or all CPUs (ppc64). + Inject an NMI. ERST {
Signature · 1 line
2.53.0
PATCH v3 3/7 hw/nmi: Remove @cpu_index argument from NMIClass::nmi_monitor_handler()
In reply to Philippe Mathieu-DaudéFrom: Philippe Mathieu-Daudé <[email protected]>
Only s390x was using the 'cpu_index' argument, but since the previous commit it isn't anymore (it use the first cpu). Since this argument is now completely unused, remove it.
--- include/hw/core/nmi.h | 8 +++++++- hw/core/nmi.c | 2 +- hw/hppa/machine.c | 2 +- hw/i386/x86.c | 2 +- hw/intc/m68k_irqc.c | 2 +- hw/m68k/q800-glue.c | 2 +- hw/misc/macio/gpio.c | 2 +- hw/ppc/pnv.c | 2 +- hw/ppc/spapr.c | 2 +- hw/s390x/s390-virtio-ccw.c | 2 +- 10 files changed, 16 insertions(+), 10 deletions(-)
include/hw/core/nmi.h +7 -1
@@ -37,7 +37,13 @@ typedef struct NMIState NMIState;struct NMIClass {InterfaceClass parent_class; -void (*nmi_monitor_handler)(NMIState *n,int cpu_index,Error **errp); +/** +* nmi_monitor_handler: Callback to handle NMI notifications. +* +* @ns: Class #NMIState state +* @errp: pointer to error object +*/ +void (*nmi_monitor_handler)(NMIState *ns,Error **errp); };void nmi_monitor_handle (int cpu_index,Error **errp);
hw/core/nmi.c +1 -1
@@ -40,7 +40,7 @@ static int do_nmi(Object *o, void *opaque)NMIClass *nc =NMI_GET_CLASS (n); ns->handled = true; - nc->nmi_monitor_handler (n, ns->cpu_index, &ns->err); + nc->nmi_monitor_handler (n, &ns->err);if (ns->err) {return -1 ; }
hw/hppa/machine.c +1 -1
@@ -829,7 +829,7 @@ static void hppa_machine_reset(MachineState *ms, ResetType type) cpu[0 ]->env.cmdline_or_bootorder ='c' ; } -static void hppa_nmi (NMIState *n,int cpu_index,Error **errp) +static void hppa_nmi (NMIState *ns,Error **errp) {CPUState *cs;
hw/i386/x86.c +1 -1
@@ -147,7 +147,7 @@ static const CPUArchIdList *x86_possible_cpu_arch_ids(MachineState *ms)return ms->possible_cpus; } -static void x86_nmi (NMIState *n,int cpu_index,Error **errp) +static void x86_nmi (NMIState *ns,Error **errp) {/* cpu index isn't used */ CPUState *cs;
hw/intc/m68k_irqc.c +1 -1
@@ -70,7 +70,7 @@ static void m68k_irqc_instance_init(Object *obj)qdev_init_gpio_in (DEVICE (obj), m68k_set_irq,M68K_IRQC_LEVEL_NUM ); } -static void m68k_nmi (NMIState *n,int cpu_index,Error **errp) +static void m68k_nmi (NMIState *n,Error **errp) {m68k_set_irq (n,M68K_IRQC_LEVEL_7 ,1 ); }
hw/m68k/q800-glue.c +1 -1
@@ -159,7 +159,7 @@ static void glue_auxmode_set_irq(void *opaque, int irq, int level) s->auxmode = level; } -static void glue_nmi (NMIState *n,int cpu_index,Error **errp) +static void glue_nmi (NMIState *n,Error **errp) {GLUEState *s =GLUE (n);
hw/misc/macio/gpio.c +1 -1
@@ -188,7 +188,7 @@ static void macio_gpio_reset(DeviceState *dev)macio_set_gpio (s,1 , true); } -static void macio_gpio_nmi (NMIState *n,int cpu_index,Error **errp) +static void macio_gpio_nmi (NMIState *n,Error **errp) {macio_set_gpio (MACIO_GPIO (n),9 , true);macio_set_gpio (MACIO_GPIO (n),9 , false);
hw/ppc/pnv.c +1 -1
@@ -3552,7 +3552,7 @@ static void pnv_cpu_do_nmi(PnvChip *chip, PowerPCCPU *cpu, void *opaque)async_run_on_cpu (CPU (cpu), pnv_cpu_do_nmi_on_cpu,RUN_ON_CPU_HOST_INT (0 )); } -static void pnv_nmi (NMIState *n,int cpu_index,Error **errp) +static void pnv_nmi (NMIState *ns,Error **errp) {PnvMachineState *pnv =PNV_MACHINE (qdev_get_machine ());int i;
hw/ppc/spapr.c +1 -1
@@ -3550,7 +3550,7 @@ void spapr_do_system_reset_on_cpu(CPUState *cs, run_on_cpu_data arg) } } -static void spapr_nmi (NMIState *n,int cpu_index,Error **errp) +static void spapr_nmi (NMIState *ns,Error **errp) {CPUState *cs;
hw/s390x/s390-virtio-ccw.c +1 -1
@@ -725,7 +725,7 @@ static HotplugHandler *s390_get_hotplug_handler(MachineState *machine,return NULL ; } -static void s390_nmi (NMIState *n,int cpu_index,Error **errp) +static void s390_nmi (NMIState *ns,Error **errp) {s390_cpu_restart (S390_CPU (first_cpu)); }
Signature · 1 line
2.53.0
Re: [PATCH v3 3/7] hw/nmi: Remove @cpu_index argument from NMIClass::nmi_monitor_handler()
Quoted 10 lines · Philippe Mathieu-Daudé
From: Philippe Mathieu-Daudé <[email protected]>
Only s390x was using the '
cpu_index' argument, but since the previous commit it isn't anymore (it use the first cpu). Since this argument is now completely unused, remove it.Signed-off-by Philippe Mathieu-Daudé <[email protected]>Signed-off-by Philippe Mathieu-Daudé <[email protected]>---
thanks
-- PMM
PATCH v3 4/7 hw/nmi: Remove @cpu_index argument from nmi_trigger()
In reply to Philippe Mathieu-DaudéFrom: Philippe Mathieu-Daudé <[email protected]>
nmi_monitor_handle() is not related to the monitor, rename it as nmi_trigger().
Return a boolean value indicating success / failure as recommended by the Error API since commit e3fe3988d7 ("error: Document Error API usage rules").
The 'cpu_index' argument is not used, remove it.
Document nmi_trigger() as suggested by Peter Maydell in
https://lore.kernel.org/qemu-devel/CAFEAcA-yALySmCJLbitCmYpiZKUXJNOavGJG9RYeo8fKqz7gcw@mail.gmail.com/.
--- include/hw/core/nmi.h | 25 ++++++++++++++++++++++++- hw/core/nmi.c | 9 ++++----- hw/ipmi/ipmi.c | 3 +-- hw/watchdog/watchdog.c | 2 +- system/cpus.c | 2 +- 5 files changed, 31 insertions(+), 10 deletions(-)
include/hw/core/nmi.h +24 -1
@@ -46,6 +46,29 @@ struct NMIClass { void (*nmi_monitor_handler)(NMIState *ns, Error **errp); }; -void nmi_monitor_handle (int cpu_index,Error **errp); +/** +* nmi_trigger: Trigger an NMI, in a machine-specific way +* @errp: pointer to error object +* +* This function triggers an NMI, in a machine-specific way. The +* intention is that this should typically trigger a guest kernel +* dump or reboot, and might happen as a result of user request +* from the monitor, watchdog timeouts, and similar events. +* (For example on the x86 PC it triggers an NMI on all CPUs, +* and on s390 it triggers the RESTART interrupt on the first CPU.) +* +* The NMI is triggered by looking for QOM objects which +* implement the TYPE_NMI interface, and calling their nmi_handler +* method. Usually it is the machine model class that implements +* this interface. +* +* Not all machines implement NMI handling; this function +* will return an error if used on a machine which does not +* implement NMIs. +* +* On success, return %true. +* On failure, store an error through @errp and return %false. +*/ +bool nmi_trigger (Error **errp);#endif /* NMI_H */
hw/core/nmi.c +4 -5
@@ -22,11 +22,8 @@#include "qemu/osdep.h" #include "hw/core/nmi.h" #include "qapi/error.h" -#include "qemu/module.h" -#include "monitor/monitor.h" struct do_nmi_s { -int cpu_index;Error *err;bool handled; };
@@ -54,19 +51,21 @@ static int nmi_children(Object *o, struct do_nmi_s *ns)return object_child_foreach_recursive (o, do_nmi, ns); } -void nmi_monitor_handle (int cpu_index,Error **errp) +bool nmi_trigger (Error **errp) {struct do_nmi_s ns = { - .cpu_index = cpu_index, .err =NULL , .handled = false };if (nmi_children (object_get_root (), &ns)) {error_propagate (errp, ns.err); +return false; }else if (!ns.handled) {error_setg (errp,"machine does not provide NMIs" ); +return false; } +return true; }static const TypeInfo nmi_info = {
hw/ipmi/ipmi.c +1 -2
@@ -59,8 +59,7 @@ static int ipmi_do_hw_op(IPMIInterface *s, enum ipmi_op op, int checkonly)if (checkonly) {return 0 ; } -/* We don't care what CPU we use. */ -nmi_monitor_handle (0 ,NULL ); +nmi_trigger (NULL );return 0 ;case IPMI_SHUTDOWN_VIA_ACPI_OVERTEMP :
hw/watchdog/watchdog.c +1 -1
@@ -81,7 +81,7 @@ void watchdog_perform_action(void)case WATCHDOG_ACTION_INJECT_NMI :qapi_event_send_watchdog (WATCHDOG_ACTION_INJECT_NMI ); -nmi_monitor_handle (0 ,NULL ); +nmi_trigger (NULL );break ;default :
system/cpus.c +1 -1
@@ -926,6 +926,6 @@ exit:void qmp_inject_nmi (Error **errp) { -nmi_monitor_handle (monitor_get_cpu_index (monitor_cur ()), errp); +nmi_trigger (errp); }
Signature · 1 line
2.53.0
Re: [PATCH v3 4/7] hw/nmi: Remove @cpu_index argument from nmi_trigger()
Hi
Quoted 132 lines · Philippe Mathieu-Daudé
From: Philippe Mathieu-Daudé <[email protected]>
nmi_monitor_handle()is not related to the monitor, rename it asnmi_trigger().Return a boolean value indicating success / failure as recommended by the Error API since commit
e3fe3988d7("error: Document Error API usage rules").The '
cpu_index' argument is not used, remove it.Document
nmi_trigger()as suggested by Peter Maydell in
https://lore.kernel.org/qemu-devel/CAFEAcA-yALySmCJLbitCmYpiZKUXJNOavGJG9RYeo8fKqz7gcw@mail.gmail.com/.Signed-off-by Philippe Mathieu-Daudé <[email protected]>Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- include/hw/core/nmi.h | 25 ++++++++++++++++++++++++- hw/core/nmi.c | 9 ++++----- hw/ipmi/ipmi.c | 3 +-- hw/watchdog/watchdog.c | 2 +- system/cpus.c | 2 +- 5 files changed, 31 insertions(+), 10 deletions(-)include/hw/core/nmi.h +24
-1@@ -46,6 +46,29 @@ struct NMIClass { void (*nmi_monitor_handler)(NMIState *ns, Error **errp); }; -void nmi_monitor_handle (int cpu_index,Error **errp); +/** +* nmi_trigger: Trigger an NMI, in a machine-specific way +* @errp: pointer to error object +* +* This function triggers an NMI, in a machine-specific way. The +* intention is that this should typically trigger a guest kernel +* dump or reboot, and might happen as a result of user request +* from the monitor, watchdog timeouts, and similar events. +* (For example on the x86 PC it triggers an NMI on all CPUs, +* and on s390 it triggers the RESTART interrupt on the first CPU.) +* +* The NMI is triggered by looking for QOM objects which +* implement the TYPE_NMI interface, and calling their nmi_handler +* method. Usually it is the machine model class that implements +* this interface. +* +* Not all machines implement NMI handling; this function +* will return an error if used on a machine which does not +* implement NMIs. +* +* On success, return %true. +* On failure, store an error through @errp and return %false. +*/ +bool nmi_trigger (Error **errp);#endif /* NMI_H */ hw/core/nmi.c +4
-5@@ -22,11 +22,8 @@#include "qemu/osdep.h" #include "hw/core/nmi.h" #include "qapi/error.h" -#include "qemu/module.h" -#include "monitor/monitor.h" struct do_nmi_s { -int cpu_index;Error *err;bool handled; };@@ -54,19 +51,21 @@ static int nmi_children(Object *o, struct do_nmi_s *ns)return object_child_foreach_recursive (o, do_nmi, ns); } -void nmi_monitor_handle (int cpu_index,Error **errp) +bool nmi_trigger (Error **errp) {struct do_nmi_s ns = { - .cpu_index = cpu_index, .err =NULL , .handled = false };if (nmi_children (object_get_root (), &ns)) {error_propagate (errp, ns.err); +return false; }else if (!ns.handled) {error_setg (errp,"machine does not provide NMIs" ); +return false; } +return true; }static const TypeInfo nmi_info = {hw/ipmi/ipmi.c +1
-2@@ -59,8 +59,7 @@ static int ipmi_do_hw_op(IPMIInterface *s, enum ipmi_op op, int checkonly)if (checkonly) {return 0 ; } -/* We don't care what CPU we use. */ -nmi_monitor_handle (0 ,NULL ); +nmi_trigger (NULL );return 0 ;case IPMI_SHUTDOWN_VIA_ACPI_OVERTEMP :hw/watchdog/watchdog.c +1
-1@@ -81,7 +81,7 @@ void watchdog_perform_action(void)case WATCHDOG_ACTION_INJECT_NMI :qapi_event_send_watchdog (WATCHDOG_ACTION_INJECT_NMI ); -nmi_monitor_handle (0 ,NULL ); +nmi_trigger (NULL );break ;default :system/cpus.c +0
-0
system/cpus.c exit: · line 930
Quoted 6 lines
system/cpus.c +1
-1@@ -926,6 +926,6 @@ exit:void qmp_inject_nmi (Error **errp) { -nmi_monitor_handle (monitor_get_cpu_index (monitor_cur ()), errp); +nmi_trigger (errp); }
This officially drops the current CPU for HMP command too. Just acknowledge it in the commit message, and remove the "*cpu*" documentation in hmp-commands.hx?
Also, can we use one word for "deliver", "trigger", "inject"? or is there any distinction I am missing?
Re: [PATCH v3 4/7] hw/nmi: Remove @cpu_index argument from nmi_trigger()
Quoted 110 lines · Marc-André Lureau
Hi
Quoted 106 lines · Philippe Mathieu-Daudé
From: Philippe Mathieu-Daudé <[email protected]>
nmi_monitor_handle()is not related to the monitor, rename it asnmi_trigger().Return a boolean value indicating success / failure as recommended by the Error API since commit
e3fe3988d7("error: Document Error API usage rules").The '
cpu_index' argument is not used, remove it.Document
nmi_trigger()as suggested by Peter Maydell in
https://lore.kernel.org/qemu-devel/CAFEAcA-yALySmCJLbitCmYpiZKUXJNOavGJG9RYeo8fKqz7gcw@mail.gmail.com/.Signed-off-by Philippe Mathieu-Daudé <[email protected]>Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- include/hw/core/nmi.h | 25 ++++++++++++++++++++++++- hw/core/nmi.c | 9 ++++----- hw/ipmi/ipmi.c | 3 +-- hw/watchdog/watchdog.c | 2 +- system/cpus.c | 2 +- 5 files changed, 31 insertions(+), 10 deletions(-)include/hw/core/nmi.h +28
-3-void nmi_monitor_handle (int cpu_index,Error **errp); +/** +* nmi_trigger: Trigger an NMI, in a machine-specific way +* @errp: pointer to error object +* +* This function triggers an NMI, in a machine-specific way. The +* intention is that this should typically trigger a guest kernel +* dump or reboot, and might happen as a result of user request +* from the monitor, watchdog timeouts, and similar events. +* (For example on the x86 PC it triggers an NMI on all CPUs, +* and on s390 it triggers the RESTART interrupt on the first CPU.) +* +* The NMI is triggered by looking for QOM objects which +* implement the TYPE_NMI interface, and calling their nmi_handler +* method. Usually it is the machine model class that implements +* this interface. +* +* Not all machines implement NMI handling; this function +* will return an error if used on a machine which does not +* implement NMIs. +* +* On success, return %true. +* On failure, store an error through @errp and return %false. +*/ +bool nmi_trigger (Error **errp); -void nmi_monitor_handle (int cpu_index,Error **errp) +bool nmi_trigger (Error **errp) {struct do_nmi_s ns = { - .cpu_index = cpu_index, .err =NULL , .handled = false };if (nmi_children (object_get_root (), &ns)) {error_propagate (errp, ns.err); +return false; }else if (!ns.handled) {error_setg (errp,"machine does not provide NMIs" ); +return false; } +return true; }static const TypeInfo nmi_info = {hw/ipmi/ipmi.c +1
-2@@ -59,8 +59,7 @@ static int ipmi_do_hw_op(IPMIInterface *s, enum ipmi_op op, int checkonly)if (checkonly) {return 0 ; } -/* We don't care what CPU we use. */ -nmi_monitor_handle (0 ,NULL ); +nmi_trigger (NULL );return 0 ;case IPMI_SHUTDOWN_VIA_ACPI_OVERTEMP :hw/watchdog/watchdog.c +1
-1@@ -81,7 +81,7 @@ void watchdog_perform_action(void)case WATCHDOG_ACTION_INJECT_NMI :qapi_event_send_watchdog (WATCHDOG_ACTION_INJECT_NMI ); -nmi_monitor_handle (0 ,NULL ); +nmi_trigger (NULL );break ;default :system/cpus.c +0
-0@@ -926,6 +926,6 @@ exit:
Quoted 9 lines
system/cpus.c exit: · line 930
Quoted 5 lines
system/cpus.c +1
-1void qmp_inject_nmi (Error **errp) { -nmi_monitor_handle (monitor_get_cpu_index (monitor_cur ()), errp); +nmi_trigger (errp); }This officially drops the current CPU for HMP command too. Just acknowledge it in the commit message, and remove the "*cpu*" documentation in hmp-commands.hx?
Ack.
Quoted 3 lines
Also, can we use one word for "deliver", "trigger", "inject"? or is there any distinction I am missing?
Hmm indeed from the monitor perspective we "inject" a NMI.
Watchdog seems to also "inject" with WATCHDOG_ACTION_INJECT_NMI (here my understanding is "raise", but whatever).
I suppose IPMI devices also "raise", but "inject" is acceptable.
$ git grep deliver_nmi hw/i386/x86.c:159: apic_deliver_nmi(cpu->apic_state); hw/intc/apic_common.c:122:void apic_deliver_nmi(APICCommonState *s) include/hw/i386/apic.h:10:void apic_deliver_nmi(APICCommonState *s);
The NMIClass handler then "route" or "deliver" it.
I'll rename as 'nmi_inject' I suppose, better to keep in pair with the QMP command name.
PATCH v3 5/7 hw/nmi: Rename nmi_monitor_handler() -> deliver_nmi()
In reply to Philippe Mathieu-Daudénmi_monitor_handler() is not related to the monitor, rename it as deliver_nmi().
--- include/hw/core/nmi.h | 4 ++-- hw/core/nmi.c | 2 +- hw/hppa/machine.c | 2 +- hw/i386/x86.c | 2 +- hw/intc/m68k_irqc.c | 2 +- hw/m68k/q800-glue.c | 2 +- hw/misc/macio/gpio.c | 2 +- hw/ppc/pnv.c | 2 +- hw/ppc/spapr.c | 2 +- hw/s390x/s390-virtio-ccw.c | 2 +- 10 files changed, 11 insertions(+), 11 deletions(-)
include/hw/core/nmi.h +2 -2
@@ -38,12 +38,12 @@ struct NMIClass {InterfaceClass parent_class;/** -* nmi_monitor_handler: Callback to handle NMI notifications. +* deliver_nmi: Callback to handle NMI notifications. * * @ns: Class #NMIState state * @errp: pointer to error object */ -void (*nmi_monitor_handler)(NMIState *ns,Error **errp); +void (*deliver_nmi)(NMIState *ns,Error **errp); };/**
hw/core/nmi.c +1 -1
@@ -37,7 +37,7 @@ static int do_nmi(Object *o, void *opaque)NMIClass *nc =NMI_GET_CLASS (n); ns->handled = true; - nc->nmi_monitor_handler (n, &ns->err); + nc->deliver_nmi (n, &ns->err);if (ns->err) {return -1 ; }
hw/hppa/machine.c +1 -1
@@ -851,7 +851,7 @@ static void hppa_machine_common_class_init(ObjectClass *oc, const void *data) mc->default_ram_id ="hppa.ram" ; mc->default_nic ="tulip" ; - nc->nmi_monitor_handler = hppa_nmi; + nc->deliver_nmi = hppa_nmi; }static void HP_B160L_machine_init_class_init (ObjectClass *oc,const void *data)
hw/i386/x86.c +1 -1
@@ -389,7 +389,7 @@ static void x86_machine_class_init(ObjectClass *oc, const void *data) mc->get_default_cpu_node_id = x86_get_default_cpu_node_id; mc->possible_cpu_arch_ids = x86_possible_cpu_arch_ids; mc->kvm_type = x86_kvm_type; - nc->nmi_monitor_handler = x86_nmi; + nc->deliver_nmi = x86_nmi; object_class_property_add(oc, X86_MACHINE_SMM, "OnOffAuto", x86_machine_get_smm, x86_machine_set_smm,
hw/intc/m68k_irqc.c +1 -1
@@ -97,7 +97,7 @@ static void m68k_irqc_class_init(ObjectClass *oc, const void *data)InterruptStatsProviderClass *ic =INTERRUPT_STATS_PROVIDER_CLASS (oc);device_class_set_props (dc, m68k_irqc_properties); - nc->nmi_monitor_handler = m68k_nmi; + nc->deliver_nmi = m68k_nmi;device_class_set_legacy_reset (dc, m68k_irqc_reset); dc->vmsd = &vmstate_m68k_irqc; ic->get_statistics = m68k_irqc_get_statistics;
hw/m68k/q800-glue.c +1 -1
@@ -237,7 +237,7 @@ static void glue_class_init(ObjectClass *klass, const void *data) dc->vmsd = &vmstate_glue;device_class_set_props (dc, glue_properties); rc->phases.hold = glue_reset_hold; - nc->nmi_monitor_handler = glue_nmi; + nc->deliver_nmi = glue_nmi; }static const TypeInfo glue_info_types[] = {
hw/misc/macio/gpio.c +1 -1
@@ -201,7 +201,7 @@ static void macio_gpio_class_init(ObjectClass *oc, const void *data)device_class_set_legacy_reset (dc, macio_gpio_reset); dc->vmsd = &vmstate_macio_gpio; - nc->nmi_monitor_handler = macio_gpio_nmi; + nc->deliver_nmi = macio_gpio_nmi; }static const TypeInfo macio_gpio_init_info = {
hw/ppc/pnv.c +1 -1
@@ -3583,7 +3583,7 @@ static void pnv_machine_class_init(ObjectClass *oc, const void *data) mc->default_ram_size =1 * GiB; mc->default_ram_id ="pnv.ram" ; ispc->print_info = pnv_pic_print_info; - nc->nmi_monitor_handler = pnv_nmi; + nc->deliver_nmi = pnv_nmi;object_class_property_add_bool (oc,"hb-mode" , pnv_machine_get_hb, pnv_machine_set_hb);
hw/ppc/spapr.c +1 -1
@@ -4652,7 +4652,7 @@ static void spapr_machine_class_init(ObjectClass *oc, const void *data) mc->nvdimm_supported = true; smc->resize_hpt_default =SPAPR_RESIZE_HPT_ENABLED ; fwc->get_dev_path = spapr_get_fw_dev_path; - nc->nmi_monitor_handler = spapr_nmi; + nc->deliver_nmi = spapr_nmi; vhc->cpu_in_nested = spapr_cpu_in_nested; vhc->deliver_hv_excp = spapr_exit_nested; vhc->hypercall = emulate_spapr_hypercall;
hw/s390x/s390-virtio-ccw.c +1 -1
@@ -830,7 +830,7 @@ static void ccw_machine_class_init(ObjectClass *oc, const void *data) hc->plug = s390_machine_device_plug; hc->unplug_request = s390_machine_device_unplug_request; hc->unplug = s390_machine_device_unplug; - nc->nmi_monitor_handler = s390_nmi; + nc->deliver_nmi = s390_nmi; mc->default_ram_id ="s390.ram" ; mc->default_nic ="virtio-net-ccw" ; dsi->qmp_dump_skeys = s390_qmp_dump_skeys;
Signature · 1 line
2.53.0
PATCH v3 6/7 hw/nmi: Remove unused @errp argument from deliver_nmi()
In reply to Philippe Mathieu-DaudéNot a single handler update @errp. The single user is nmi_trigger() filling with "machine does not provide NMIs". Remove the unused argument from the deliver_nmi() callback, simplifying the methods in hw/core/nmi.c.
--- include/hw/core/nmi.h | 3 +-- hw/core/nmi.c | 32 ++++++-------------------------- hw/hppa/machine.c | 2 +- hw/i386/x86.c | 2 +- hw/intc/m68k_irqc.c | 2 +- hw/m68k/q800-glue.c | 2 +- hw/misc/macio/gpio.c | 2 +- hw/ppc/pnv.c | 2 +- hw/ppc/spapr.c | 2 +- hw/s390x/s390-virtio-ccw.c | 2 +- 10 files changed, 15 insertions(+), 36 deletions(-)
include/hw/core/nmi.h +1 -2
@@ -41,9 +41,8 @@ struct NMIClass {* deliver_nmi: Callback to handle NMI notifications. * * @ns: Class #NMIState state -* @errp: pointer to error object */ -void (*deliver_nmi)(NMIState *ns,Error **errp); +void (*deliver_nmi)(NMIState *ns); };/**
hw/core/nmi.c +6 -26
@@ -23,45 +23,25 @@#include "hw/core/nmi.h" #include "qapi/error.h" -struct do_nmi_s { -Error *err; -bool handled; -}; -static int do_nmi (Object *o,void *opaque) { -struct do_nmi_s *ns = opaque; +bool *handled = opaque;NMIState *n = (NMIState *)object_dynamic_cast (o,TYPE_NMI );if (n) { -NMIClass *nc =NMI_GET_CLASS (n); - - ns->handled = true; - nc->deliver_nmi (n, &ns->err); -if (ns->err) { -return -1 ; - } + *handled = true; +NMI_GET_CLASS (n)->deliver_nmi (n); }return 0 ; } -static int nmi_children (Object *o,struct do_nmi_s *ns) -{ -return object_child_foreach_recursive (o, do_nmi, ns); -} -bool nmi_trigger (Error **errp) { -struct do_nmi_s ns = { - .err =NULL , - .handled = false - }; +bool handled = false; -if (nmi_children (object_get_root (), &ns)) { -error_propagate (errp, ns.err); -return false; - }else if (!ns.handled) { +object_child_foreach_recursive (object_get_root (), do_nmi, &handled); +if (!handled) {error_setg (errp,"machine does not provide NMIs" );return false; }
hw/hppa/machine.c +1 -1
@@ -829,7 +829,7 @@ static void hppa_machine_reset(MachineState *ms, ResetType type) cpu[0 ]->env.cmdline_or_bootorder ='c' ; } -static void hppa_nmi (NMIState *ns,Error **errp) +static void hppa_nmi (NMIState *ns) {CPUState *cs;
hw/i386/x86.c +1 -1
@@ -147,7 +147,7 @@ static const CPUArchIdList *x86_possible_cpu_arch_ids(MachineState *ms)return ms->possible_cpus; } -static void x86_nmi (NMIState *ns,Error **errp) +static void x86_nmi (NMIState *ns) {/* cpu index isn't used */ CPUState *cs;
hw/intc/m68k_irqc.c +1 -1
@@ -70,7 +70,7 @@ static void m68k_irqc_instance_init(Object *obj)qdev_init_gpio_in (DEVICE (obj), m68k_set_irq,M68K_IRQC_LEVEL_NUM ); } -static void m68k_nmi (NMIState *n,Error **errp) +static void m68k_nmi (NMIState *n) {m68k_set_irq (n,M68K_IRQC_LEVEL_7 ,1 ); }
hw/m68k/q800-glue.c +1 -1
@@ -159,7 +159,7 @@ static void glue_auxmode_set_irq(void *opaque, int irq, int level) s->auxmode = level; } -static void glue_nmi (NMIState *n,Error **errp) +static void glue_nmi (NMIState *n) {GLUEState *s =GLUE (n);
hw/misc/macio/gpio.c +1 -1
@@ -188,7 +188,7 @@ static void macio_gpio_reset(DeviceState *dev)macio_set_gpio (s,1 , true); } -static void macio_gpio_nmi (NMIState *n,Error **errp) +static void macio_gpio_nmi (NMIState *n) {macio_set_gpio (MACIO_GPIO (n),9 , true);macio_set_gpio (MACIO_GPIO (n),9 , false);
hw/ppc/pnv.c +1 -1
@@ -3552,7 +3552,7 @@ static void pnv_cpu_do_nmi(PnvChip *chip, PowerPCCPU *cpu, void *opaque)async_run_on_cpu (CPU (cpu), pnv_cpu_do_nmi_on_cpu,RUN_ON_CPU_HOST_INT (0 )); } -static void pnv_nmi (NMIState *ns,Error **errp) +static void pnv_nmi (NMIState *ns) {PnvMachineState *pnv =PNV_MACHINE (qdev_get_machine ());int i;
hw/ppc/spapr.c +1 -1
@@ -3550,7 +3550,7 @@ void spapr_do_system_reset_on_cpu(CPUState *cs, run_on_cpu_data arg) } } -static void spapr_nmi (NMIState *ns,Error **errp) +static void spapr_nmi (NMIState *ns) {CPUState *cs;
hw/s390x/s390-virtio-ccw.c +1 -1
@@ -725,7 +725,7 @@ static HotplugHandler *s390_get_hotplug_handler(MachineState *machine,return NULL ; } -static void s390_nmi (NMIState *ns,Error **errp) +static void s390_nmi (NMIState *ns) {s390_cpu_restart (S390_CPU (first_cpu)); }
Signature · 1 line
2.53.0
Re: [PATCH v3 6/7] hw/nmi: Remove unused @errp argument from deliver_nmi()
Quoted 8 lines · Philippe Mathieu-Daudé
Not a single handler update @errp. The single user is
nmi_trigger()filling with "machine does not provide NMIs". Remove the unused argument from thedeliver_nmi()callback, simplifying the methods inhw/core/nmi.c.Signed-off-by Philippe Mathieu-Daudé <[email protected]>---
thanks
-- PMM
PATCH v3 7/7 hw/nmi: Deliver NMI only once
In reply to Philippe Mathieu-DaudéUse the first handler available to deliver NMI only once. If anothers handlers are available, no need to keep delivering.
--- hw/core/nmi.c | 2 ++ 1 file changed, 2 insertions(+)
hw/core/nmi.c +2 -0
@@ -31,6 +31,8 @@ static int do_nmi(Object *o, void *opaque)if (n) { *handled = true;NMI_GET_CLASS (n)->deliver_nmi (n); +/* We only need to deliver NMI once */ +return 1 ; }return 0 ;
Signature · 1 line
2.53.0
Re: [PATCH v3 7/7] hw/nmi: Deliver NMI only once
Quoted 15 lines · Philippe Mathieu-Daudé
Use the first handler available to deliver NMI only once. If anothers handlers are available, no need to keep delivering.
Suggested-by Peter Maydell <[email protected]>Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/core/nmi.c | 2 ++ 1 file changed, 2 insertions(+)hw/core/nmi.c +0
-0
hw/core/nmi.c static int do_nmi(Object *o, void *opaque) · line 38
Quoted 8 lines
hw/core/nmi.c +2
-0@@ -31,6 +31,8 @@ static int do_nmi(Object *o, void *opaque)if (n) { *handled = true;NMI_GET_CLASS (n)->deliver_nmi (n); +/* We only need to deliver NMI once */ +return 1 ; }return 0 ;
Looking back at my review comments on v1 of this series, I think we could clarify the comment / commit message a bit. Commit message:
We only expect one device in the system to implement the TYPE_NMI interface (typically the machine, but in a few cases for e.g. m68k and ppc this is an interrupt controller or similar device); so we don't need to keep walking the whole QOM tree once we've found it. As no machine type creates more than one object implementing TYPE_NMI, this is not a behaviour change.
and comment:
/*
* We expect only one object to implement TYPE_NMI, so once
* we've asked it to deliver the NMI we can stop looking. */
With that
thanks
-- PMM
Re: [PATCH v3 7/7] hw/nmi: Deliver NMI only once
Quoted 40 lines · Peter Maydell
Quoted 15 lines · Philippe Mathieu-Daudé
Use the first handler available to deliver NMI only once. If anothers handlers are available, no need to keep delivering.
Suggested-by Peter Maydell <[email protected]>Signed-off-by Philippe Mathieu-Daudé <[email protected]>--- hw/core/nmi.c | 2 ++ 1 file changed, 2 insertions(+)hw/core/nmi.c +0
-0hw/core/nmi.c static int do_nmi(Object *o, void *opaque) · line 38
Quoted 8 lines
hw/core/nmi.c +2
-0@@ -31,6 +31,8 @@ static int do_nmi(Object *o, void *opaque)if (n) { *handled = true;NMI_GET_CLASS (n)->deliver_nmi (n); +/* We only need to deliver NMI once */ +return 1 ; }return 0 ;Looking back at my review comments on v1 of this series, I think we could clarify the comment / commit message a bit. Commit message:
We only expect one device in the system to implement the
TYPE_NMIinterface (typically the machine, but in a few cases for e.g. m68k and ppc this is an interrupt controller or similar device); so we don't need to keep walking the whole QOM tree once we've found it. As no machine type creates more than one object implementingTYPE_NMI, this is not a behaviour change.and comment:
Quoted 8 lines
/*
* We expect only one object to implementTYPE_NMI, so once
* we've asked it to deliver the NMI we can stop looking. */With that
Reviewed-by Peter Maydell <[email protected]>
Thanks for the wording help!