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

Re: [Xen-devel] [PATCH] PCI Backend - Late Binding

To: Ryan <hap9@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] PCI Backend - Late Binding
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 23 Mar 2006 13:43:56 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 23 Mar 2006 13:45:16 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Your message of "Wed, 22 Mar 2006 19:32:40 EST." <1143073960.22254.30.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> # Add a new slot to the PCI Backend's list
> echo -n 0000:01:04.d > /sys/bus/pci/drivers/pciback/new_slot
> # Now that the backend is watching for the slot, bind to it
> echo -n 0000:01:04.d > /sys/bus/pci/drivers/pciback/bind

Thanks for the patches, which I've now applied. Why do you need the
two-stage process to bind on a PCI device? Is it because writing to
the 'bind' file gets swallowed by sysfs unless your driver has
pre-registered an interest in the particular PCI device?

 -- Keir

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