From: Ian Campbell <ian.campbell@citrix.com>
To: Tianyang Chen <tiche@seas.upenn.edu>, xen-devel@lists.xenproject.org
Cc: dario.faggioli@citrix.com, ian.jackson@eu.citrix.com,
george.dunlap@citrix.com, Meng Xu <mengxu@cis.upenn.edu>,
jbeulich@suse.com, Dagaen Golomb <dgolomb@seas.upenn.edu>
Subject: Re: [PATCH 1/1] Improved RTDS scheduler
Date: Mon, 4 Jan 2016 11:42:03 +0000 [thread overview]
Message-ID: <1451907723.13361.39.camel@citrix.com> (raw)
In-Reply-To: <1451555121-8085-2-git-send-email-tiche@seas.upenn.edu>
On Thu, 2015-12-31 at 04:45 -0500, Tianyang Chen wrote:
> Budget replenishment is now handled by a dedicated timer which is
> triggered at the most imminent release time of all runnable vcpus.
>
> Signed-off-by: Tianyang Chen <tiche@seas.upenn.edu>
> Signed-off-by: Meng Xu <mengxu@cis.upenn.edu>
> Signed-off-by: Dagaen Golomb <dgolomb@seas.upenn.edu>
> ---
> 0000-cover-letter.patch | 16 +++
> 0001-Improved-RTDS-scheduler.patch | 280 ++++++++++++++++++++++++++++++++++++
> bak | 62 ++++++++
I assume you didn't actually intend to commit those ;-)
(In general single patches do not require a separate cover letter unless
the required context contains a large amount of information which is not
appropriate for the commit message of the actual change, I'll leave it to
you and the scheduler maintainers to decide how much of your cover letter
it would be appropriate to move to the commit message).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-04 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 9:45 [PATCH 0/1] Improved RTDS scheduler Tianyang Chen
2015-12-31 9:45 ` [PATCH 1/1] " Tianyang Chen
2016-01-04 11:42 ` Ian Campbell [this message]
2016-01-04 13:48 ` Meng Xu
2016-01-04 14:04 ` Ian Campbell
2016-01-04 14:36 ` Dario Faggioli
2016-01-06 7:11 ` Tianyang Chen
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=1451907723.13361.39.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=dgolomb@seas.upenn.edu \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=mengxu@cis.upenn.edu \
--cc=tiche@seas.upenn.edu \
--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).