Displaying 4 results from an estimated 4 matches for "parse_ivhd_device_speci".
Did you mean:
parse_ivhd_device_spec
2013 Sep 12
3
[PATCH 1/1 V3] x86/AMD-Vi: Add additional check for invalid special->handle
...e override present for IO-APIC %#x "
+ "(IVRS: %#x devID %04x:%02x:%02x.%u)\n",
+ apic, handle, seg, PCI_BUS(bdf),
+ PCI_SLOT(bdf), PCI_FUNC(bdf));
+ ret = 1;
+ }
+
+ return ret;
+}
+
static u16 __init parse_ivhd_device_special(
const struct acpi_ivrs_device8c *special, u16 seg,
u16 header_length, u16 block_length, struct amd_iommu *iommu)
@@ -698,16 +725,18 @@ static u16 __init parse_ivhd_device_special(
return 0;
}
- AMD_IOMMU_DEBUG("IVHD Special: %04x:%02x:%02x.%u variety %#x handle...
2013 Aug 28
12
[PATCH V2] x86/AMD-Vi: Add additional check for invalid special->handle
...ed, 37 insertions(+), 18 deletions(-)
diff --git a/xen/drivers/passthrough/amd/iommu_acpi.c b/xen/drivers/passthrough/amd/iommu_acpi.c
index 89b359c..8b14112 100644
--- a/xen/drivers/passthrough/amd/iommu_acpi.c
+++ b/xen/drivers/passthrough/amd/iommu_acpi.c
@@ -698,14 +698,16 @@ static u16 __init parse_ivhd_device_special(
return 0;
}
- AMD_IOMMU_DEBUG("IVHD Special: %04x:%02x:%02x.%u variety %#x handle %#x\n",
+ AMD_IOMMU_DEBUG("IVHD Special: %04x:%02x:%02x.%u variety %#x handle %#x used_id %#x\n",
seg, PCI_BUS(bdf), PCI_SLOT(bdf), PCI_FUNC(bdf),
-...
2013 Jul 22
69
[xen-unstable] Commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, makes dom0 boot process stall several times.
Hi Jan,
After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times.
Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times.
(It also stalls on shutdown BTW)
I have
2013 Oct 06
17
AMD IOMMU disabled - No Perdev Intremap
Hi!
From other people posting to this list, I know that there has been a
bug related to the issue described in Xen Security Advisory 36 that
disables iommu for some AMD users like me.
However, even when passing "iommu=no-amd-iommu-perdev-intremap" it
still disables i/o virtualisatoin. Related Xen dmesg output:
(XEN) IVHD Error: Invalid IO-APIC 0
(XEN) AMD-Vi: Error initialization