All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Guthro <bguthro@virtualiron.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 1/3] Do not use DEFINE_RWLOCK Macro
Date: Wed, 29 Aug 2007 14:20:05 -0400	[thread overview]
Message-ID: <46D5B8D5.8030605@virtualiron.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 171 bytes --]

Do not use the DEFINE_RWLOCK macro, as it is not available when compiled 
against
older kernels, such as SLES9's 2.6.5

Signed-off-by: Ben Guthro <bguthro@virtualron.com>

[-- Attachment #2: xen-legacy-reboot.patch --]
[-- Type: text/x-patch, Size: 733 bytes --]

diff -r ef25e071a074 unmodified_drivers/linux-2.6/platform-pci/machine_reboot.c
--- a/unmodified_drivers/linux-2.6/platform-pci/machine_reboot.c	Wed Aug 29 13:38:54 2007 -0400
+++ b/unmodified_drivers/linux-2.6/platform-pci/machine_reboot.c	Wed Aug 29 13:41:20 2007 -0400
@@ -15,8 +15,10 @@ struct ap_suspend_info {
 /*
  * Use a rwlock to protect the hypercall page from being executed in AP context
  * while the BSP is re-initializing it after restore.
+ * Do not use the DEFINE_RWLOCK macro, as it is not available when compiled against
+ *  older kernels
  */
-static DEFINE_RWLOCK(suspend_lock);
+static rwlock_t suspend_lock = RW_LOCK_UNLOCKED;
 
 /*
  * Spinning prevents, for example, APs touching grant table entries while

[-- 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-08-29 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 18:20 Ben Guthro [this message]
2007-08-29 18:37 ` [PATCH 1/3] Do not use DEFINE_RWLOCK Macro Ian Campbell
2007-08-29 20:31   ` Ben Guthro

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=46D5B8D5.8030605@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.