search for: config_xen

hi all, I noticed "CONFIG_XEN" appears many times in Xen source code. I''m confused about the meaning of "CONFIG_XEN". For example, in "gnttab.c", the definations of gnttab_map() and gnttab_resume() vary with "ifdef CONFIG_XEN" or not. And I also noticed ifndef CONFIG_XEN ,...

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested

Hi. The patch I send before was too large so that it was dropped from the maling list. I'm sending again with smaller size. This patch set is the xen paravirtualization of hand written assenbly code. And I expect that much clean up is necessary before merge. We really need the feed back before starting actual clean up as Eddie already said before. Eddie discussed how to clean up and suggested

...f..7c12c08 100644 > > --- a/include/asm-ia64/meminit.h > > +++ b/include/asm-ia64/meminit.h > > @@ -18,10 +18,17 @@ > > * - crash dumping code reserved region > > * - Kernel memory map built from EFI memory map > > * - ELF core header > > + * ifdef CONFIG_XEN > > + * - xen start info > > + * endif > > * > > * More could be added if necessary > > */ > > +#ifdef CONFIG_XEN > > #define IA64_MAX_RSVD_REGIONS 8 > > +#else > > +#define IA64_MAX_RSVD_REGIONS 9 > > +#endif > > This one se...

...f..7c12c08 100644 > > --- a/include/asm-ia64/meminit.h > > +++ b/include/asm-ia64/meminit.h > > @@ -18,10 +18,17 @@ > > * - crash dumping code reserved region > > * - Kernel memory map built from EFI memory map > > * - ELF core header > > + * ifdef CONFIG_XEN > > + * - xen start info > > + * endif > > * > > * More could be added if necessary > > */ > > +#ifdef CONFIG_XEN > > #define IA64_MAX_RSVD_REGIONS 8 > > +#else > > +#define IA64_MAX_RSVD_REGIONS 9 > > +#endif > > This one se...

On Tue, Mar 22, 2011 at 06:03:28PM +0530, Trinabh Gupta wrote: > This patch implements a default cpuidle driver for xen. > Earlier pm_idle was flipped to default_idle. Maybe there > is a better way to ensure default_idle is called > without using this cpuidle driver. Please also CC the Xen devel mailing list (I did this for you) I couldn''t find it in the description, but I

There is no need to include pv-guest only object files in a kernel not configured to support those. Move Xen's irq.o, xen-asm*.o and pv parts of entry_*.o into CONFIG_XEN_PV sections. Signed-off-by: Juergen Gross <jgross at suse.com> --- arch/x86/entry/entry_32.S | 4 +++- arch/x86/entry/entry_64.S | 6 ++++-- arch/x86/xen/Makefile | 8 ++++---- 3 files changed, 11 insertions(+), 7 deletions(-) diff --git a/arch/x86/entry/entry_32.S b/arch/x86/entry/ent...

...Fri Apr 04 13:27:48 2008 +0100 +++ b/drivers/acpi/hardware/hwsleep.c Fri Apr 04 10:22:07 2008 -0600 @@ -227,7 +227,7 @@ acpi_status asmlinkage acpi_enter_sleep_ u32 PM1Bcontrol; struct acpi_bit_register_info *sleep_type_reg_info; struct acpi_bit_register_info *sleep_enable_reg_info; -#ifndef CONFIG_XEN +#if !(defined(CONFIG_XEN) && defined(CONFIG_X86)) u32 in_value; #else int err; @@ -331,7 +331,7 @@ acpi_status asmlinkage acpi_enter_sleep_ ACPI_FLUSH_CPU_CACHE(); -#ifndef CONFIG_XEN +#if !(defined(CONFIG_XEN) && defined(CONFIG_X86)) status = acpi_hw_register_write(AC...

Implement a simple Xen APIC module and use it to deliver MSI/MSIX for Xen HVM guests.

...virtio_ring.c b/drivers/virtio/virtio_ring.c > index c169c6444637..305c05cc249a 100644 > --- a/drivers/virtio/virtio_ring.c > +++ b/drivers/virtio/virtio_ring.c > @@ -47,6 +47,18 @@ > > static bool vring_use_dma_api(void) > { > +#if defined(CONFIG_X86) && defined(CONFIG_XEN) > + /* > + * In theory, it's possible to have a buggy QEMU-supposed > + * emulated Q35 IOMMU and Xen enabled at the same time. On > + * such a configuration, virtio has never worked and will > + * not work without an even larger kludge. Instead, enable > + * the DMA AP...

...virtio_ring.c b/drivers/virtio/virtio_ring.c > index c169c6444637..305c05cc249a 100644 > --- a/drivers/virtio/virtio_ring.c > +++ b/drivers/virtio/virtio_ring.c > @@ -47,6 +47,18 @@ > > static bool vring_use_dma_api(void) > { > +#if defined(CONFIG_X86) && defined(CONFIG_XEN) > + /* > + * In theory, it's possible to have a buggy QEMU-supposed > + * emulated Q35 IOMMU and Xen enabled at the same time. On > + * such a configuration, virtio has never worked and will > + * not work without an even larger kludge. Instead, enable > + * the DMA AP...

...h/i386/kernel/Makefile 2007-03-05 10:00:18.000000000 +0100 +++ head-2007-02-27/arch/i386/kernel/Makefile 2007-02-27 16:27:37.000000000 +0100 @@ -74,6 +74,52 @@ $(obj)/vsyscall-%.so: $(src)/vsyscall.ld $(obj)/vsyscall-%.o $(obj)/$(vsyscall_note) FORCE $(call if_changed,syscall) +ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can assemble it. +# Note: kbuild does not track this dependency due to usage of .include +$(obj)/vsyscall.o: $(obj)/vsyscall-int80.rel $(obj)/vs...

...h/i386/kernel/Makefile 2007-03-05 10:00:18.000000000 +0100 +++ head-2007-02-27/arch/i386/kernel/Makefile 2007-02-27 16:27:37.000000000 +0100 @@ -74,6 +74,52 @@ $(obj)/vsyscall-%.so: $(src)/vsyscall.ld $(obj)/vsyscall-%.o $(obj)/$(vsyscall_note) FORCE $(call if_changed,syscall) +ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can assemble it. +# Note: kbuild does not track this dependency due to usage of .include +$(obj)/vsyscall.o: $(obj)/vsyscall-int80.rel $(obj)/vs...

...h/i386/kernel/Makefile 2007-03-05 10:00:18.000000000 +0100 +++ head-2007-02-27/arch/i386/kernel/Makefile 2007-02-27 16:27:37.000000000 +0100 @@ -74,6 +74,52 @@ $(obj)/vsyscall-%.so: $(src)/vsyscall.ld $(obj)/vsyscall-%.o $(obj)/$(vsyscall_note) FORCE $(call if_changed,syscall) +ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can assemble it. +# Note: kbuild does not track this dependency due to usage of .include +$(obj)/vsyscall.o: $(obj)/vsyscall-int80.rel $(obj)/vs...

Hi Keir, This patch updates the ia64 buildconfigs, enabling pcifront for all kernels and pciback for -xen and -xen0. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 4833dc75ce4d buildconfigs/linux-defconfig_xen0_ia64 --- a/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 17:52:57 2006 +0100 +++ b/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 16:54:09 2006 -0600 @@ -1,7 +1,7 @@ # # Automatically generated make config: don''t edit # Linux kernel version: 2.6.16.13-xen0 -# Fri Jun 30 12:59:19...

Dear List, I?m trying to figure out *memory page sharing***using HVM on Xen 4.0.1, but I?m not really able to find some useful information or sources about this issue. I just found two links porviding these sources: http://knol.google.com/k/learning-grant-tables http://blog.chinaunix.net/space.php?uid=20286427&do=blog&id=109114 Both are not working.. I think they are made for an older

Hello everybody, I dont found the new feature about kernel 3.0 and Xen DOM0. Where Kernel 3.0 has native support in dom0? how would I enable this option. In my currently kernel (gentoo source 3.0 and vanilla kernel 3.0) don''t found Xen device drivers, need i enable anything? thanks! -- ------------------- Pablo J. Villarruel / pablo@libo.com.ar

Hi linux/ia64 developers. Few days before Eddie posted the mail for Linux/IA64 paravirtualization. But only a few responded partially because there was no reviewable patches. Here is the patches for xen/ia64 Linux paravirtualization. The goal is to merge IA64 xen Linux paravirtualization for both domU and dom0 eventually. However the first step is to merge domU portion. As you can see from the

...rch/*/xen/ - contains xen code that is archdep linux/drivers/xen/core/ - contains xen code that is common to all xen architectures, but is not specific to a particular driver class linux/drivers/xen/{blkback,...}/ - contains xen code that is (or soon will be) common for specific drivers CONFIG_XEN is used in config/Makefiles/code. CONFIG_XEN_arch (e.g. CONFIG_XEN_X86) is used (only if absolutely necessary) in xen common code to indicate code that is archdep [1] this includes header files containing macros/inlines to "arch-dep''ify" code in linux/drivers/xen; th...

...; - *(uint32_t *)(signature + 4) = ecx; - *(uint32_t *)(signature + 8) = edx; - signature[12] = 0; - - if (!strcmp("XenVMMXenVMM", signature) && ((eax - base) >= 2)) - return base; - } - - return 0; + return hypervisor_cpuid_base("XenVMMXenVMM", 2); } #ifdef CONFIG_XEN -- 1.7.1