On Mon, Dec 16, 2013 at 11:34:32AM +, David Vrabel wrote:
> On 13/12/13 16:09, Konrad Rzeszutek Wilk wrote:
> > The life-cycle of a PCI device in Xen pciback is a bit complex.
> >
> > It starts with the device being binded to us - for which
> > we do a device function reset.
> >
> > If the de
On 13/12/13 16:09, Konrad Rzeszutek Wilk wrote:
> The life-cycle of a PCI device in Xen pciback is a bit complex.
>
> It starts with the device being binded to us - for which
> we do a device function reset.
>
> If the device is unbinded from us - we also do a function
> reset.
Spelling: bound a
> +/* Called when 'bind' */
> static int pcistub_probe(struct pci_dev *dev, const struct pci_device_id *id)
> {
> int err = 0;
> @@ -528,6 +617,7 @@ out:
> return err;
> }
>
> +/* Called when 'unbind' */
> static void pcistub_remove(struct pci_dev *dev)
> {
> struct pcistub
The life-cycle of a PCI device in Xen pciback is a bit complex.
It starts with the device being binded to us - for which
we do a device function reset.
If the device is unbinded from us - we also do a function
reset.
If the device is un-assigned from a guest - we do a function
reset.
All on the
4 matches
Mail list logo
