From: Blue Swirl <blauwirbel@gmail.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: laijs@cn.fujitsu.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3]: QMP: Introduce inject-nmi command
Date: Sat, 30 Apr 2011 09:33:15 +0300 [thread overview]
Message-ID: <BANLkTi=3K2t1H-nuq4fp_eRTLKiTKjaTXg@mail.gmail.com> (raw)
In-Reply-To: <1304116821-18201-1-git-send-email-lcapitulino@redhat.com>
On Sat, Apr 30, 2011 at 1:40 AM, Luiz Capitulino <lcapitulino@redhat.com> wrote:
> This series introduces the inject-nmi command for QMP, which sends an
> NMI to _all_ guest's CPUs.
>
> Also note that this series changes the human monitor nmi command to use
> the QMP implementation, which means that it now has a DIFFERENT behavior.
> Please, check patch 3/3 for details.
As discussed earlier, please change the QMP version for future
expandability so that instead of single command 'inject-nmi', 'inject'
takes parameter 'nmi'. HMP command 'nmi' can remain for now, but
'inject' should be added.
next prev parent reply other threads:[~2011-04-30 6:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:40 [Qemu-devel] [PATCH 0/3]: QMP: Introduce inject-nmi command Luiz Capitulino
2011-04-29 22:40 ` [Qemu-devel] [PATCH 1/3] QMP: QError: New QERR_UNSUPPORTED Luiz Capitulino
2011-04-29 22:40 ` [Qemu-devel] [PATCH 2/3] QMP: add inject-nmi qmp command Luiz Capitulino
2011-04-29 22:40 ` [Qemu-devel] [PATCH 3/3] HMP: Use QMP inject nmi implementation Luiz Capitulino
2011-04-30 6:33 ` Blue Swirl [this message]
2011-05-02 15:57 ` [Qemu-devel] [PATCH 0/3]: QMP: Introduce inject-nmi command Luiz Capitulino
2011-05-04 19:28 ` Blue Swirl
2011-05-06 9:08 ` Markus Armbruster
2011-05-06 14:55 ` Luiz Capitulino
2011-05-06 15:36 ` Blue Swirl
2011-05-09 13:32 ` Luiz Capitulino
2011-05-26 17:25 ` Markus Armbruster
2011-05-26 19:23 ` Blue Swirl
2011-05-27 14:04 ` Luiz Capitulino
2011-05-27 14:55 ` Anthony Liguori
2011-05-27 15:43 ` Luiz Capitulino
2011-05-27 16:26 ` Markus Armbruster
2011-05-27 17:17 ` Blue Swirl
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='BANLkTi=3K2t1H-nuq4fp_eRTLKiTKjaTXg@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=armbru@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=lcapitulino@redhat.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).