similar to: [PATCH] [Mini-OS] Make gnttab allocation/free safe

- introduce local variables (shortcuts for frequently used <dom>->grant_table) - adjust first parameter of mapcount() - drop lock acquisition from gnttab_get_version() - remove hard tabs and adjust formatting Signed-off-by: Jan Beulich <jbeulich@suse.com> Tested-by: Andrew Thomas <andrew.thomas@oracle.com> --- a/xen/common/grant_table.c +++ b/xen/common/grant_table.c @@

stubdom: permit compilation without lwip Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r b320cfe1f10f extras/mini-os/lib/sys.c --- a/extras/mini-os/lib/sys.c Thu Jun 05 13:04:07 2008 +0100 +++ b/extras/mini-os/lib/sys.c Fri Jun 06 11:28:09 2008 +0100 @@ -43,7 +43,9 @@ #include <stdlib.h> #include <math.h> +#ifdef HAVE_LWIP #include

I finally decided to build 4.0.1 on my OpenSuSE box. I''ve been plodding along and resolving issues/dependencies as needed but now I''m stumped. While building I get the following message: cc1: warnings being treated as errors netfront.c:41:32: error: variably modified ‘tx_freelist’ at file scope netfront.c:44:34: error: variably modified ‘rx_buffers’ at file scope

Hi, When running domUs with pygrub, I get errors: .... xen be core: xen be core: can''t open gnttab device can''t open gnttab device xen be core: xen be core: can''t open gnttab device can''t open gnttab device xen be core: xen be core: can''t open gnttab device ..... domUs start, but these errors continue on dom0 Configuration: dom0: Ubuntu 8.10

I have two dell servers running arch linux and xen 4.3 One of them had after installing lates xen 4.3 had been showing this error message" failed to add gnttab to physmap " I reverted back to git pull from 02/17/13 and virtual machines start fine. Can sommone point me in righ direction what could be causing the error message _______________________________________________ Xen-users

Legacy (non-pvops) gntdev drivers may require this operation to be performed when the number of grants intended to be used simultaneously exceeds a certain driver specific default limit, and qemu''s qdisk driver is an example of needing to do so. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/tools/libxc/xc_linux_osdep.c +++ b/tools/libxc/xc_linux_osdep.c @@ -541,6 +541,27 @@

This patch implements the xenidc_channel interface using grant tables but leaves the channel bring-up and tear-down sequencing to a derived class (xenidc_gnttab_channel implements that). This code is part of the implementation of the xenidc_endpoint used for interdomain communication by the USB driver. Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com>

Rather than just leaking pages that can''t be freed at the point where access permission for the backend domain gets revoked, put them on a list and run a timer to (infrequently) retry freeing them. (This can particularly happen when unloading a frontend driver when devices are still present, and the backend still has them in non-closed state or hasn''t finished closing them yet.)

From: Matt Wilson <msw@amazon.com> Commit f62805f1 introduced a bug where lazy MMU mode isn''t exited if a m2p_add/remove_override call fails. Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com> Cc: David Vrabel <david.vrabel@citrix.com> Cc: Anthony

Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/drivers/xen/core/gnttab.c +++ b/drivers/xen/core/gnttab.c @@ -35,6 +35,7 @@ #include <linux/sched.h> #include <linux/mm.h> #include <linux/seqlock.h> +#include <linux/timer.h> #include <xen/interface/xen.h> #include <xen/gnttab.h> #include <asm/pgtable.h> @@ -183,35 +184,119 @@ int

This patch is cleaned up of the patch which was sent as http://lists.xensource.com/archives/html/xen-devel/2007-06/msg00324.html # HG changeset patch # User yamahata@valinux.co.jp # Date 1181545986 -32400 # Node ID 69e2dd4e06c405a92717c5f1818f5096e1dc0bcd # Parent d5e0eb7dd069c0ffc1854da81aa143ccfb0ad66e make dma address conversion logic of gnttab dma arch specific. gnttab_dma_map_page() and

Hello, sorry to bother you with this: while trying to compile mini-os from xen-unstable.hg, I noticed that compilation failed like this: gcc -fno-builtin -Wall -Werror -Wredundant-decls -Wno-format -Wstrict-prototypes -Wnested-externs -Wpointer-arith -Winline -m32 -march=i686 -g -Iinclude -Iinclude/x86 -Iinclude/x86/x86_32 -c gnttab.c -o gnttab.o gnttab.c: In Funktion »init_gnttab«:

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual block

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest as a paravirt_ops backend. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen hvc console (console=hvc0) *

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual

Hi Andi, This patch series implements the Linux Xen guest in terms of the paravirt-ops interface. The features in implemented this patch series are: * domU only * UP only (most code is SMP-safe, but there's no way to create a new vcpu) * writable pagetables, with late pinning/early unpinning (no shadow pagetable support) * supports both PAE and non-PAE modes * xen console * virtual