From: "Jan Beulich" <JBeulich@suse.com>
To: Chong Li <lichong659@gmail.com>
Cc: Chong Li <chong.li@wustl.edu>,
george.dunlap@eu.citrix.com, dario.faggioli@citrix.com,
xen-devel@lists.xen.org, mengxu@cis.upenn.edu,
dgolomb@seas.upenn.edu
Subject: Re: [PATCH] xen: enable per-VCPU parameter for RTDS
Date: Tue, 05 Apr 2016 01:57:51 -0600 [thread overview]
Message-ID: <57038C1F02000078000E30A9@prv-mh.provo.novell.com> (raw)
In-Reply-To: <1459818433-2498-1-git-send-email-lichong659@gmail.com>
>>> On 05.04.16 at 03:07, <lichong659@gmail.com> wrote:
> Commit f7b87b0745b4 ("enable per-VCPU parameter for RTDS") introduced
> a bug: it made it possible, in Credit and Credit2, when doing domain
> or vcpu parameters' manipulation, to leave the hypervisor with a
> spinlock held and interrupts disabled.
>
> Fix it.
>
> Signed-off-by: Chong Li <chong.li@wustl.edu>
>
> Acked-by: Dario Faggioli <dario.faggioli@citrix.com>
This appears to be the 3rd variant of the patch, all with the same
bogus subject, and no versioning information at all. Please
remember that mails can arrive out of order, so there's no way
to reliably tell which one got sent first. So for this to go in I'm
expecting you to re-send with a proper subject and an indication
that this is not the initial version of the patch.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-05 7:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 1:07 [PATCH] xen: enable per-VCPU parameter for RTDS Chong Li
2016-04-05 1:44 ` Meng Xu
2016-04-05 7:57 ` Jan Beulich [this message]
2016-04-05 9:25 ` George Dunlap
2016-04-05 9:43 ` Dario Faggioli
2016-04-05 12:45 ` Wei Liu
-- strict thread matches above, loose matches on Subject: below --
2016-04-04 22:45 Chong Li
2016-04-04 23:14 ` Andrew Cooper
2016-04-05 9:18 ` George Dunlap
2016-04-05 9:39 ` Dario Faggioli
2016-04-04 21:21 Chong Li
2016-04-04 22:05 ` Dario Faggioli
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=57038C1F02000078000E30A9@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=chong.li@wustl.edu \
--cc=dario.faggioli@citrix.com \
--cc=dgolomb@seas.upenn.edu \
--cc=george.dunlap@eu.citrix.com \
--cc=lichong659@gmail.com \
--cc=mengxu@cis.upenn.edu \
--cc=xen-devel@lists.xen.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).