Re: [RFC PATCH 00/10] Rework PCI locking

2023-01-19 Thread Jan Beulich
On 18.01.2023 19:21, Julien Grall wrote: > On 06/09/2022 11:32, Jan Beulich wrote: >> On 31.08.2022 16:10, Volodymyr Babchuk wrote: >>> Hello, >>> >>> This is yet another take to a PCI locking rework. This approach >>> was suggest by Jan Beulich who proposed to use a reference >>> counter to contro

Re: [RFC PATCH 00/10] Rework PCI locking

2023-01-18 Thread Julien Grall
Hi Jan, On 06/09/2022 11:32, Jan Beulich wrote: On 31.08.2022 16:10, Volodymyr Babchuk wrote: Hello, This is yet another take to a PCI locking rework. This approach was suggest by Jan Beulich who proposed to use a reference counter to control lifetime of pci_dev objects. When I started added

Re: [RFC PATCH 00/10] Rework PCI locking

2022-09-06 Thread Jan Beulich
On 31.08.2022 16:10, Volodymyr Babchuk wrote: > Hello, > > This is yet another take to a PCI locking rework. This approach > was suggest by Jan Beulich who proposed to use a reference > counter to control lifetime of pci_dev objects. > > When I started added reference counting it quickly became c

[RFC PATCH 00/10] Rework PCI locking

2022-08-31 Thread Volodymyr Babchuk
Hello, This is yet another take to a PCI locking rework. This approach was suggest by Jan Beulich who proposed to use a reference counter to control lifetime of pci_dev objects. When I started added reference counting it quickly became clear that this approach can provide more granular locking in