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 21:40:28 +0100	[thread overview]
Message-ID: <4B26A2BC.6010501@redhat.com> (raw)
In-Reply-To: <20091214191742.GA6100@redhat.com>

On 12/14/09 20:17, Michael S. Tsirkin wrote:
> On Mon, Dec 14, 2009 at 06:18:29PM +0100, Gerd Hoffmann wrote:
>> On 12/14/09 17:23, Michael S. Tsirkin wrote:
>>> On Mon, Dec 14, 2009 at 04:01:33PM +0100, Gerd Hoffmann wrote:
>>> So how do you do this?
>>> Assume we have -disable_hw_csum.
>>> We want new machine type to have it off, right?
>>> But now you run qemu on host which does
>>> not support hw_csum. With your suggestion
>>> it will not enable hw csum?
>>
>> I have trouble getting the setup you are talking about ...
>>
>> Sounds like hw_csum could be enabled/disabled depending on the hardware
>> capabilities on the host.  Is that correct?
>>
>> cheers,
>>    Gerd
>
> This currently depends on version of tun driver in the host.

So this has nothing to do with -M pc-0.11 backward compatibility, right? 
  You'll hit this when migrating 0.12 -> 0.12 with different host 
kernels, right?  And the common bit here is that both issues can be 
handled by configuring virtio feature bits via properties, right?

What was the question again?

cheers,
   Gerd

  reply	other threads:[~2009-12-14 20:40 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 [this message]
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=4B26A2BC.6010501@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).