From: Markus Armbruster <armbru@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3] qemu, qmp: convert do_inject_nmi() to QObject, QError
Date: Wed, 15 Dec 2010 18:39:07 +0100 [thread overview]
Message-ID: <m3tyifylz8.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20101215151411.0f52b692@doriath> (Luiz Capitulino's message of "Wed, 15 Dec 2010 15:14:11 -0200")
Luiz Capitulino <lcapitulino@redhat.com> writes:
> On Wed, 15 Dec 2010 11:49:23 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
>
>> Lai Jiangshan <laijs@cn.fujitsu.com> writes:
>>
>> > Convert do_inject_nmi() to QObject, QError, we need to use it(via libvirt).
>> >
>> > changed from v1
>> > Add document.
>> > Add error handling when the cpu index is invalid.
>> >
>> > changed from v2
>> > use QERR_INVALID_PARAMETER_VALUE as Markus suggest.
>> >
>> > Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
>>
>> A note on commit messages:
>>
>> The commit message should describe the current version of the patch.
>> Don't repeat the subject line in the body.
>>
>> Patch history is very useful for review, but usually uninteresting once
>> the patch is committed. Thus, it's best to put it after the "---"
>> separator.
>>
>> Subsystem tags in the subject line are helpful. But "qemu" doesn't
>> provide any information there :)
>>
>>
>> Regarding the patch:
>>
>> The conversion looks good.
>>
>> The new QMP command is called "inject_nmi", while the existing human
>> monitor command is called "nmi". Luiz asked for this name change. I
>> don't mind. But should we rename the human monitor command for
>> consistency?
>
> I don't think so, we don't need (and maybe don't even want) naming parity
> between QMP and HMP. Remember that one of our mistakes was to couple the two.
Human "nmi" and QMP "inject_nmi" are identical commands, aren't they?
Giving the same things the same name isn't coupling :)
The mistake that matters here was adopting existing human commands for
QMP uncritically.
> Also, Avi asked for more descriptive names in QMP and I agree with him, I
> would even be in favor of calling it inject-non-maskable-interrupt.
I like inject_nmi better than nmi. inject-non-maskable-interrupt is too
long even for QMP.
>> Regardless, the differing command name is worth mentioning in the commit
>> message.
next prev parent reply other threads:[~2010-12-15 17:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 9:49 [PATCH v3] qemu,qmp: convert do_inject_nmi() to QObject, QError Lai Jiangshan
2010-12-15 10:49 ` [Qemu-devel] [PATCH v3] qemu, qmp: " Markus Armbruster
2010-12-15 17:14 ` Luiz Capitulino
2010-12-15 17:39 ` Markus Armbruster [this message]
2010-12-15 17:52 ` Luiz Capitulino
2010-12-15 17:09 ` [PATCH v3] qemu,qmp: " 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
2010-12-16 10:51 ` Avi Kivity
2010-12-16 11:12 ` Luiz Capitulino
2010-12-16 11:47 ` [Qemu-devel] Re: [PATCH v3] qemu, qmp: " 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=m3tyifylz8.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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