Hi Julien,
> On 21 Oct 2021, at 14:47, Julien Grall wrote:
>
>
>
> On 21/10/2021 14:15, Bertrand Marquis wrote:
>> Hi Julien,
>
> Hi Bertand,
>
>>> On 21 Oct 2021, at 10:28, Julien Grall wrote:
>>>
>>> Hi all,
>>>
>>> While going through the passthrough code. I noticed that we don't have
On 21/10/2021 14:15, Bertrand Marquis wrote:
Hi Julien,
Hi Bertand,
On 21 Oct 2021, at 10:28, Julien Grall wrote:
Hi all,
While going through the passthrough code. I noticed that we don't have a common
lock for the IOMMU between the PCI and DT code.
This is going to be an issue given
Hi Julien,
> On 21 Oct 2021, at 10:28, Julien Grall wrote:
>
> Hi all,
>
> While going through the passthrough code. I noticed that we don't have a
> common lock for the IOMMU between the PCI and DT code.
>
> This is going to be an issue given it would technically be possible to add a
> PCI
Hi all,
While going through the passthrough code. I noticed that we don't have a
common lock for the IOMMU between the PCI and DT code.
This is going to be an issue given it would technically be possible to
add a PCI device while assigning a DT.
Rahul, Bertrand, Oleksandr, can you have a
On 07.10.2021 02:05, Stefano Stabellini wrote:
> On Wed, 6 Oct 2021, Rahul Singh wrote:
>> Hardware domain is in charge of doing the PCI enumeration and will
>> discover the PCI devices and then will communicate to XEN via hyper
>> call PHYSDEVOP_pci_device_add(..) to add the PCI devices in XEN.
On Wed, 6 Oct 2021, Rahul Singh wrote:
> Hardware domain is in charge of doing the PCI enumeration and will
> discover the PCI devices and then will communicate to XEN via hyper
> call PHYSDEVOP_pci_device_add(..) to add the PCI devices in XEN.
>
> Also implement PHYSDEVOP_pci_device_remove(..)
Hardware domain is in charge of doing the PCI enumeration and will
discover the PCI devices and then will communicate to XEN via hyper
call PHYSDEVOP_pci_device_add(..) to add the PCI devices in XEN.
Also implement PHYSDEVOP_pci_device_remove(..) to remove the PCI device.
As most of the code for
