From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v8 0/5] cpus: Add generic "nmi" monitor command support
Date: Mon, 25 Aug 2014 13:24:42 +0200 [thread overview]
Message-ID: <53FB1CFA.4000309@redhat.com> (raw)
In-Reply-To: <1408536997-2075-1-git-send-email-aik@ozlabs.ru>
Il 20/08/2014 14:16, Alexey Kardashevskiy ha scritto:
> This adds an "nmi" monitor command handler per CPUs.
> x86, s390 and ppc CPUS are supported.
>
> Please comment. Thanks.
>
> Changes:
> v8:
> * adjusted commit log for s390 patch
> * fixed missing "static" in 1/4
>
> v7:
> * fixed typenames, function names, copyrights
> * s390x QOM'ed for later addition of the NMI interface
> * Since none of x86 machines is QOM'ed, postpone migration to new interface for x86
>
> v6:
> * back 5 steps and make it an interface again
>
> v5:
> * added Error** to the callback
> * fixed some comments
>
> v4:
> * now it is not nmi() but nmi_monitor_handler() to avoid confusion
>
> v3:
> * patches reorganized
> * comments from v2 addressed, more details are in individual commit logs
>
> v2:
> * moved from machine interface to CPUClass callback
> * s390 and x86 moved to target-s390/target-i386
> * x86 handler delivers to the current CPU only now
>
>
>
>
> Alexey Kardashevskiy (5):
> cpus: Define callback for QEMU "nmi" command
> s390x: Convert QEMUMachine to MachineClass
> s390x: Migrate to new NMI interface
> spapr: Add support for new NMI interface
> pc_piix: Migrate to new NMI interface
>
> cpus.c | 31 ++---------------
> hmp-commands.hx | 6 ++--
> hw/core/Makefile.objs | 1 +
> hw/core/nmi.c | 84 ++++++++++++++++++++++++++++++++++++++++++++++
> hw/i386/pc_piix.c | 42 +++++++++++++++++++++++
> hw/ppc/spapr.c | 21 ++++++++++++
> hw/s390x/s390-virtio-ccw.c | 49 ++++++++++++++++++---------
> hw/s390x/s390-virtio.c | 59 ++++++++++++++++++++++----------
> hw/s390x/s390-virtio.h | 3 ++
> include/hw/nmi.h | 49 +++++++++++++++++++++++++++
> qapi-schema.json | 4 +--
> qmp-commands.hx | 3 +-
> target-ppc/cpu-qom.h | 1 +
> target-ppc/excp_helper.c | 8 +++++
> 14 files changed, 291 insertions(+), 70 deletions(-)
> create mode 100644 hw/core/nmi.c
> create mode 100644 include/hw/nmi.h
>
Applying patches 1-4 to uq/master. PC will wait for the QOM machine
conversion.
Paolo
prev parent reply other threads:[~2014-08-25 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 12:16 [Qemu-devel] [PATCH v8 0/5] cpus: Add generic "nmi" monitor command support Alexey Kardashevskiy
2014-08-20 12:16 ` [Qemu-devel] [PATCH v8 1/5] cpus: Define callback for QEMU "nmi" command Alexey Kardashevskiy
2014-08-20 12:16 ` [Qemu-devel] [PATCH v8 2/5] s390x: Convert QEMUMachine to MachineClass Alexey Kardashevskiy
2014-08-20 12:16 ` [Qemu-devel] [PATCH v8 3/5] s390x: Migrate to new NMI interface Alexey Kardashevskiy
2014-08-20 12:16 ` [Qemu-devel] [PATCH v8 4/5] spapr: Add support for " Alexey Kardashevskiy
2014-08-20 12:16 ` [Qemu-devel] [PATCH v8 5/5] pc_piix: Migrate to " Alexey Kardashevskiy
2014-08-25 11:24 ` Paolo Bonzini [this message]
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=53FB1CFA.4000309@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=cornelia.huck@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).