From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: borntraeger@de.ibm.com, jasowang@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.5] virtio: handle non-virtio-1-capable backend
Date: Wed, 2 Dec 2015 18:19:42 +0100 [thread overview]
Message-ID: <20151202181942.1a9497c2.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20151202184036-mutt-send-email-mst@redhat.com>
On Wed, 2 Dec 2015 18:43:05 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Dec 02, 2015 at 03:09:58PM +0100, Cornelia Huck wrote:
> > If you run a qemu advertising VERSION_1 with an old kernel where
> > vhost did not yet support VERSION_1, you'll end up with a device
> > that is {modern pci|ccw revision 1} but does not advertise VERSION_1.
> > This is not a sensible configuration and is rejected by the Linux
> > guest drivers.
> >
> > To fix this, add a ->post_plugged() callback invoked after features
> > have been queried that can handle the VERSION_1 bit being withdrawn
> > and change pci (only setup modern if VERSION_1 is still present) and
> > ccw (fall back to revision 0 if VERSION_1 is gone).
> >
> > Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
>
>
> Unfortunately this is too late: we need to know
> whether modern will be supported to know whether
> to add the pci express capability :(
>
> Maybe this should be moved into plugged
> callback?
As discussed on irc: I'll cut this down to ccw only for 2.5, and we'll
rethink for 2.6. Patch in progress.
next prev parent reply other threads:[~2015-12-02 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 14:09 [Qemu-devel] [PATCH for-2.5] virtio: handle non-virtio-1-capable backend Cornelia Huck
2015-12-02 16:43 ` Michael S. Tsirkin
2015-12-02 17:19 ` Cornelia Huck [this message]
2015-12-03 9:14 ` Christian Borntraeger
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=20151202181942.1a9497c2.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=jasowang@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).