WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] issue in unplug qemu PCI devices

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: [Xen-devel] issue in unplug qemu PCI devices
From: "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
Date: Fri, 12 Feb 2010 16:48:25 +0800
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Zhai, Edwin" <edwin.zhai@xxxxxxxxx>
Delivery-date: Fri, 12 Feb 2010 00:48:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (X11/20080914)
IOEMU change set e7911109 uses Magic ioport (0x10) protocol for negotating with guest PV drivers during startup, and allowing PV drivers to disable hardware emulations thus preventing guest from seeing the same device through two paths.

But when I tried PV drivers in xen upstream, this unplug logic never succeed. PV driver uses following io sequence to interact with platform_pci device in qemu:
1. inw 0x10
2. inb 0x12
3. outw(0x12, 0xbeef)
4. outl(0x10,0xdead)

But I only saw 1&2 happened in xen io instruction emulation(x86_emulate), while 3&4 seemed to lost so the unplug will never happen.

Are you aware of this issue? Or some suggestion for debugging?

BTW, the unplug logic itself has some issues also:
1. Pass-through NICs are also unplugged, although them have different path with vnif and emulated NIC. 2. Unplug happens as long as inserting the xen_platform_pci module regardless of existence of PVed device in the config file. End user likely to unplug all the PCI device by accident. 3. Inserting xen_platform_pci module would unplug all the devices, which is not reasonable. E.g. end user only has vbd driver, but all NICs are also unplugged.









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