[Xen-devel] [PATCH][HVM] pass-through PCI device hotplug support

[Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>]

Zhai, Edwin wrote:
> Thanks for you info.
>
> Did you change the PCI dev config in xend, which is not friendly to hotplug?
> (only one dev node for all pass-through devices)
No, I left it as it was.

> Do you have a HVM PV driver for pass-through device?
No, I included hotplug handling methods in pcifront driver
which work only on PV linux.

Thanks,
----------
    Yosuke

> Thanks,
>
>
> On Mon, Feb 18, 2008 at 09:53:22PM +0900, Yosuke Iwamatsu wrote:
> > Hi,
> >
> > Just for your information,
> > I have been working on pass-through PCI device hotplug for PV domains,
> > and now pci-attach/detach for PV domains worked successfully.
> > I think I can submit an RFC patch in a few days.
> >
> > Thanks,
> > -----------------
> > Yosuke Iwamatsu
> >   NEC Corporation
> >
> >
> > Zhai, Edwin wrote:
> > > Keir,
> > >
> > > This patch is the new version against 17051 to enable HVM guest VT-d device 
> > > hotplug.
> > >
> > > ** Currently only 2 virtual pci slots(6~7) are made as being capable of hotplug, 
> > > so more than 2 vtd dev can't be hotplugged, but we can easily extend it in 
> > > future.
> > > Three new commands are added:
> > > "xm pci-list domid" show the current assigned vtd device, like:
> > > VSlt  domain   bus   slot   func
> > > 0x6      0x0  0x02   0x00    0x0
> > >
> > > "xm pci-detach" hot remove the specified vtd device by the virtual slot, like:
> > > xm pci-detach EdwinHVMDomainVtd 6
> > >
> > > "xm pci-attach DomainID dom bus dev func [vslot]" hot add a new vtd device in 
> > > the vslot. If no vslot specified, a free slot will be picked up. e.g. to insert 
> > > '0000:03:00.0':
> > > xm pci-attach EdwinHVMDomainVtd 0 3 0 0
> > >
> > > ** guest pci hotplug
> > > linux: pls. use 2.6.X and enable ACPI PCI hotplug ( Bus options=> PCI hotplug => 
> > > ACPI PCI hotplug driver)
> > > windows: 2000/xp/2003/vista are all okay
> > >
> > >
> > > Thanks a lot.
> > >
> > >
> > >
> > > ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel