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/
Home Products Support Community News


[Xen-devel] [PATCH 0/3] RFC: PCIe IO space multiplexing for bootable pas

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0/3] RFC: PCIe IO space multiplexing for bootable pass through HVM domain
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Thu, 2 Apr 2009 13:01:28 +0900
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, Ian.Jackson@xxxxxxxxxxxxx
Delivery-date: Wed, 01 Apr 2009 21:04:32 -0700
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: Mutt/1.5.18 (2008-05-17)
Hi all. This is for PCIe IO space multiplexing. Please comment.

It is not uncommon that a big iron for server consolidation has
many (e.g. > 16) PCIe slots. It will hold many domains, and
the administrator wants them to boot from pass through devices.
But currently up to 16 hvm domains can boot from pass through device.

This patch series addresses this issue by multiplexing IO space access.
The patches are composed of
        Linux part: IO space ressignment code and multiplexing driver
        xen part:   udev script for the driver
        ioemu part: make use of the PCIe io space multiplexing driver

Add dom0 kernel command line specifying the pass through devices by
(Don't forget add related options. pciback.hide, reassign_resources,
reassigndev or guestdev.)

PCI expansion ROM BIOS often uses IO port access to boot from its device
and Linux as dom0 exclusively assigns IO space to downstream PCI bridges
and the assignment unit of PCI bridge IO space is 4K. So the only up to
16 PCIe device can be accessed via IO space within 64K IO ports.
So on virtualized environment, it means only up to 16 guest domains
can boot from such pass-through devices.

PCI devices or root complex integrated endpoints aren't supported.
IO port of IO shared devices can't be accessed from dom0 Linux device driver.
But this wouldn't be a big issue because PCIe specification discourages
the use of IO space and recommends that IO space should be used only
for bootable device with ROM code. OS device driver should work without
IO space access.

At present I have tested with only single multifunction PCIe because
I don't have a machine with complicated PCIe topology nor many PCIe cards.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>