From: Tim Deegan <tim@xen.org>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Alex Bligh <alex@alex.org.uk>, Matt Wilson <msw@amazon.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] Add Xen platform PCI device version 2.
Date: Thu, 20 Jun 2013 09:56:22 +0100 [thread overview]
Message-ID: <20130620085622.GA44136@ocelot.phlegethon.org> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD004D3FC@LONPEX01CL01.citrite.net>
At 07:47 +0000 on 20 Jun (1371714432), Paul Durrant wrote:
> > > I agree. If this is really the only solution, we would need to have
> > > both versions presented to the guest so that old drivers continue to
> > > work without any intervention.
> >
> > I suspect that if we expose both, both sets of drivers try to run the
> > same PV connections, and hilarity ensues.
> >
>
> Actually I think I can make that work, and it is the conclusion I came
> to after Alex's comment.
Ah, nice! In that case, I'm a lot less worried -- we can just expose
both versions/devices by default and there's no need for a visible
control knob tied to driver version (except maybe for debugging).
It means an 'unsupported' device appearing on other/older OSes, which is
unfortunate, but ISTR only Windows really complains visibly about that.
Tim.
next prev parent reply other threads:[~2013-06-20 8:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 9:32 [Qemu-devel] [PATCH] Add Xen platform PCI device version 2 Paul Durrant
2013-06-19 9:42 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2013-06-19 9:43 ` Paul Durrant
2013-06-19 10:07 ` Ian Campbell
2013-06-19 10:13 ` Paul Durrant
2013-06-19 10:42 ` Alex Bligh
2013-06-19 11:35 ` Paul Durrant
2013-06-19 18:21 ` Matt Wilson
2013-06-19 20:15 ` Tim Deegan
2013-06-20 7:47 ` Paul Durrant
2013-06-20 8:08 ` Alex Bligh
2013-06-20 8:19 ` Paul Durrant
2013-06-20 8:56 ` Tim Deegan [this message]
2013-06-20 9:25 ` Paul Durrant
2013-06-26 10:39 ` Ian Campbell
2013-06-26 11:23 ` Paul Durrant
2013-06-26 11:53 ` Ian Campbell
2013-06-26 11:57 ` Tim Deegan
2013-06-26 12:06 ` Paul Durrant
2013-06-26 12:36 ` Tim Deegan
2013-06-26 13:00 ` Paul Durrant
2013-06-26 20:00 ` Alex Bligh
2013-06-27 8:29 ` Paul Durrant
2013-06-27 10:58 ` Paul Durrant
2013-06-19 10:43 ` Ian Campbell
2013-06-19 10:36 ` Tim Deegan
2013-06-19 11:31 ` Paul Durrant
2013-06-19 16:40 ` Paolo Bonzini
2013-06-26 10:38 ` Ian Campbell
2013-06-19 10:54 ` James Harper
2013-06-19 11:23 ` Paul Durrant
2013-06-19 15:46 ` Tim Deegan
2013-06-19 16:03 ` Paul Durrant
2013-06-19 11:40 ` Paul Durrant
2013-06-20 12:17 ` [Qemu-devel] " Anthony Liguori
2013-06-20 12:44 ` Paul Durrant
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=20130620085622.GA44136@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=alex@alex.org.uk \
--cc=msw@amazon.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xen.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).