This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [PATCH] Fix NR_PIRQS to be the same in Xen and Linux

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] Fix NR_PIRQS to be the same in Xen and Linux
From: "Natasha Jarymowycz" <natasha@xxxxxxxxxx>
Date: Tue, 12 Jul 2005 12:16:29 -0500
Delivery-date: Tue, 12 Jul 2005 17:15:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: natasha@xxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Opera M2/7.54 (Win32, build 3929)

In linux-2.6-xen-sparse/include/asm-xen/asm-i386/mach-xen/irq_vectors.h,
NR_PIRQS is 256.  But in Xen NR_PIRQS is defined to be only 128.  This
patch ups the number in Xen to 256.

Signed-off-by: Natasha Jarymowycz <natasha@xxxxxxxxxx>

diff -Nrup mercurial/xen/include/xen/sched.h 
--- mercurial/xen/include/xen/sched.h   2005-07-05 11:05:47.000000000 -0500
+++ mercurial.patched/xen/include/xen/sched.h   2005-07-12 10:33:28.000000000 
@@ -122,7 +122,7 @@ struct domain
      * domain's event-channel spinlock. Read accesses can also synchronise on
      * the lock, but races don't usually matter.
-#define NR_PIRQS 128 /* Put this somewhere sane! */
+#define NR_PIRQS 256 /* Put this somewhere sane! */
     u16              pirq_to_evtchn[NR_PIRQS];
     u32              pirq_mask[NR_PIRQS/32];

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>