pci_release_devices() takes the global PCI lock. Once pci_release_devices()
has completed, it will be called redundantly each time paging_teardown() and
vcpu_destroy_pagetables() continue.
This is liable to be millions of times for a reasonably sized guest, and is a
serialising bottleneck now tha
On 21/02/2019 13:22, Andrew Cooper wrote:
> pci_release_devices() takes the global PCI lock. Once pci_release_devices()
> has completed, it will be called redundantly each time paging_teardown() and
> vcpu_destroy_pagetables() continue.
>
> This is liable to be millions of times for a reasonably
On Thu, Feb 21, 2019 at 12:22:13PM +, Andrew Cooper wrote:
> pci_release_devices() takes the global PCI lock. Once pci_release_devices()
> has completed, it will be called redundantly each time paging_teardown() and
> vcpu_destroy_pagetables() continue.
>
> This is liable to be millions of ti
>>> On 21.02.19 at 14:31, wrote:
> On Thu, Feb 21, 2019 at 12:22:13PM +, Andrew Cooper wrote:
>> pci_release_devices() takes the global PCI lock. Once pci_release_devices()
>> has completed, it will be called redundantly each time paging_teardown() and
>> vcpu_destroy_pagetables() continue.
>
Hi Andrew,
On 2/21/19 12:22 PM, Andrew Cooper wrote:
pci_release_devices() takes the global PCI lock. Once pci_release_devices()
has completed, it will be called redundantly each time paging_teardown() and
vcpu_destroy_pagetables() continue.
This is liable to be millions of times for a reasona
