qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Glauber Costa <glommer@gmail.com>
Cc: qemu-devel@nongnu.org, "Bjørn Mork" <bjorn@mork.no>
Subject: Re: [Qemu-devel] [PATCH] kvm: add kvm version to the "info kvm" monitor command
Date: Wed, 29 Jul 2009 18:23:00 -0300	[thread overview]
Message-ID: <20090729182300.4cdb7be8@doriath> (raw)
In-Reply-To: <5d6222a80907291348r3c25c802if1b844f3bdae11e3@mail.gmail.com>

On Wed, 29 Jul 2009 17:48:13 -0300
Glauber Costa <glommer@gmail.com> wrote:

> On Wed, Jul 29, 2009 at 3:48 PM, Luiz Capitulino<lcapitulino@redhat.com> wrote:
> > On Wed, 29 Jul 2009 13:03:38 +0200
> > Bjørn Mork <bjorn@mork.no> 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
> >
> >  Doesn't seem a good idea, as this is considered a stable protocol.
> >
> >  Either, we should check current users or add 'info kvm-version'.
> 
> can't see why. We recently added information to info migrate, and many others.
> If we are using a new line, shouldn't matter, since it is expected that parsers
> for those things would be line based.

 I don't think this is a safe assumption if you take it literally
for all the commands. If I remember correctly, libvirt for example,
expects the string '(qemu)' as a meaning of 'command executed',
in this case anything different could cause problems.

 I would have to check the code to be certain, though. But will
not matter anyway, if 'info kvm' has no users.

> Not only I'd like to see this, I would also like to see information of
> kvm itself being
> more verbose, like whether or not we have in kernel irqchip/pit

 Yes, this is really useful. I'm just concerned with current
users and when I started working on the monitor protocol people have
clearly expressed their concern on not changing commands output.

 I also should add that I would be extremely happy to find out
that monitor's output could be changed. :)

  reply	other threads:[~2009-07-29 21:23 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 [this message]
2009-07-29 20:58 ` Anthony Liguori
2009-07-30  8:13   ` Bjørn Mork

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=20090729182300.4cdb7be8@doriath \
    --to=lcapitulino@redhat.com \
    --cc=bjorn@mork.no \
    --cc=glommer@gmail.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).