From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: [PATCH 2/2 v2] PCI: add remove_id sysfs entry Date: Thu, 19 Mar 2009 17:35:10 -0700 Message-ID: <20090319173510.5d7b5d41@hobbes.lan> References: <1234542767.23746.81.camel@blaa> <20090214021244.GW27684@sequoia.sous-sol.org> <20090214033319.GA4591@kroah.com> <20090224012625.GA7436@sequoia.sous-sol.org> <20090224055035.GF7436@sequoia.sous-sol.org> <20090224055223.GG7436@sequoia.sous-sol.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Greg KH , Mark McLoughlin , kvm , "linux-pci@vger.kernel.org" , Chris Wright , "Dugger, Donald D" , "Kay, Allen M" To: Chris Wright Return-path: In-Reply-To: <20090224055223.GG7436@sequoia.sous-sol.org> Sender: linux-pci-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, 23 Feb 2009 21:52:23 -0800 Chris Wright wrote: > This adds a remove_id sysfs entry to allow users of new_id to later > remove the added dynid. One use case is management tools that want to > dynamically bind/unbind devices to pci-stub driver while devices are > assigned to KVM guests. Rather than having to track which driver was > originally bound to the driver, a mangement tool can simply: > > # echo "8086 10f5" > /sys/bus/pci/drivers/pci-stub/new_id > # echo 0000:00:19.0 > /sys/bus/pci/devices/0000:00:19.0/driver/unbind > # echo 0000:00:19.0 > /sys/bus/pci/drivers/pci-stub/bind > > Guest uses device > > # echo "8086 10f5" > /sys/bus/pci/drivers/pci-stub/remove_id > # echo 0000:00:19.0 > /sys/bus/pci/drivers_probe > > Signed-off-by: Chris Wright Applied to linux-next, thanks Chris. -- Jesse Barnes, Intel Open Source Technology Center