From: Suravee Suthikulpanit
The guest IOMMU feature is currently not functioning. However,
the current guest_iommu_init() is causing issue when it tries to
register mmio handler because the it is currently called by the
following code path:
arch/x86/domain.c: arch_domain_create()
]- driver
From: Suravee Suthikulpanit
At the time of registering HVM I/O handler, the HVM domain might
not have been initialized, which means the hvm_domain.io_handler
would be NULL. In the hvm_next_io_handler(), this should be asserted.
Reviewed-by: Paul Durrant
Signed-off-by: Suravee Suthikulpanit
---
From: Suravee Suthikulpanit
Hi All,
Changes from V3:
* Remove calls to guest_iommu_init()/destroy() for now since
the guest iommu feature is not functing and causing breakage.
* Do not change the ordering of the iommu_domain_init() and
hvm_domain_init() for now until we agree on pro
From: Suravee Suthikulpanit
Along with the IVHD block type 10h, newer AMD platforms also come with
types 11h, which is a superset of the older one. Having multiple IVHD
block types in the same platform allows backward compatibility of newer
systems to work with existing drivers. The driver shoul
From: Suravee Suthikulpanit
Along with the IVHD block type 10h, newer AMD platforms also come with
types 11h, which is a superset of the older one. Having multiple IVHD
block types in the same platform allows backward compatibility of newer
systems to work with existing drivers. The driver shoul
From: Suravee Suthikulpanit
Along with the IVHD block type 10h, newer AMD platforms also come with
types 11h, which is a superset of the older one. Having multiple IVHD
block types in the same platform allows backward compatibility of newer
systems to work with existing drivers. The driver shoul
From: Suravee Suthikulpanit
guest_iommu_init tries to register mmio handler before HVM domain
is initialized. This cause registration to silently failing.
This patch adds a sanitiy check and puts out error message.
Signed-off-by: Suravee Suthikulapanit
---
xen/drivers/passthrough/amd/iommu_gue
From: Suravee Suthikulpanit
Hi All,
Changes from V2:
* Use assert instead of sanity check before count increment in
the hvm_next_io_handler().
* Post-pone iommu_domain_init() and add proper error handling code
to destroy hvm in case of failure.
* Split out sanity check in guest_iom
From: Suravee Suthikulpanit
At the time of registering HVM I/O handler, the HVM domain might
not have been initialized, which means the hvm_domain.io_handler
would be NULL. In the hvm_next_io_handler(), this should be asserted.
Signed-off-by: Suravee Suthikulpanit
---
xen/arch/x86/hvm/intercep
From: Suravee Suthikulpanit
The guest_iommu_init() is currently called by the following code path:
arch/x86/domain.c: arch_domain_create()
]- drivers/passthrough/iommu.c: iommu_domain_init()
|- drivers/passthrough/amd/pci_amd_iommu.c: amd_iommu_domain_init();
|- drive
From: Suravee Suthikulpanit
At the time of registering HVM I/O handler, the HVM domain might
not have been initialized, which means the hvm_domain.io_handler
would be NULL. In the hvm_next_io_handler(), this should be asserted.
Signed-off-by: Suravee Suthikulpanit
---
xen/arch/x86/hvm/intercep
From: Suravee Suthikulpanit
The guest_iommu_init() is currently called by the following code path:
arch/x86/domain.c: arch_domain_create()
]- drivers/passthrough/iommu.c: iommu_domain_init()
|- drivers/passthrough/amd/pci_amd_iommu.c: amd_iommu_domain_init();
|- drive
From: Suravee Suthikulpanit
Hi All,
Changes from V2:
* Use assert instead of sanity check before count increment in
the hvm_next_io_handler().
* Post-pone iommu_domain_init() and add proper error handling code
to destroy hvm in case of failure.
* Split out sanity check in guest_iom
From: Suravee Suthikulpanit
Along with the IVHD block type 10h, newer AMD platforms also come with
types 11h, which is a superset of the older one. Having multiple IVHD
block types in the same platform allows backward compatibility of newer
systems to work with existing drivers. The driver shoul
From: Suravee Suthikulpanit
The guest_iommu_init() is currently called by the following code path:
arch/x86/domain.c: arch_domain_create()
]- drivers/passthrough/iommu.c: iommu_domain_init()
|- drivers/passthrough/amd/pci_amd_iommu.c: amd_iommu_domain_init();
|- drive
From: Suravee Suthikulpanit
Hi All,
On systems with iommu v2 enabled, the hypervisor crashes when trying
to start up an HVM guest.
Investigating shows that the guest_iommu_init() is called before the
HVM domain is initialized. It then tries to register_mmio_handler()
causing the hvm_next_io_ha
From: Suravee Suthikulpanit
At the time of registering HVM I/O handler, the HVM domain might
not have been initialized, which means the hvm_domain.io_handler
would be NULL. In the hvm_next_io_handler(), this should be checked
before returning and referencing the array. Also, the io_handler_count
From: Suravee Suthikulpanit
Hi All,
On systems with iommu v2 enabled, the hypervisor crashes when trying
to start up an HVM guest.
Investigating shows that the guest_iommu_init() is called before the
HVM domain is initialized. It then tries to register_mmio_handler()
causing the hvm_next_io_ha
From: Suravee Suthikulpanit
The guest_iommu_init() is currently called by the following code path:
arch/x86/domain.c: arch_domain_create()
]- drivers/passthrough/iommu.c: iommu_domain_init()
|- drivers/passthrough/amd/pci_amd_iommu.c: amd_iommu_domain_init();
|- drive
From: Suravee Suthikulpanit
At the time of registering HVM I/O handler, the HVM domain might
not have been initialized, which means the hvm_domain.io_handler
would be NULL. In the hvm_next_io_handler(), this should be checked
before returning and referencing the array. Also, the io_handler_count
20 matches
Mail list logo