search for: xs_wire

...mmand XS_RESET_WATCHES has been added in xen-unstable.hg changeset 23839:42a45baf037d. The command removes all watches and transactions for the guest. The following patches make use of the new command to wipe all existing watches during startup. Olaf Olaf Hering (2): xen/pv-on-hvm kexec: update xs_wire.h:xsd_sockmsg_type from xen-unstable xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel drivers/xen/xenbus/xenbus_xs.c | 13 +++++++++++++ include/xen/interface/io/xs_wire.h | 6 +++++- 2 files changed, 18 insertions(+), 1 deletions(-) -- 1.7.3.4...

...stration of watches will fail and some features of a PVonHVM guest are not available. The guest is still able to boot, but repeated kexec boots will fail. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- drivers/xen/xenbus/xenbus_xs.c | 20 ++++++++++++++++++++ include/xen/interface/io/xs_wire.h | 3 ++- 2 files changed, 22 insertions(+), 1 deletions(-) diff --git a/drivers/xen/xenbus/xenbus_xs.c b/drivers/xen/xenbus/xenbus_xs.c index d1c217b..bce15cf 100644 --- a/drivers/xen/xenbus/xenbus_xs.c +++ b/drivers/xen/xenbus/xenbus_xs.c @@ -618,6 +618,23 @@ static struct xenbus_watch *find...

...17:05:38 2006 -0700 @@ -34,6 +34,7 @@ #include <linux/device.h> #include <linux/notifier.h> #include <asm/semaphore.h> +#include <xen/interface/xen.h> #include <xen/interface/grant_table.h> #include <xen/interface/io/xenbus.h> #include <xen/interface/io/xs_wire.h> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...changeset: 26522:ffd30e7388ad user: Ian Jackson <Ian.Jackson@eu.citrix.com> date: Thu Feb 07 14:21:47 2013 +0000 oxenstored: Enforce a maximum message size of 4096 bytes The maximum size of a message is part of the protocol spec in xen/include/public/io/xs_wire.h Before this patch a client which sends an overly large message can cause a buffer read overrun. Note if a badly-behaved client sends a very large message then it will be difficult for them to make their connection work again-- they will probably need to reboot....

...lags); put_free_entry(ref); return TRUE; diff -r b26bdba50c41 xenpci/xenbus.c --- a/xenpci/xenbus.c Thu Nov 01 16:21:24 2007 -0700 +++ b/xenpci/xenbus.c Fri Nov 02 09:52:30 2007 -0700 @@ -20,6 +20,9 @@ Foundation, Inc., 51 Franklin Street, Fi #include "xenpci.h" #include "io/xs_wire.h" #include <stdlib.h> + +#pragma warning( disable : 4204 ) +#pragma warning( disable : 4221 ) struct xenbus_req_info { @@ -85,7 +88,7 @@ static int allocate_xenbus_id(void) KdPrint((__DRIVER_NAME " --> allocate_xenbus_id\n")); - while (1) + for (;;) { // s...

...rface/grant_table.h | 375 ++++ include/xen/interface/io/blkif.h | 94 + include/xen/interface/io/console.h | 23 include/xen/interface/io/netif.h | 156 + include/xen/interface/io/ring.h | 260 +++ include/xen/interface/io/xenbus.h | 42 include/xen/interface/io/xs_wire.h | 87 + include/xen/interface/memory.h | 145 + include/xen/interface/physdev.h | 145 + include/xen/interface/sched.h | 77 include/xen/interface/vcpu.h | 177 ++ include/xen/interface/version.h | 60 include/xen/interface/xen.h | 446...

...rface/grant_table.h | 375 ++++ include/xen/interface/io/blkif.h | 94 + include/xen/interface/io/console.h | 23 include/xen/interface/io/netif.h | 156 + include/xen/interface/io/ring.h | 260 +++ include/xen/interface/io/xenbus.h | 42 include/xen/interface/io/xs_wire.h | 87 + include/xen/interface/memory.h | 145 + include/xen/interface/physdev.h | 145 + include/xen/interface/sched.h | 77 include/xen/interface/vcpu.h | 177 ++ include/xen/interface/version.h | 60 include/xen/interface/xen.h | 446...

...rface/grant_table.h | 375 ++++ include/xen/interface/io/blkif.h | 94 + include/xen/interface/io/console.h | 23 include/xen/interface/io/netif.h | 156 + include/xen/interface/io/ring.h | 260 +++ include/xen/interface/io/xenbus.h | 42 include/xen/interface/io/xs_wire.h | 87 + include/xen/interface/memory.h | 145 + include/xen/interface/physdev.h | 145 + include/xen/interface/sched.h | 77 include/xen/interface/vcpu.h | 177 ++ include/xen/interface/version.h | 60 include/xen/interface/xen.h | 446...

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

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

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

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

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths