All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Dor Laor <dlaor@redhat.com>,
	ajax@redhat.com, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER
Date: Thu, 28 May 2009 04:44:33 -0500	[thread overview]
Message-ID: <4A1E5D01.6000005@us.ibm.com> (raw)
In-Reply-To: <1243503206.4046.56.camel@blaa>

Mark McLoughlin wrote:
> On Wed, 2009-05-27 at 17:37 -0500, Anthony Liguori wrote:
>   
>> This is can't really be a hard rule yet without the machine config, but 
>> we should do our best when we can.
>>     
>
> There's not much point in doing this unless there's some practical way
> to use it.
>
> If we e.g. add a 'class' parameter for virtio-blk and virtio-console,
> we'd also need to add some way for a management tool to figure out what
> the class value is when it initially creates the guest and, for ever
> more, supply that value.
>
> Options I see:
>
>   1) Add a monitor command to query the class values and delay actually 
>      changing the values until the next release cycle
>
>   2) Use 'info version' to achieve this - management tools would need to
>      start retaining the version that guests were created with and
>      supplying that version to qemu on the command line. As you say,
>      though, linear versioning sucks
>
>   3) Decide we can only make these guarantees with the machine config
>      stuff - management tools would need to query a running qemu for a
>      detailed machine config when initially creating the guest and
>      always supply that when later starting the guest
>   

Today, the qdev stuff supports properties for devices.  If you make
class a property of these devices, you would just need something to dump
the device properties for a given device.

I think it should be a relatively straight forward thing today.

Regards,

Anthony Liguori

> Cheers,
> Mark.
>
>   

  reply	other threads:[~2009-05-28  9:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 17:14 [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER Mark McLoughlin
2009-05-24  9:11 ` Avi Kivity
2009-05-27 14:21 ` Anthony Liguori
2009-05-27 17:42   ` Mark McLoughlin
2009-05-27 22:37     ` Anthony Liguori
2009-05-28  9:33       ` Mark McLoughlin
2009-05-28  9:44         ` Anthony Liguori [this message]
2009-05-28 12:53     ` Paul Brook
2009-05-28 12:56       ` Anthony Liguori
2009-05-28 13:22         ` Paul Brook
2009-05-28 13:29           ` Anthony Liguori
2009-05-28 21:45             ` Dor Laor
2009-05-29  9:43               ` Mark McLoughlin
2009-05-29  9:50                 ` Anthony Liguori
2009-05-31 14:32                   ` Avi Kivity
2009-05-29  9:55                 ` Anthony Liguori
2009-05-29 10:09                 ` Mark McLoughlin
2009-05-31 14:47                   ` Dor Laor
2009-06-02  8:49                     ` Mark McLoughlin
2009-06-02 13:08                       ` Dor Laor
2009-06-02 13:39                         ` Mark McLoughlin
2009-05-31 14:35                 ` Dor Laor
2009-06-02  8:49                   ` Mark McLoughlin
2009-05-28 13:04       ` Daniel P. Berrange
2009-05-28 13:19         ` Anthony Liguori
2009-05-31 18:48           ` Jamie Lokier
2009-05-28 13:20         ` Paul Brook

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=4A1E5D01.6000005@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=ajax@redhat.com \
    --cc=dlaor@redhat.com \
    --cc=markmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.