From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] add architecture specific softirq headers
Date: Thu, 30 Nov 2006 09:54:00 -0700 [thread overview]
Message-ID: <1164905640.6117.5.camel@lappy> (raw)
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
We have a need for a couple architecture specific softirqs for
handling collection of system firmware error records on ia64. Rather
than add error prone architecture #ifdefs to xen/softirq.h, I propose
extending the generic header to include an architecture specific header
as in the attached patch. Thoughts? Thanks,
Alex
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
---
[-- Attachment #2: arch-softirq.patch --]
[-- Type: text/x-patch, Size: 2395 bytes --]
diff -r d1b0a5adaeab xen/include/xen/softirq.h
--- a/xen/include/xen/softirq.h Wed Nov 29 23:40:40 2006 +0000
+++ b/xen/include/xen/softirq.h Thu Nov 30 09:43:39 2006 -0700
@@ -9,7 +9,17 @@
#define NMI_SOFTIRQ 4
#define PAGE_SCRUB_SOFTIRQ 5
#define TRACE_SOFTIRQ 6
-#define NR_SOFTIRQS 7
+
+#define NR_COMMON_SOFTIRQS 7
+
+#include <asm/softirq.h>
+
+#ifndef NR_ARCH_SOFTIRQS
+#warning No architecture defined NR_ARCH_SOFTIRQS, update asm/softirq.h
+#define NR_ARCH_SOFTIRQS 0
+#endif
+
+#define NR_SOFTIRQS (NR_COMMON_SOFTIRQS + NR_ARCH_SOFTIRQS)
#ifndef __ASSEMBLY__
diff -r d1b0a5adaeab xen/include/asm-ia64/softirq.h
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xen/include/asm-ia64/softirq.h Thu Nov 30 09:39:28 2006 -0700
@@ -0,0 +1,14 @@
+#ifndef __ASM_SOFTIRQ_H__
+#define __ASM_SOFTIRQ_H__
+
+/*
+ * This header only provides architecture specific softirqs.
+ * It should not be included except through xen/softirqs.h
+ */
+#if !defined(NR_COMMON_SOFTIRQS) || defined(NR_SOFTIRQS)
+#error asm/softirq.h should only be included from xen/softirq.h
+#endif
+
+#define NR_ARCH_SOFTIRQS 0
+
+#endif /* __ASM_SOFTIRQ_H__ */
diff -r d1b0a5adaeab xen/include/asm-powerpc/softirq.h
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xen/include/asm-powerpc/softirq.h Thu Nov 30 09:35:54 2006 -0700
@@ -0,0 +1,14 @@
+#ifndef __ASM_SOFTIRQ_H__
+#define __ASM_SOFTIRQ_H__
+
+/*
+ * This header only provides architecture specific softirqs.
+ * It should not be included except through xen/softirqs.h
+ */
+#if !defined(NR_COMMON_SOFTIRQS) || defined(NR_SOFTIRQS)
+#error asm/softirq.h should only be included from xen/softirq.h
+#endif
+
+#define NR_ARCH_SOFTIRQS 0
+
+#endif /* __ASM_SOFTIRQ_H__ */
diff -r d1b0a5adaeab xen/include/asm-x86/softirq.h
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/xen/include/asm-x86/softirq.h Thu Nov 30 09:49:27 2006 -0700
@@ -0,0 +1,14 @@
+#ifndef __ASM_SOFTIRQ_H__
+#define __ASM_SOFTIRQ_H__
+
+/*
+ * This header only provides architecture specific softirqs.
+ * It should not be included except through xen/softirqs.h
+ */
+#if !defined(NR_COMMON_SOFTIRQS) || defined(NR_SOFTIRQS)
+#error asm/softirq.h should only be included from xen/softirq.h
+#endif
+
+#define NR_ARCH_SOFTIRQS 0
+
+#endif /* __ASM_SOFTIRQ_H__ */
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
reply other threads:[~2006-11-30 16:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1164905640.6117.5.camel@lappy \
--to=alex.williamson@hp.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.