Displaying 2 results from an estimated 2 matches for "print_iommu_reg".
Did you mean:
print_iommu_regs
2010 Mar 11
0
[PATCH] VT-d: various initialization fixes
...all successfully set up pieces would be leaked.
Also keep iommu_free() from calling destroy_irq() when no irq was
ever set up.
Additionally, clear_fault_bits() has no need to read the capabilities
field from I/O memory - it''s already cached in "struct iommu".
Finally, simplify print_iommu_regs() and its output, and actually use
this function.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
--- 2010-03-02.orig/xen/drivers/passthrough/vtd/iommu.c 2010-03-09 13:51:48.000000000 +0100
+++ 2010-03-02/xen/drivers/passthrough/vtd/iommu.c 2010-03-09 13:51:03.000000000 +0100
@@ -1068,9 +...
2013 Jul 09
6
4.3 regression in booting on a particular platform
...us 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000
(XEN) [VT-D]iommu.c:1168: IOMMU: unsupported
(XEN) ---- print_iommu_regs ----
(XEN) drhd->address = 0
(XEN) VER = f0004800
(XEN) CAP = f000eef3f000e2c3
(XEN) n_fault_reg = ef
(XEN) fault_recording_offset = 3f00
(XEN) ECAP = f000ff54f000eef5
(XEN) GCMD = f0003182
(XEN) GSTS = f000312a
(XEN) RTADDR = e8000304f000fea5
(XEN) CCMD = f000eef3f000eef3
(XEN) FSTS = f000eef3...