similar to: [PATCH] x86-64: IOMMU compilation

plain text document attachment (xx-paravirt-bios.patch) Add an interface for paravirt ops and e820. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/e820.c =================================================================== --- clean-start.orig/arch/x86_64/kernel/e820.c +++

plain text document attachment (xx-paravirt-bios.patch) Add an interface for paravirt ops and e820. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/e820.c =================================================================== --- clean-start.orig/arch/x86_64/kernel/e820.c +++

Remove unused and pointless bits from mpparse.c (and other files where they are related to it). Of what remains, move whatever possible into .init.*, and some data items into .data.read_mostly. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2011-03-09.orig/xen/arch/x86/acpi/boot.c +++ 2011-03-09/xen/arch/x86/acpi/boot.c @@ -177,7 +177,8 @@ acpi_parse_x2apic(struct acpi_subtable_h

The DMI checks that force the use of the bigsmp APIC driver are for systems that are no longer supported by Xen (32-bit x86). Signed-off-by: Matt Wilson <msw@amazon.com> Cc: Keir Fraser <keir@xen.org> Cc: Jan Beulich <jbeulich@suse.com> Cc: Andrew Cooper <andrew.cooper3@citrix.com> --- xen/arch/x86/genapic/bigsmp.c | 30 +----------------------------- 1 files changed, 1

Forcibly enabling the MMCFG space on AMD Fam10 CPUs cannot be expected to work since with the firmware not being aware of the address range used it cannot possibly reserve the space in E820 or ACPI resources. Hence we need to manually insert the range into the E820 table, and enable the range only when the insertion actually works without conflict. Further, the actual enabling of the space is

Here are the relevant details. all help is greatly appreciated. xenbox linux # uname -a Linux xenbox.localhost 2.6.14-gentoo-r2 #2 Mon Dec 5 16:17:58 Local time zone must be set--see zic manua x86_64 Intel(R) Xeon(TM) CPU 3.00GHzGenuineIntel GNU/Linux xenbox linux # lspci 0000:00:00.0 Host bridge: Intel Corporation E7520 Memory Controller Hub (rev 0c) 0000:00:00.1 Class ff00: Intel Corporation

Also, rename to MOVE_CLEANUP_VECTOR to be in line with the other IPI names. This requires bumping LAST_HIPRIORITY_VECTOR, but does mean that the range FIRST-LAST_HIPRIORITY_VECTORs are free once again. Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> diff -r 0268e7380953 -r c7884dbb6f7d xen/arch/x86/apic.c --- a/xen/arch/x86/apic.c Mon Sep 05 15:10:28 2011 +0100 +++

The iommu is enabled by default when xen is booting and later disabled in iommu_setup() when no iommu is present. But under some circumstances iommu code can be called before iommu_setup() is processed. If there is no iommu available xen crashes. This can happen for example when panic(...) is called as introduced with the patch "x86-64: detect processors subject to AMD erratum #121 and

From: Jan Kiszka <jan.kiszka at siemens.com> Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse non-root kernel. Signed-off-by: Jan Kiszka <jan.kiszka at

From: Jan Kiszka <jan.kiszka at siemens.com> Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse non-root kernel. Signed-off-by: Jan Kiszka <jan.kiszka at

From: Jan Kiszka <jan.kiszka at siemens.com> Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse non-root kernel. Signed-off-by: Jan Kiszka <jan.kiszka at

From: Jan Kiszka <jan.kiszka at siemens.com> Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse non-root kernel. Signed-off-by: Jan Kiszka <jan.kiszka at

From: Jan Kiszka <jan.kiszka at siemens.com> Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse non-root kernel. Signed-off-by: Jan Kiszka <jan.kiszka at

Does Xen 3.0.0 actually support the IOMMU on x86_64? I''ve tried building with a couple of different configurations, and it always fails if I''ve enabled CONFIG_GART_IOMMU. The problems center around undefined references to functions such as dma_alloc_coherent, dma_free_coherent, iommu_setup, iommu_hole_init, force_iommu, iommu_aperture_allowed, and so on. In all cases, changing

Serve an arbitrary map of regions of the underlying plugin. --- common-rules.mk | 1 + configure.ac | 1 + filters/map/Makefile.am | 61 +++ filters/map/map.c | 256 +++++++++ filters/map/maptype.c | 493 ++++++++++++++++++ filters/map/maptype.h

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. Signed-off-by: Fengzhe Zhang <fengzhe.zhang@intel.com> diff -r 02c0af2bf280

Hello When i try to make world (any) from xen-3.0.2 to xen-unstable-src I gat following error : gcc -O2 -fomit-frame-pointer -DNDEBUG -m64 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/test1/xen-unstable/xen/include

From: Rusty Russell <rusty@rustcorp.com.au> lguest is a simple hypervisor for Linux on Linux. Unlike kvm it doesn't need VT/SVM hardware. Unlike Xen it's simply "modprobe and go". Unlike both, it's 5000 lines and self-contained. Performance is ok, but not great (-30% on kernel compile). But given its hackability, I expect this to improve, along with the

From: Rusty Russell <rusty@rustcorp.com.au> lguest is a simple hypervisor for Linux on Linux. Unlike kvm it doesn't need VT/SVM hardware. Unlike Xen it's simply "modprobe and go". Unlike both, it's 5000 lines and self-contained. Performance is ok, but not great (-30% on kernel compile). But given its hackability, I expect this to improve, along with the

Hi all, I'm upgrading my old F9 mail server to Centos 7 and all is going well. However, I've got a problem with recently created users. I've rsync'd /home and /var/spool/mail after moving /etc/passwd and /etc/group I used the default locations on the old F9 server, i.e. mail delivered to /var/spool/mail/%u by EXIM and Dovecot using that as the inbox. Dovecot then used ~/mail/