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: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH RFC] virtio: add features qdev property
Date: Mon, 14 Dec 2009 11:24:41 +0100	[thread overview]
Message-ID: <4B261269.7080801@redhat.com> (raw)
In-Reply-To: <20091214094255.GA32140@redhat.com>

On 12/14/09 10:42, Michael S. Tsirkin wrote:
> On Mon, Dec 14, 2009 at 10:41:26AM +0100, Gerd Hoffmann wrote:
>> On 12/13/09 21:43, Michael S. Tsirkin wrote:
>>> Add features property to virtio. This makes it
>>> possible to e.g. define machine without indirect
>>> buffer support, which is required for 0.10
>>> compatibility. or without hardware checksum
>>> support, which is required for 0.11 compatibility.
>>
>> I'd suggest to add flags for the individual features to the drivers
>> which actually use it instead, so you'll have
>>
>>    -device virtio-net-pci,hw-checksum=0
>>
>> and
>>
>>    -device virtio-blk-pci,indirect-buffers=0
>>
>> cheers,
>>    Gerd
>
> Hmm. I hoped to avoid it, there are lots of features so it's a lot of
> work and in practice, this will most likely be set by machine
> description ...

MSI-X aka vectors property is already done this way, so I'd tend to 
continue this way.  It is also more user friendly.  Sure, these are most 
likely not used on a daily base by users, but being able to turn off -- 
say -- indirect buffers for testing and/or bug hunting reasons without 
having to construct magic hex numbers from virtio header files would be 
nice.

Can you give a list of features?  The patch description sounded like it 
is just the two listed above ...

cheers,
   Gerd

  reply	other threads:[~2009-12-14 10: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 [this message]
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
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=4B261269.7080801@redhat.com \
    --to=kraxel@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).