search for: iommu_supports_eim

...lting in find_iommu_for_device() to be called in the context of disable_IO_APIC() / __stop_this_cpu(). This patch fixes this by keeping the iommu disabled until iommu_setup() is entered. Originally-by: Ronny Hegewald <ronny.hegewald@online.de> In order for iommu_enable to be off initially, iommu_supports_eim() must not depend on it anymore, nor must acpi_parse_dmar(). The former in turn requires that iommu_intremap gets uncoupled from iommu_enabled (in particular, failure during IOMMU setup should no longer result in iommu_intremap getting cleared by generic code; IOMMU specific code can still do so pr...

>>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: > So it seems like dom0 is unable to (correctly) bind to some hardware > interrupts. I wonder if these messages from Xen's dmesg are relevant. > (XEN) Not enabling x2APIC: depends on iommu_supports_eim. > (XEN) I/O virtualisation disabled > (XEN) Enabled directed EOI with ioapic_ack_old on! The last one certainly isn't, and the first two shouldn't (albeit the non-Xen kernel is running in x2APIC mode). That difference is likely because the Xen and non-Xen boots are with differing BI...

...Beulich wrote: >>>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: >> So it seems like dom0 is unable to (correctly) bind to some hardware >> interrupts. I wonder if these messages from Xen's dmesg are relevant. >> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >> (XEN) I/O virtualisation disabled >> (XEN) Enabled directed EOI with ioapic_ack_old on! > > The last one certainly isn't, and the first two shouldn't (albeit the > non-Xen kernel is running in x2APIC mode). That difference is likely > because the Xen and non-Xen...

...Beulich wrote: >>>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: >> So it seems like dom0 is unable to (correctly) bind to some hardware >> interrupts. I wonder if these messages from Xen's dmesg are relevant. >> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >> (XEN) I/O virtualisation disabled >> (XEN) Enabled directed EOI with ioapic_ack_old on! > The last one certainly isn't, and the first two shouldn't (albeit the > non-Xen kernel is running in x2APIC mode). That difference is likely > because the Xen and non-Xen boots...

1: IOMMU: properly check whether interrupt remapping is enabled 2: AMD IOMMU: only disable when certain IVRS consistency checks fail 3: VT-d: deal with 5500/5520/X58 errata Patch 1 and 2 are version 2 of a previously submitted, then withdrawn patch following up after XSA-36. Patch 3 is version 3 of a patch previously sent by Malcolm and Andrew. Signed-off-by: Jan Beulich

...omparison. > >>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: > > So it seems like dom0 is unable to (correctly) bind to some hardware > > interrupts. I wonder if these messages from Xen's dmesg are relevant. > > (XEN) Not enabling x2APIC: depends on iommu_supports_eim. > > (XEN) I/O virtualisation disabled > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > The last one certainly isn't, and the first two shouldn't (albeit the > non-Xen kernel is running in x2APIC mode). That difference is likely > because the Xen and non-X...

...Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a701 base: 0xfed00000 (XEN) Xen ERST support is initialized. (XEN) Using ACPI (MADT) for SMP configuration information (XEN) SMP: Allowing 128 CPUs (120 hotplug CPUs) (XEN) IRQ limits: 24 GSI, 1528 MSI/MSI-X (XEN) Not enabling x2APIC: depends on iommu_supports_eim. (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 3292.659 MHz processor. (XEN) Initing memory sharing. (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 (XEN) mce_intel.c:717: MCA Capability: BCAST 1 SER 0 CMCI 1 firstbank 0 extended MCE MSR 0 (XEN) Intel machine check...

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

Hi there! I just fresh-installed Xen on new server, Xeon E5-2620, and noticed following thing: node1 ~ # xl info -n host : node1 release : 3.8.8 version : #1 SMP Tue Apr 23 20:54:17 MSK 2013 machine : x86_64 nr_cpus : 6 max_cpu_id : 5 nr_nodes : 1 cores_per_socket : 6 threads_per_core

...20 and twice for 22). The contents of /proc/interrupts under native might tell you what those other interrupts are... So it seems like dom0 is unable to (correctly) bind to some hardware interrupts. I wonder if these messages from Xen's dmesg are relevant. (XEN) Not enabling x2APIC: depends on iommu_supports_eim. (XEN) I/O virtualisation disabled (XEN) Enabled directed EOI with ioapic_ack_old on! Ian. -------------- next part -------------- root at xen-3:~# lsusb Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated R...

Ian Campbell <ijc at hellion.org.uk> writes: #Please boot with loglvl=all on the hypervisor command line for this too. No problem Ian, Here are some results with (now) the latest BIOS version 41. (was version 35) This is a fresh new install of Debian "Testing" non production server. Just wanted to run some test domU's. Changing USB ports, no effect. I even tried a different