From: Keir Fraser <keir.xen@gmail.com>
To: John Weekes <lists.xen@nuclearfallout.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
George Dunlap <george.dunlap@citrix.com>
Subject: Re: [PATCH] Fix locking bug in vcpu_migrate
Date: Sat, 23 Apr 2011 08:01:22 +0100 [thread overview]
Message-ID: <C9D837D2.16CA4%keir.xen@gmail.com> (raw)
In-Reply-To: <4DB20236.4020604@nuclearfallout.net>
On 22/04/2011 23:33, "John Weekes" <lists.xen@nuclearfallout.net> wrote:
> I would be happy to temporarily turn over the reins on this machine to
> you or George, if you'd like to debug any of these issues directly. I
> may not be able to continue experimenting in the short term here myself
> due to time constraints.
Given that these are all apparently credit2 (non-default) scheduler issues,
I'll leave it to George.
-- Keir
prev parent reply other threads:[~2011-04-23 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 10:00 [PATCH] Fix locking bug in vcpu_migrate John Weekes
2011-04-22 10:30 ` Keir Fraser
2011-04-22 18:23 ` John Weekes
2011-04-22 18:43 ` Keir Fraser
2011-04-22 22:33 ` John Weekes
2011-04-23 7:01 ` Keir Fraser [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=C9D837D2.16CA4%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=lists.xen@nuclearfallout.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).