From: Tim Deegan <tim@xen.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Paul Durrant <Paul.Durrant@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"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: Wed, 19 Jun 2013 11:36:24 +0100 [thread overview]
Message-ID: <20130619103624.GA32645@ocelot.phlegethon.org> (raw)
In-Reply-To: <1371636452.22783.105.camel@zakaz.uk.xensource.com>
At 11:07 +0100 on 19 Jun (1371640052), Ian Campbell wrote:
> On Wed, 2013-06-19 at 10:43 +0100, Paul Durrant wrote:
> > > -----Original Message-----
> > > From: Ian Campbell
> > > Sent: 19 June 2013 10:42
> > > To: Paul Durrant
> > > Cc: qemu-devel@nongnu.org; xen-devel@lists.xen.org
> > > Subject: Re: [Xen-devel] [PATCH] Add Xen platform PCI device version 2.
> > >
> > > On Wed, 2013-06-19 at 10:32 +0100, Paul Durrant wrote:
> > > > The XenServer 6.1+ Citrix Windows PV bus driver binds to a new version
> > > > of the Xen platform device (since the newer driver set cannot co-exist
> > > > with previous drivers which bind to the existing "xen-platform" type of
> > > > device). This patch introduces a new "xen-platform-2" device type with
> > > > the appropriate device_id and revision.
>
> We obviously can't say to users "Are you running Windows and are you
> running PV drivers >= X.Y, if so set lever A to position B, otherwise if
> you are running some other OS or an earlier version of the Windows PV
> driver set it to position A".
Agreed - that's a horrible interface, and an egregious layer violation.
The VM's admin should be able to install/upgrade software without
involving the host admin.
Can you explain a bit more about why this is needed? Presumably 'real'
device manufacturers can ship new versions of their drivers through
Windows Update without needing to rev their hardware or get the user to
change BIOS settings.
Tim.
next prev parent reply other threads:[~2013-06-19 10:36 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
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 [this message]
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=20130619103624.GA32645@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=Paul.Durrant@citrix.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).