On 22.06.2023 00:11, Volodymyr Babchuk wrote:
> Jan Beulich writes:
>> On 15.06.2023 11:39, Volodymyr Babchuk wrote:
>>> Stewart Hildebrand writes:
On 6/13/23 06:32, Volodymyr Babchuk wrote:
> Hello,
>
> This is another another version of vPCI rework (previous one can be
> fo
Hi Jan,
Jan Beulich writes:
> On 15.06.2023 11:39, Volodymyr Babchuk wrote:
>> Stewart Hildebrand writes:
>>> On 6/13/23 06:32, Volodymyr Babchuk wrote:
Hello,
This is another another version of vPCI rework (previous one can be
found at [1]). The biggest change is how vPCI
On 15.06.2023 11:39, Volodymyr Babchuk wrote:
> Stewart Hildebrand writes:
>> On 6/13/23 06:32, Volodymyr Babchuk wrote:
>>> Hello,
>>>
>>> This is another another version of vPCI rework (previous one can be
>>> found at [1]). The biggest change is how vPCI locking is done. This
>>> series uses pe
Hi Stewart,
Stewart Hildebrand writes:
> On 6/13/23 06:32, Volodymyr Babchuk wrote:
>> Hello,
>>
>> This is another another version of vPCI rework (previous one can be
>> found at [1]). The biggest change is how vPCI locking is done. This
>> series uses per-domain vPCI rwlock.
>>
>> Note tha
On 6/13/23 06:32, Volodymyr Babchuk wrote:
> Hello,
>
> This is another another version of vPCI rework (previous one can be
> found at [1]). The biggest change is how vPCI locking is done. This
> series uses per-domain vPCI rwlock.
>
> Note that this series does not include my work on reference c
Hello,
This is another another version of vPCI rework (previous one can be
found at [1]). The biggest change is how vPCI locking is done. This
series uses per-domain vPCI rwlock.
Note that this series does not include my work on reference counting
for PCI devices because this counting does not re
