From: "Bjørn Mork" <bjorn@mork.no>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] kvm: add kvm version to the "info kvm" monitor command
Date: Thu, 30 Jul 2009 10:13:40 +0200 [thread overview]
Message-ID: <873a8e611n.fsf@nemi.mork.no> (raw)
In-Reply-To: <4A70B7F6.3060706@codemonkey.ws> (Anthony Liguori's message of "Wed, 29 Jul 2009 15:58:30 -0500")
Anthony Liguori <anthony@codemonkey.ws> writes:
> Bjørn Mork wrote:
>> There isn't a one-to-one mapping between the KVM version and
>> the QEMU version output from "info version". Complete the
>> picture by adding the KVM version to the existing "info kvm"
>> monitor command.
>>
>> (qemu) info kvm
>> kvm support: enabled
>> kvm version: kvm-85
>>
>
> info version will tell you the kvm version.
It will? Ah, right. I see that QEMU_PKGVERSION has been added to it.
Weird. I did attempt to add the KVM version to "info version" a while
ago, but this was (rightfully) rejected due to the monitor command
stability requirements and the fact that it would affect non-KVM usage
too.
Well, I guess my extended usage of "info kvm" isn't necessary anymore.
But it would IMHO still be useful to define the ouput as a variable
number of lines of 'name: value' sets. I realise that we can't know for
sure that this won't break any parser anywhere, but such bugs should be
fairly easy to fix for those affected, if anyone.
Bjørn
prev parent reply other threads:[~2009-07-30 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 11:03 [Qemu-devel] [PATCH] kvm: add kvm version to the "info kvm" monitor command Bjørn Mork
2009-07-29 18:48 ` Luiz Capitulino
2009-07-29 20:48 ` Glauber Costa
2009-07-29 21:23 ` Luiz Capitulino
2009-07-29 20:58 ` Anthony Liguori
2009-07-30 8:13 ` Bjørn Mork [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=873a8e611n.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=anthony@codemonkey.ws \
--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).