search for: x2apic

...EN) ACPI: LAPIC (acpi_id[0x3b] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3c] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3d] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3e] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3f] lapic_id[0xff] disabled) (XEN) ACPI: X2APIC (apic_id[0x00] uid[0x00] disabled) (XEN) ACPI: X2APIC (apic_id[0x01] uid[0x01] disabled) (XEN) ACPI: X2APIC (apic_id[0x02] uid[0x02] disabled) (XEN) ACPI: X2APIC (apic_id[0x03] uid[0x03] disabled) (XEN) ACPI: X2APIC (apic_id[0x04] uid[0x04] disabled) (XEN) ACPI: X2APIC (apic_id[0x05] uid[0x05] disa...

...ks: I run into a problem when enabling Xen in next generation server platforms with Xen c/s is 21380. Xen reported "CPU Not responding" when booting up 32 CPUs( 2 sockets with 8 cores/16threads total). The log files belonging showed something wrong with APCI. So I added x2apic=0 in the xen grub line, but the symptom remained. However, Native RHEL5.5 can normally started in this platforms. Does anyone meet this problem and know how to solve it or give some hints? Thanks very much! Btw, I also tried the latest xen (version 4.1 rc5). Hy...

x86:x2apic: Disable x2apic on x86-32 permanently x2apic initialization on x86_32 uses vcpu pointer before it is initialized. As x2apic is unlikely to be used on x86_32, this patch disables x2apic permanently on x86_32. It also asserts the sanity of vcpu pointer before dereference to prevent further misuse....

...or GSI16, once for 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 808...

Please consider this patch to allow x2apic without IR support when running on VMware platform. Tested on top of 3.8-rc3. Thanks, Alok -- Allow x2apic without IR on VMware platform. From: Alok N Kataria <akataria at vmware.com> This patch updates x2apic initializaition code to allow x2apic on VMware platform even without interrupt...

Please consider this patch to allow x2apic without IR support when running on VMware platform. Tested on top of 3.8-rc3. Thanks, Alok -- Allow x2apic without IR on VMware platform. From: Alok N Kataria <akataria at vmware.com> This patch updates x2apic initializaition code to allow x2apic on VMware platform even without interrupt...

On platforms which supports x2APIC, the patches enable this enhancement for Xen. The x2APIC specification is available at http://www.intel.com/products/processor/manuals/ http://download.intel.com/design/processor/specupdt/318148.pdf apicid_u8_2_u32.patch: changes the ''apicid'' from u8 to u32; x2apic.patch: replac...

...r memmap [ 0.000000] DMA32 zone: 711520 pages, LIFO batch:31 [ 0.000000] Normal zone: 17920 pages used for memmap [ 0.000000] Normal zone: 1310720 pages, LIFO batch:31 [ 0.000000] ACPI: PM-Timer IO Port: 0x408 [ 0.000000] ACPI: Local APIC address 0xfee00000 [ 0.000000] ACPI: X2APIC (apic_id[0x00] uid[0x00] disabled) [ 0.000000] ACPI: X2APIC (apic_id[0x01] uid[0x01] disabled) [ 0.000000] ACPI: X2APIC (apic_id[0x02] uid[0x02] disabled) [ 0.000000] ACPI: X2APIC (apic_id[0x03] uid[0x03] disabled) [ 0.000000] ACPI: X2APIC (apic_id[0x04] uid[0x04] disabled) [ 0.00000...

This patch masks PIC and IOAPIC RTE''s before x2APIC enabling, unmask and restore them after x2APIC enabling. It also really enables interrupt remapping before x2APIC enabling instead of just checking interrupt remapping setting. This patch also handles all x2APIC configuration including BIOS settings and command line settings. Especially, it handle...

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.

Hi, on a Nehalem system with VT-d enabled we are seeing strange ACPI-Table contents, especially a corrupted DMAR entry. The hypervisor shows following data on boot: (XEN) ACPI: RSDP 000F80E0, 0024 (r2 PTLTD ) (XEN) ACPI: XSDT BF7C469E, 00D4 (r1 PTLTD XSDT 60000 LTP 0) (XEN) ACPI: FACP BF7C9CC9, 00F4 (r3 FSC TYLERBRG 60000 PTL F4240) (XEN) ACPI: DSDT BF7C4772, 54D3 (r1

...EN) ACPI: LAPIC (acpi_id[0x3b] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3c] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3d] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3e] lapic_id[0xff] disabled) (XEN) ACPI: LAPIC (acpi_id[0x3f] lapic_id[0xff] disabled) (XEN) ACPI: X2APIC (apic_id[0x00] uid[0x00] disabled) (XEN) ACPI: X2APIC (apic_id[0x01] uid[0x01] disabled) (XEN) ACPI: X2APIC (apic_id[0x02] uid[0x02] disabled) (XEN) ACPI: X2APIC (apic_id[0x03] uid[0x03] disabled) (XEN) ACPI: X2APIC (apic_id[0x04] uid[0x04] disabled) (XEN) ACPI: X2APIC (apic_id[0x05] uid[0x05] disa...

...ight is still affected by this library error http://www.gossamer-threads.com/lists/xen/devel/234300 However, after correcting the library error, I was able to complete the unstable build. In both cases, it either stops with a panic/blank screen, or just reboots. Here are some other notes: 1) If x2apic is enabled on the motherboard, it almost immediately reboots with any of the configurations above 2) The boot gets to here: (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. Then goes to a "(XEN)Failed to bring up CPU x(error -5)" and this is where it hangs with th...

Other than for the legacy APIC, the x2APIC MADT entries have valid ranges possibly extending beyond what our internal arrays can handle, and hence we need to guard ourselves against corrupting memory here. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/acpi/boot.c +++ b/xen/arch/x86/acpi/boot.c @@ -97,7 +97,20 @@...

http://www.intel.com/content/www/us/en/chipsets/5520-and-5500-chipset-ioh-specification-update.html Stepping B-3 has two errata (#47 and #53) related to Interrupt remapping, to which the workaround is for the BIOS to completely disable interrupt remapping. These errata are fixed in stepping C-2. Unfortunately this chipset is very common and many BIOSes are not disabling remapping. We can

During debugging of another problem I found that in x2APIC mode, the destination field of the low address value wasn''t passed back correctly. While this is benign in most cases (as the value isn''t being used anywhere), it can be confusing (and misguiding) when printing the value read or when comparing it to the one previously passed into...

The "APIC-register virtualization" and "virtual-interrupt deliver" VM-execution control has no effect on the behavior of RDMSR/WRMSR if the "virtualize x2APIC mode" VM-execution control is 0. When guest uses x2APIC mode, we should enable "virtualize x2APIC mode" for APICV first. Signed-off-by: Jiongxi Li <jiongxi.li@intel.com> diff --git a/xen/arch/x86/hvm/vmx/vmcs.c b/xen/arch/x86/hvm/vmx/vmcs.c index de22e03..4807eb2 100644 --- a...

>>> 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-...

...-machine q35 makes no difference.) My CPU flags inside the crashing guest look like this: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1 whereas in a (working) -cpu qemu64 guest, they look like this: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflus...

...-machine q35 makes no difference.) My CPU flags inside the crashing guest look like this: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1 whereas in a (working) -cpu qemu64 guest, they look like this: fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflus...