Re: [Xen-devel] [v5][PATCH 0/5] xen: add Intel IGD passthrough support

["Michael S. Tsirkin" <mst@xxxxxxxxxx>]

On Wed, Jun 25, 2014 at 04:16:12PM +0200, Paolo Bonzini wrote:
> Il 25/06/2014 16:10, Michael S. Tsirkin ha scritto:
> >On Wed, Jun 25, 2014 at 03:53:30PM +0200, Paolo Bonzini wrote:
> >>Il 25/06/2014 15:47, Michael S. Tsirkin ha scritto:
> >>>OK, so how about doing this: either for the ISA
> >>>bridge, or for the VGA card itself:
> >>>
> >>>   set subsystem vendor id to PCI_VENDOR_ID_XEN,
> >>>   set subsystem device id to PCH device id
> >>
> >>That would work, but the same problem would then arise for the MCH.  The
> >>driver there is banging at random places in the configuration space.
> >>
> >>This is why I asked for a solution that is future-proof, and since you can
> >>make one that works for both MCH and PCH it is nice to do the work just
> >>once.
> >
> >Q35 has MCH, so I don't see why we can't make that work,
> >extending it as appropriate.
> 
> Is Q35's MCH configuration space entirely compatible with newer chipsets
> that are in the host and that the IGD driver expects?  I dont think it's
> safe to assume that.

So far only a couple of registers were emulated.
I don't see any conflicts there.

Implementing a newer MCH would also be useful, outside xen.


> >Doing that for PIIX is iffy.
> >Should we really do that? Q35 is there.
> 
> Xen doesn't support Q35,

You have to start somewhere :)

> and Q35 is still lacking migration.

It isn't, just disable ahci.

> So it's really a chicken-and-egg problem.
> 
> Paolo

Well I don't see how is this PV thing any better.

Again, experience shows if we don't push hard enough for people to fix
their stuff, and just merge crappy work-arounds "as a 1st step",
motivation for people to fix their stuff disappears, and the second step
is never taken.

Let's see the clean if incomplete solution as the first step.
We can add work-arounds for legacy configs as the second step.

-- 
MST

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel