search for: xapic

Here is a patch for clustered xAPIC and Unisys ES7000 support in Xen. To turn the features on add CONFIG_X86_CLUSTERED_APIC and CONFIG_ES7000 defines to xen/include/asm-x86/config.h Signed off by Aravindh Puthiyaparambil <aravindh.puthiyaparambil@unisys.com> _______________________________________________ Xen-devel mailing l...

Environment: ASRock Z86 Extreme4 - Intel i5 2500 http://www.asrock.com/mb/overview.asp?Model=Z68%20Extreme4 I have installed the latest UEFI patch(1.70) and all tests were run from a reset of everything to default. I have tested with both Ubuntu 11.10 and Fedora 16 and get the same results on both, including building xen 4.2-unstable. I bought this particular MB because it had a know working vt-d

I have an Intel e1000e NIC which I put into passthrough for an HVM domain under Xen 4.2. All the corresponding hardware protections are enabled on my system (DMA + Interrupt remapping), however, once in a while I get a SERR NMI in dom0 (NMI - PCI sys error (SERR) in xl dmesg). I am wondering about its exact reason. I am thinking in the following way: [+] Under Intel VT-x, interrupts are

Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting

Adding apic_verbosity=debug gives me that (hope nothing miss-typed as I have no serial console on this box). I found a lot of suggested workarounds: - noapic as suggested in output gives an noapic isn''t support - acpi_skip_timer_override has no effect at all Thx, Florian (XEN) Initing memory sharing. (XEN) AMD-Vi: IOMMU not found! (XEN) I/O virtualisation disabled (XEN) Getting

...orig/xen/include/asm-x86/cpufeature.h 2008-05-07 12:21:37.000000000 +0200 +++ 2008-10-27/xen/include/asm-x86/cpufeature.h 2008-11-19 10:15:13.000000000 +0100 @@ -94,6 +94,7 @@ #define X86_FEATURE_SSE4_2 (4*32+20) /* Streaming SIMD Extensions 4.2 */ #define X86_FEATURE_X2APIC (4*32+21) /* Extended xAPIC */ #define X86_FEATURE_POPCNT (4*32+23) /* POPCNT instruction */ +#define X86_FEATURE_HYPERVISOR (4*32+31) /* running under some hypervisor */ /* VIA/Cyrix/Centaur-defined CPU features, CPUID level 0xC0000001, word 5 */ #define X86_FEATURE_XSTORE (5*32+ 2) /* on-CPU RNG present (xstore insn) *...

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

...s self_nmi(). __stop_this_cpu() has reverted the LAPIC + * back to its boot state, so we are unable to rely on the regular + * apic_* functions, due to ''x2apic_enabled'' being possibly wrong. + * (The likely scenario is that we have reverted from x2apic mode to + * xapic, at which point #GPFs will occur if we use the apic_* + * functions) + * + * The ICR and APIC ID of the LAPIC are still valid even during + * software disable (Intel SDM Vol 3, 10.4.7.2). As a result, we + * can deliberately queue up another NMI at the LAPIC which will not +...

...050 (r1 A M I APTIO 6222004 AMI. 3) (XEN) System RAM: 4047MB (4144632kB) (XEN) No NUMA configuration found (XEN) Faking a node at 0000000000000000-000000014e000000 (XEN) Domain heap initialised (XEN) found SMP MP-table at 000fca30 (XEN) DMI 2.6 present. (XEN) APIC boot state is ''xapic'' (XEN) Using APIC driver default (XEN) ACPI: PM-Timer IO Port: 0x408 (XEN) ACPI: ACPI SLEEP INFO: pm1x_cnt[404,0], pm1x_evt[400,0] (XEN) ACPI: 32/64X FACS address mismatch in FADT - af7f9e40/0000000000000000, using 32 (XEN) ACPI: wakeup_vec[af7f9e4c], vec_size[20] (XEN) AC...

...0x1] lint[0x1]) 2 CPUs total Local APIC address fee00000 Enabling the CPU's according to the ACPI table Intel MultiProcessor Specification v1.1 Virtual Wire compatibility mode. OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000 I/O APIC #2 Version 17 at 0xFEC00000. Processors: 2 xAPIC support is present Enabling APIC mode: Flat. Using 1 I/O APICs Kernel command line: ro root=LABEL=/ hdc=ide-scsi ide_setup: hdc=ide-scsi Initializing CPU#0 Detected 3407.863 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 6789.52 BogoMIPS Page-cache hash table entries: 131...

...OS bug, IO-APIC#%d ID is %d in the MPC table!...\n", - apic, mp_ioapics[apic].mpc_apicid); - printk(KERN_ERR "... fixing up to %d. (tell your hw vendor)\n", - reg_00.bits.ID); - mp_ioapics[apic].mpc_apicid = reg_00.bits.ID; - } - - /* Don't check I/O APIC IDs for some xAPIC systems. They have - * no meaning without the serial APIC bus. */ - if (NO_IOAPIC_CHECK) - continue; - /* - * Sanity check, is the ID really free? Every APIC in a - * system must have a unique ID or we get lots of nice - * 'stuck on smp_invalidate_needed IPI wait' messages. -...

...OS bug, IO-APIC#%d ID is %d in the MPC table!...\n", - apic, mp_ioapics[apic].mpc_apicid); - printk(KERN_ERR "... fixing up to %d. (tell your hw vendor)\n", - reg_00.bits.ID); - mp_ioapics[apic].mpc_apicid = reg_00.bits.ID; - } - - /* Don't check I/O APIC IDs for some xAPIC systems. They have - * no meaning without the serial APIC bus. */ - if (NO_IOAPIC_CHECK) - continue; - /* - * Sanity check, is the ID really free? Every APIC in a - * system must have a unique ID or we get lots of nice - * 'stuck on smp_invalidate_needed IPI wait' messages. -...