From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: [PATCH] Re: xenstore notifier: atomic or blocking?
Date: Fri, 26 Oct 2007 16:47:02 +0100 [thread overview]
Message-ID: <47222816.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C33CDE2A.170AB%Keir.Fraser@cl.cam.ac.uk>
There doesn't appear to be any need for it to be atomic.
As usual, written and tested against 2.6.23 and made apply against
2.6.18 without further testing.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: head-2007-10-23/drivers/xen/xenbus/xenbus_probe.c
===================================================================
--- head-2007-10-23.orig/drivers/xen/xenbus/xenbus_probe.c 2007-10-25 15:08:03.000000000 +0200
+++ head-2007-10-23/drivers/xen/xenbus/xenbus_probe.c 2007-10-25 15:08:43.000000000 +0200
@@ -69,7 +69,7 @@ static unsigned long xen_store_mfn;
extern struct mutex xenwatch_mutex;
-static ATOMIC_NOTIFIER_HEAD(xenstore_chain);
+static BLOCKING_NOTIFIER_HEAD(xenstore_chain);
static void wait_for_devices(struct xenbus_driver *xendrv);
@@ -832,7 +832,7 @@ int register_xenstore_notifier(struct no
if (xenstored_ready > 0)
ret = nb->notifier_call(nb, 0, NULL);
else
- atomic_notifier_chain_register(&xenstore_chain, nb);
+ blocking_notifier_chain_register(&xenstore_chain, nb);
return ret;
}
@@ -840,7 +840,7 @@ EXPORT_SYMBOL_GPL(register_xenstore_noti
void unregister_xenstore_notifier(struct notifier_block *nb)
{
- atomic_notifier_chain_unregister(&xenstore_chain, nb);
+ blocking_notifier_chain_unregister(&xenstore_chain, nb);
}
EXPORT_SYMBOL_GPL(unregister_xenstore_notifier);
@@ -855,7 +855,7 @@ void xenbus_probe(struct work_struct *un
xenbus_backend_probe_and_watch();
/* Notify others that xenstore is up */
- atomic_notifier_call_chain(&xenstore_chain, 0, NULL);
+ blocking_notifier_call_chain(&xenstore_chain, 0, NULL);
}
prev parent reply other threads:[~2007-10-26 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:51 xenstore notifier: atomic or blocking? Jan Beulich
2007-10-18 8:55 ` Keir Fraser
2007-10-26 15:47 ` Jan Beulich [this message]
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=47222816.76E4.0078.0@novell.com \
--to=jbeulich@novell.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.