From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [PATCH] vfio-pci: PCI hot reset interface Date: Tue, 20 Aug 2013 08:42:47 +1000 Message-ID: <1376952167.25016.85.camel@pasglop> References: <20130814200845.21923.64284.stgit@bling.home> <1376521578.13642.65.camel@ul30vt.home> <1376937682.2657.15.camel@ul30vt.home> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Alex Williamson , "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , Alexander Viro , linux-fsdevel To: Bjorn Helgaas Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, 2013-08-19 at 14:02 -0600, Bjorn Helgaas wrote: > I guess. And supply the pci_slot rather than the pci_dev? I'm a > little bit worried because the idea of a "slot" is not well-defined in > the spec, and we have sort of an ad hoc method of discovering and > managing them, e.g., acpiphp and pciehp might discover the same slot. > But I guess that's no reason to bury generic code in vfio. And I don't have pci_slot's at all yet on powerpc "powernv" (the host platform for KVM) since at this stage we don't support physical hotplug on the target machines... Alex, why specifically looking for "slots" here ? I don't quite understand. It makes sense to be able to reset individual devices whether they are on the otherboard, behind extension chassis or directly on slots... Cheers, Ben.