qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH RFC] virtio: add features qdev property
Date: Mon, 14 Dec 2009 22:24:49 +0100	[thread overview]
Message-ID: <4B26AD21.2090700@redhat.com> (raw)
In-Reply-To: <20091214211416.GE6100@redhat.com>

On 12/14/09 22:14, Michael S. Tsirkin wrote:
> On Mon, Dec 14, 2009 at 10:12:14PM +0100, Gerd Hoffmann wrote:
>> On 12/14/09 21:43, Michael S. Tsirkin wrote:
>>> What do we put in e.g. 0.11 compat? Any features we enable
>>> there might not be supported by host.
>>
>> compat properties as usual?
>>
>> Sorry, I still fail to see your problem.
>>
>> You'll have a 'disable' bitmap.  Fill it via 'features=<bitmap-prop>'.
>> Or using separate properties for each feature.
>> qemu goes figure host_features.  When done it masks out the features
>> disabled via properties.  The result is used as final feature bitmap.
>>
>> -M pc-0.11 will disable hw_checksum
>> management software can do it too via -device virtio-net-pci,... if some
>> machines in the pool don't support it.  And of course qemu will disable
>> it on its own in case the host kernel doesn't support it.
>>
>> cheers,
>>    Gerd
>
> management is always behind :).  Imagine a new and improved qemu. I run
> old management.  I expect to see old properties, but old management can
> not disable new ones :)

If management can't deal with 0.12 features it should use -M pc-0.11

cheers,
   Gerd

  reply	other threads:[~2009-12-14 21:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13 20:43 [Qemu-devel] [PATCH RFC] virtio: add features qdev property Michael S. Tsirkin
2009-12-14  9:41 ` [Qemu-devel] " Gerd Hoffmann
2009-12-14  9:42   ` Michael S. Tsirkin
2009-12-14 10:24     ` Gerd Hoffmann
2009-12-14 11:10       ` Michael S. Tsirkin
2009-12-14 11:37         ` Gerd Hoffmann
2009-12-14 13:15           ` Michael S. Tsirkin
2009-12-14 13:30           ` Markus Armbruster
2009-12-14 13:59             ` Michael S. Tsirkin
2009-12-14 15:01               ` Gerd Hoffmann
2009-12-14 16:23                 ` Michael S. Tsirkin
2009-12-14 17:18                   ` Gerd Hoffmann
2009-12-14 19:17                     ` Michael S. Tsirkin
2009-12-14 20:40                       ` Gerd Hoffmann
2009-12-14 20:43                         ` Michael S. Tsirkin
2009-12-14 21:12                           ` Gerd Hoffmann
2009-12-14 21:14                             ` Michael S. Tsirkin
2009-12-14 21:24                               ` Gerd Hoffmann [this message]
2009-12-14 14:56             ` Gerd Hoffmann
2009-12-14 19:20           ` Michael S. Tsirkin
2009-12-14 20:42             ` Gerd Hoffmann
2009-12-14 11:50         ` Alexander Graf

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=4B26AD21.2090700@redhat.com \
    --to=kraxel@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mst@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).