From: Luiz Capitulino <lcapitulino@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, aliguori@us.ibm.com,
Markus Armbruster <armbru@redhat.com>,
kvm@vger.kernel.org, Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: [Qemu-devel] Re: [PATCH v3] qemu, qmp: convert do_inject_nmi() to QObject, QError
Date: Thu, 16 Dec 2010 08:48:15 -0200 [thread overview]
Message-ID: <20101216084815.3ca77188@doriath> (raw)
In-Reply-To: <4D09D5EA.7070000@redhat.com>
On Thu, 16 Dec 2010 11:03:38 +0200
Avi Kivity <avi@redhat.com> wrote:
> On 12/15/2010 08:00 PM, Luiz Capitulino wrote:
> > > >
> > > > Looks like a GUI feature to me,
> > >
> > > Really? Can't see how you can build "NMI to all CPUs" from "NMI this
> > > CPU". Or am I misunderstanding you?
> >
> > I guess so. Avi referred to 'nmi button on many machines', I assumed he
> > meant a virtual machine GUI, am I wrong?
>
> I meant a real machine's GUI (it's a physical button you can press with
> your finger, if you have thin fingers).
Ok, I didn't know that, but I had another idea: the command could accept
either a single cpu index or a list:
{ "execute": "inject-nmi", "arguments": { "cpus": 2 } }
{ "execute": "inject-nmi", "arguments": { "cpus": [1, 2, 3, 4] } }
This has the feature of injecting the nmi in just some cpus, although I'm
not sure this is going to be desired/useful.
If we agree on this we'll have to wait because the monitor doesn't currently
support "hybrid" arguments.
next prev parent reply other threads:[~2010-12-16 10:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 9:49 [Qemu-devel] [PATCH v3] qemu, qmp: convert do_inject_nmi() to QObject, QError Lai Jiangshan
2010-12-15 10:49 ` Markus Armbruster
2010-12-15 17:14 ` Luiz Capitulino
2010-12-15 17:39 ` Markus Armbruster
2010-12-15 17:52 ` Luiz Capitulino
2010-12-15 17:09 ` [Qemu-devel] " Luiz Capitulino
2010-12-15 17:18 ` Avi Kivity
2010-12-15 17:26 ` Luiz Capitulino
2010-12-15 17:45 ` Markus Armbruster
2010-12-15 18:00 ` Luiz Capitulino
2010-12-16 9:03 ` Avi Kivity
2010-12-16 10:48 ` Luiz Capitulino [this message]
2010-12-16 10:51 ` Avi Kivity
2010-12-16 11:12 ` Luiz Capitulino
2010-12-16 11:47 ` Markus Armbruster
2010-12-16 12:50 ` Avi Kivity
2010-12-16 13:09 ` Luiz Capitulino
2010-12-16 13:11 ` Avi Kivity
2010-12-16 13:17 ` Luiz Capitulino
2010-12-17 6:20 ` Lai Jiangshan
2010-12-17 11:22 ` Luiz Capitulino
2010-12-17 15:25 ` Avi Kivity
2010-12-20 6:09 ` Lai Jiangshan
2011-01-03 13:46 ` Luiz Capitulino
2010-12-16 9:42 ` Markus Armbruster
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=20101216084815.3ca77188@doriath \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=qemu-devel@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).