Hello,
[...]
> > > Applied. Thanks.
> >
> > Would you mind if I take this via the PCI tree?
>
> No problem. I can drop that from my tree.
Thank you!
Krzysztof
Hello,
> The VF driver controls an endpoint attached to the pci-hyperv
> controller. An invalidation sent by the PF driver in the host would be
> delivered *to* the endpoint driver by the controller driver.
Applied to controller/hyperv, thank you!
Krzysztof
Hello,
> > The VF driver controls an endpoint attached to the pci-hyperv
> > controller. An invalidation sent by the PF driver in the host would be
> > delivered *to* the endpoint driver by the controller driver.
> >
> > Signed-off-by: Easwar Hariharan
>
> Applied. Thanks.
Would you mind if I
Hello,
> The intent of the code snippet is to always return 0 for both
> PCI_INTERRUPT_LINE and PCI_INTERRUPT_PIN.
>
> The check misses PCI_INTERRUPT_PIN. This patch fixes that.
>
> This is discovered by this call in VFIO:
>
> pci_read_config_byte(vdev->pdev, PCI_INTERRUPT_PIN, &pin);
>
>
Hello,
> > The intent of the code snippet is to always return 0 for both
> > PCI_INTERRUPT_LINE and PCI_INTERRUPT_PIN.
> >
> > The check misses PCI_INTERRUPT_PIN. This patch fixes that.
> >
> > This is discovered by this call in VFIO:
> >
> > pci_read_config_byte(vdev->pdev, PCI_INTERRUPT_P
Hello,
> For a physical PCI device that is passed through to a Hyper-V guest VM,
> current code specifies the VMBus ring buffer size as 4 pages. But this
> is an inappropriate dependency, since the amount of ring buffer space
> needed is unrelated to PAGE_SIZE. For example, on x86 the ring buffer
