From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH][linux-2.6.18-xen.hg]
Date: Thu, 26 Jul 2007 11:14:44 -0400 [thread overview]
Message-ID: <46A8BA64.7020609@virtualiron.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 310 bytes --]
This patch makes the code adding PF_NOFREEZE conditional on the kernel
version.
PF_NOFREEZE first showed up in 2.6.6-rc2
This allows the xenbus code to continue to compile against kernels pre
2.6.6 - like SLES9 (2.6.5)
Patch: linux-xenbus-legacy.patch
Signed-off-by: Ben Guthro <bguthro@virtualiron.com>
[-- Attachment #2: linux-xenbus-legacy.patch --]
[-- Type: text/x-patch, Size: 729 bytes --]
diff -r d2451033c8df drivers/xen/xenbus/xenbus_xs.c
--- a/drivers/xen/xenbus/xenbus_xs.c Wed Jul 25 14:59:21 2007 -0400
+++ b/drivers/xen/xenbus/xenbus_xs.c Thu Jul 26 09:24:08 2007 -0400
@@ -717,8 +717,10 @@ static int xenwatch_thread(void *unused)
{
struct list_head *ent;
struct xs_stored_msg *msg;
-
+
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,6)
current->flags |= PF_NOFREEZE;
+#endif
for (;;) {
wait_event_interruptible(watch_events_waitq,
!list_empty(&watch_events));
@@ -837,7 +839,9 @@ static int xenbus_thread(void *unused)
{
int err;
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,6)
current->flags |= PF_NOFREEZE;
+#endif
for (;;) {
err = process_msg();
if (err)
[-- 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:[~2007-07-26 15:14 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=46A8BA64.7020609@virtualiron.com \
--to=bguthro@virtualiron.com \
--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.