similar to: [PATCH] XEN: includecheck fix for drivers/xen/evtchn.c

fix the following 'make includecheck' warning: drivers/xen/evtchn.c: linux/errno.h is included more than once. Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput at gmail.com> --- drivers/xen/evtchn.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c index af03195..79bedba 100644 --- a/drivers/xen/evtchn.c

fix the following 'make includecheck' warning: drivers/xen/evtchn.c: linux/errno.h is included more than once. Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput at gmail.com> --- drivers/xen/evtchn.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c index af03195..79bedba 100644 --- a/drivers/xen/evtchn.c

fix the following 'make includecheck' warning: drivers/xen/evtchn.c: linux/errno.h is included more than once. Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput at gmail.com> --- drivers/xen/evtchn.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c index af03195..79bedba 100644 --- a/drivers/xen/evtchn.c

mk_pirq_info(), gsi_from_irq() and vector_from_irq() are static functions and no one is calling them. This fixed following compilation warnings : drivers/xen/events.c:134: warning: ?mk_pirq_info? defined but not used drivers/xen/events.c:180: warning: ?gsi_from_irq? defined but not used drivers/xen/events.c:190: warning: ?vector_from_irq? defined but not used Signed-off-by: Jaswinder

mk_pirq_info(), gsi_from_irq() and vector_from_irq() are static functions and no one is calling them. This fixed following compilation warnings : drivers/xen/events.c:134: warning: ?mk_pirq_info? defined but not used drivers/xen/events.c:180: warning: ?gsi_from_irq? defined but not used drivers/xen/events.c:190: warning: ?vector_from_irq? defined but not used Signed-off-by: Jaswinder

mk_pirq_info(), gsi_from_irq() and vector_from_irq() are static functions and no one is calling them. This fixed following compilation warnings : drivers/xen/events.c:134: warning: ?mk_pirq_info? defined but not used drivers/xen/events.c:180: warning: ?gsi_from_irq? defined but not used drivers/xen/events.c:190: warning: ?vector_from_irq? defined but not used Signed-off-by: Jaswinder

Remove duplicated #include('s) in drivers/xen/evtchn.c Signed-off-by: Huang Weiyi <weiyi.huang at gmail.com> --- drivers/xen/evtchn.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c index af03195..79bedba 100644 --- a/drivers/xen/evtchn.c +++ b/drivers/xen/evtchn.c @@ -38,7 +38,6 @@ #include <linux/string.h>

Remove duplicated #include('s) in drivers/xen/evtchn.c Signed-off-by: Huang Weiyi <weiyi.huang at gmail.com> --- drivers/xen/evtchn.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c index af03195..79bedba 100644 --- a/drivers/xen/evtchn.c +++ b/drivers/xen/evtchn.c @@ -38,7 +38,6 @@ #include <linux/string.h>

Remove duplicated #include('s) in drivers/xen/evtchn.c Signed-off-by: Huang Weiyi <weiyi.huang at gmail.com> --- drivers/xen/evtchn.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c index af03195..79bedba 100644 --- a/drivers/xen/evtchn.c +++ b/drivers/xen/evtchn.c @@ -38,7 +38,6 @@ #include <linux/string.h>

# This is a BitKeeper generated diff -Nru style patch. # # ChangeSet # 2005/05/01 17:01:17-07:00 kmacy@curly.lab.netapp.com # add SMP support to evtchn # Signed-off-by: Kip Macy <kmacy@netapp.com> # # freebsd-5.3-xen-sparse/i386-xen/include/xen_intr.h # 2005/05/01 17:01:15-07:00 kmacy@curly.lab.netapp.com +3 -0 # add SMP interfaces # #

Processing commands for control at bugs.debian.org: > reassign 469811 linux-2.6 Bug#469811: xen-hypervisor-3.0.3-1-i386-pae: kernel BUG at drivers/xen/core/evtchn.c:481 Bug reassigned from package `xen-hypervisor-3.0.3-1-i386-pae' to `linux-2.6'. > forcemerge 410807 469811 Bug#410807: linux-2.6/etch xen support - kernel BUG at drivers/xen/core/evtchn.c:481 Bug#469811:

Hello folks I see the EVTCHN driver being initialized as a part of DomainU. XEND (or domain controller) uses the EVTCHN driver to receive notifications for events on the control interface. However there is no XEND (or domain controller) that runs in DomainU. So what is the purpose of initializing EVTCHN driver in DomainU Thanks in advance Nauzad

Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r cfb49fe940fd -r 81f75ed45ec2 tools/hotplug/Linux/init.d/xencommons --- a/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 16:56:16 2011 -0700 +++ b/tools/hotplug/Linux/init.d/xencommons Tue Aug 16 17:05:18 2011 -0700 @@ -29,12 +29,18 @@ XENCONSOLED_PIDFILE=/var/run/xenconsoled.pid shopt -s extglob -if [

# HG changeset patch # User john.levon@sun.com # Date 1171946682 28800 # Node ID e8a7491ed4c57d4d82642dd954b8909d9065b377 # Parent 24a6bc1d1b93405558741a2a8fa7ba2f7c44964a Xenconsoled should ignore spurious watch event. Otherwise, it can rebind to the same evtchn of a dying domU during suspending and cause below error message: (XEN) event_channel.c:177:d0 EVTCHNOP failure: domain 0, error -22,

Package: xen-utils-3.0-unstable-1 Version: 3.0-unstable+hg11561-1 Severity: grave Justification: renders package unusable with the recent unstable kernel, the evtchn device should be created with major/minor 10, 63. Instead, it's being created with 10, 201. If fixed manually, xenstored will re-create it with the wrong minor number. This causes Xen to be entirely unusable, as xenstored is

Hi All, When xm block-detach command was done on PV-ON-HVM, the response of other disks was lost. It is because a wrong event channel was invalidated when detaching it. Not the evtchn number but the irq number is invalidated specifying it. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com> Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com> Signed-off-by:

Hi All, The interface of the evtchn has been changed as follows. ・xen-unstable.hg : cs13198 [PV-ON-HVM] Update evtchn interface to match new PV Linux interfaces. ・xen-unstable.hg : cs13197 [LINUX] Extend the event-channel interfaces to provide helper methods However, the following errors occur if pv-on-hvm is done in insmod. This patch corrected this issue. --- # insmod xen-vbd.ko

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Hi! the error suddenly appeared when rebooting one of the etch instances using xm reboot <name> on our etch server DEVIDE:~# DEVIDE kernel: ------------[ cut here ]------------ DEVIDE kernel: CPU: 3 DEVIDE:~# Message from syslogd@DEVIDE at Tue May 8 11:45:27 2007 ... Message from syslogd@DEVIDE at Tue May 8 11:45:27 2007

Keir, below/attached patch is necessary to allow SVM partitions to boot unmodified guests with xen-unstable.hg c/s 8961. c/s 8822 and 8828 (some necessary evtchn modifications) cause SVM partitions to fail with "lost interrupt" hda error during boot. We currently do not understand why these modifications are necessary and in fact, a race occurs with one part of the patch (added

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-4 Severity: critical Justification: breaks the whole system Hi! the error suddenly appeared when creating a domU using xm create <name> on our etch server The server freezes and isn't accessible via console/ssh anymore. The server is a Dell PowerEdge 2900 with 2 Quad-Core Xeon E5335 and 8Gb memory. pc307005:~# xm create -c