From: Jeremy Fitzhardinge <jeremy@goop.org>
To: pasik@iki.fi, konrad.wilk@oracle.com,
xen-devel@lists.xensource.com, andy@cs.ubc.ca
Subject: Re: [PATCH 0 of 3] Remus: control tool
Date: Tue, 01 Dec 2009 15:04:49 -0800 [thread overview]
Message-ID: <4B15A111.1050004@goop.org> (raw)
In-Reply-To: <20091201161619.GA2438@zanzibar.quuxuum.com>
On 12/01/09 08:16, Brendan Cully wrote:
> I'll probably take a crack at this soon. From a quick look at the
> pvops suspend code, it seems like it may suffer from a race when
> multiple suspends are issued that Keir fixed in the 2.6.18 tree some
> time ago -- it'd be better to get that fixed before porting the event
> channel patch.
>
What's the bug? I don't see a reentrancy issue there because the
suspend happens synchronously in the xenwatch thread under
xenwatch_mutex. Or race for that matter.
Am I missing something?
Of course, if you start triggering suspends via event channels, we'll
need to work out something else.
J
next prev parent reply other threads:[~2009-12-01 23:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 1:10 [PATCH 0 of 3] Remus: control tool Brendan Cully
2009-11-13 1:10 ` [PATCH 1 of 3] Remus: add python control extensions Brendan Cully
2009-11-13 1:10 ` [PATCH 2 of 3] Remus: add control script to activate remus on a VM Brendan Cully
2009-11-13 1:10 ` [PATCH 3 of 3] Remus: support for network buffering Brendan Cully
2009-11-13 14:18 ` [PATCH 0 of 3] Remus: control tool Konrad Rzeszutek Wilk
2009-11-13 21:36 ` Brendan Cully
2009-12-01 15:20 ` Pasi Kärkkäinen
2009-12-01 16:16 ` Brendan Cully
2009-12-01 23:04 ` Jeremy Fitzhardinge [this message]
2009-12-01 23:53 ` Brendan Cully
2009-12-02 8:07 ` Keir Fraser
2009-12-02 18:17 ` Jeremy Fitzhardinge
2009-12-02 18:20 ` Brendan Cully
2009-12-02 18:30 ` Jeremy Fitzhardinge
2009-12-02 18:25 ` Keir Fraser
2009-12-02 18:34 ` Jeremy Fitzhardinge
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=4B15A111.1050004@goop.org \
--to=jeremy@goop.org \
--cc=andy@cs.ubc.ca \
--cc=konrad.wilk@oracle.com \
--cc=pasik@iki.fi \
--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.