From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH v2 0/2] scheduler locking adjustments
Date: Fri, 11 Oct 2013 17:14:23 +0100 [thread overview]
Message-ID: <525823DF.5090907@citrix.com> (raw)
In-Reply-To: <525831D302000078000FAA1A@nat28.tlf.novell.com>
On 11/10/13 16:13, Jan Beulich wrote:
> 1: scheduler: adjust internal locking interface
> 2: sched: fix race between sched_move_domain() and vcpu_wake()
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
Both Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
It might be kind to leave some grep/cscope/ctags-fodder around for the
macro-constructed functions in the same way as mfn_t/gfn_t with
TYPE_SAFE but the names of the functions are certainly less obscure than
the TYPE_SAFE ones.
~Andrew
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-10-11 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 14:14 [PATCH] scheduler: adjust internal locking interface Jan Beulich
2013-10-11 14:29 ` Andrew Cooper
2013-10-11 14:37 ` Jan Beulich
2013-10-11 14:41 ` George Dunlap
2013-10-11 15:03 ` Jan Beulich
2013-10-11 15:13 ` [PATCH v2 0/2] scheduler locking adjustments Jan Beulich
2013-10-11 15:16 ` [PATCH v2 1/2] scheduler: adjust internal locking interface Jan Beulich
2013-10-11 15:17 ` [PATCH v2 2/2] sched: fix race between sched_move_domain() and vcpu_wake() Jan Beulich
2013-10-11 16:14 ` Andrew Cooper [this message]
2013-10-11 17:17 ` [PATCH v2 0/2] scheduler locking adjustments Keir Fraser
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=525823DF.5090907@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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).