similar to: [PATCH] xen/xenbus: silence GCC warning

Add xs_reset_watches function to shutdown watches from old kernel after kexec boot. The old kernel does not unregister all watches in the shutdown path. They are still active, the double registration can not be detected by the new kernel. When the watches fire, unexpected events will arrive and the xenwatch thread will crash (jumps to NULL). An orderly reboot of a hvm guest will destroy the

The following series improves kexec in a Xen PVonHVM guest. It is available via git: git://github.com/olafhering/linux.git xen-kexec-XS_RESET_WATCHES-3.0 A new xenstored command 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

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1325788840 -3600 # Node ID 2f5a98692acde9e74d4009f50f83a8aa08296310 # Parent 3a22ed3ec534799b3cab55b0dc0a7380e701ecbe add feature flag to xenstore for XS_RESET_WATCHES Tell guest about availibilty of xenstoreds XS_RESET_WATCHES function. Guests can not issue this command unconditionally because some buggy toolstacks (such as

Hi, since the printk_ratelimit() function shouldn't be used anymore, I replaced it in a few files with printk_ratelimited(). If you wish some more patches I can send more in. Greets, Manu Manuel Zerpies (11): drivers/ide: use printk_ratelimited() instead of printk_ratelimit() drivers/tty: use printk_ratelimited() instead of printk_ratelimit() net/can: use printk_ratelimited() instead

Hi, since the printk_ratelimit() function shouldn't be used anymore, I replaced it in a few files with printk_ratelimited(). If you wish some more patches I can send more in. Greets, Manu Manuel Zerpies (11): drivers/ide: use printk_ratelimited() instead of printk_ratelimit() drivers/tty: use printk_ratelimited() instead of printk_ratelimit() net/can: use printk_ratelimited() instead

Hi, since the printk_ratelimit() function shouldn't be used anymore, I replaced it in a few files with printk_ratelimited(). If you wish some more patches I can send more in. Greets, Manu Manuel Zerpies (11): drivers/ide: use printk_ratelimited() instead of printk_ratelimit() drivers/tty: use printk_ratelimited() instead of printk_ratelimit() net/can: use printk_ratelimited() instead

Hi, there. I am running CentOS 4.4 on HVM Domain. And I tried Para-virtual driver for HVM Domain. Hunged up then "modprobe xenbus". My Domain-0 information: OS: CentOS 4.4 xen: 3.0.4.1 kernel: 2.6.16.33-xen_3.0.4.1 My HVM Domain information: OS: CentOS 4.4 Kernel: 2.6.9-42.0.10.EL PV Drv: xen-unstable.hg I traced the source code. I think problem at line:132 in xenbus_xs.c. It stopped

Directly including ../tools breaks building in separate object tree, as well as building from mkpatch patch (I believe Rik hit that one). This puts xenstore headers in linux-public. Signed-off-by: Chris Wright <chrisw@osdl.org> --- a/linux-2.6-xen-sparse/drivers/xen/xenbus/Makefile Mon Aug 8 18:43:57 2005 +++ b/linux-2.6-xen-sparse/drivers/xen/xenbus/Makefile Mon Aug 8 15:15:06 2005 @@

virtio_balloon.h exports "u16" and "u64" to userspace. Use "__u16" and "__u64" instead. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Tested with a kernel build. 1) Both types are used in this header for quite some time now. So is my patch flawed or doesn't userspace actually use virtio_balloon.h? include/uapi/linux/virtio_balloon.h

virtio_balloon.h exports "u16" and "u64" to userspace. Use "__u16" and "__u64" instead. Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) Tested with a kernel build. 1) Both types are used in this header for quite some time now. So is my patch flawed or doesn't userspace actually use virtio_balloon.h? include/uapi/linux/virtio_balloon.h

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- man/extlinux.1 | 6 +++--- man/syslinux.1 | 10 +++------- 2 files changed, 6 insertions(+), 10 deletions(-) diff --git a/man/extlinux.1 b/man/extlinux.1 index 3192122..62bf3b1 100644 --- a/man/extlinux.1 +++ b/man/extlinux.1 @@ -57,8 +57,8 @@ about your system and your BIOS; the vast majority of all problems reported turn out to

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) If I build syslinux on a system without mingw a (successful) build will end with: ls: cannot access win32/syslinux.exe: No such file or directory ls: cannot access win64/syslinux64.exe: No such file or directory [...] make: [all] Error 2 (ignored) Ie, it ends with an ignored error. That's confusing (and a bit

Hello, This patch allows userspace tools on a domU to setup a watch on the xenstore. It does this by intercepting XS_WATCH requests written to /proc/xen/xenbus and then re-submitting the request to the in-kernel xenstore interface, in linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_xs.c. When a callback occurs, an in-kernel function is invoked, which then reconstructs a response in the format

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- syslinux accepts a --directory (or -d) option. As far as I can see this option only affects the installation location of the ldlinux.sys file. (It also affects the boot sector that syslinux generates, but that is not something user visible.) Currently man/syslinux.1 talks about the "SYSLINUX control files". That is not entirely

Hi folks, we (the company i am working for) are running several dozens of virtualisation servers using CentOS 6 + Xen4CentOS as the virtualisation infrastructure. With the latest versions of all packages installed [1], we see failures in live-migration of stock-CentOS6 HVM guests, leaving a "Domain-unnamed" on the source host, while the migrated guest runs fine on the target host.

Currently PVHVM Linux guests after ddacf5ef684a "xen/pv-on-hvm kexec: add xs_reset_watches to shutdown watches from old kernel" hang when run against oxenstored because it does not handle the unknown XS_RESET_WATCHES operation and does not reply. The symptom of this issue is a hang during boot at this point: cpu 1 spinlock event irq 70 CPU 1 irqstacks, hard=dec94000

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

Hi, Anybody (Christian?) could please tell me if we can get the support for registering watch with /proc/xen/xenbus? (..OK, I know that we will change it this /proc stuff to a device soon) So far we can only do read/write/rm. I really miss the xen watch feature. Many thanks, Hieu _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com