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] [RFC] Auto rebind PCI devices

To: hap9@xxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC] Auto rebind PCI devices
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Tue, 4 Apr 2006 17:43:32 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 04 Apr 2006 10:42:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: University of Cambridge
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
Hi Ryan,

I remember you showing some interest when I suggested rebinding PCI devices 
automatically.  I've hacked together a quick prototype of "what I meant".

I put a bundle at: 

You can fetch my changes into a repository using:
hg unbundle <url>

The behaviour is:
* If the device specified in a domain config file is already bound to another 
driver in dom0, fail creation with an error - as before.
* If the device specified in the config is not currently bound to a driver, 
add it to the pciback driver and create the domain.
* If the device specificed in the config is bound *and* pci-force-rebind is 
set, then unbind it from the existing driver and rebind it to pciback, then 
start the domain.

pci-force-rebind allows users who want total automation in the rebinding 
process to have it, whilst by default preventing the automatic rebinding from 
stealing devices dom0 is relying on.

I'd be interested to see what you think about it - in particular, whether 
there are potential failures in the rebinding code that I ought to be 
catching (e.g. if drivers won't unbind from a device - can that happen?).  
Any objections to the general functionality?


Xen-devel mailing list

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