From: Anthony Liguori <aliguori@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: [Xen-changelog] Disable xcs stop from xend script since it kills xenstored now.
Date: Tue, 06 Sep 2005 14:22:47 -0500 [thread overview]
Message-ID: <431DEC87.2070006@us.ibm.com> (raw)
In-Reply-To: <E1ECh5G-0003Yd-NB@xenbits.xensource.com>
Hey Christian,
I see you've made xenstored connect to xcs so that it can receive VIRQ
notifications. Can you describe briefly how you envision this all
ending up working?
I really dislike using VIRQs to get shutdown notification. Plus, I
think the current state of things is much more brittle.
Is all of this really worth avoiding polling? The previous consoled
code that used polling worked just fine. If we would have stuck with
it, there would be no xcs dependencies anymore except for netif.
Regards,
Anthony Liguori
Xen patchbot -unstable wrote:
># HG changeset patch
># User cl349@firebug.cl.cam.ac.uk
># Node ID 6d7b05e1c1e5038d34cab546bb3d50f12127c6e1
># Parent d4d69c509371fc2019156cb1bf76a62c89d44bb6
>Disable xcs stop from xend script since it kills xenstored now.
>Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
>
>diff -r d4d69c509371 -r 6d7b05e1c1e5 tools/misc/xend
>--- a/tools/misc/xend Tue Sep 6 17:00:25 2005
>+++ b/tools/misc/xend Tue Sep 6 17:18:28 2005
>@@ -151,10 +151,8 @@
> start_consoled()
> return daemon.start(trace=1)
> elif sys.argv[1] == 'stop':
>- stop_xcs()
> return daemon.stop()
> elif sys.argv[1] == 'restart':
>- stop_xcs()
> start_xcs()
> start_xenstored()
> start_consoled()
>
>_______________________________________________
>Xen-changelog mailing list
>Xen-changelog@lists.xensource.com
>http://lists.xensource.com/xen-changelog
>
>
>
parent reply other threads:[~2005-09-06 19:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1ECh5G-0003Yd-NB@xenbits.xensource.com>]
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=431DEC87.2070006@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=rusty@rustcorp.com.au \
--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.