From: George Dunlap <george.dunlap@eu.citrix.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] Add cap value to credit scheduler debug info
Date: Mon, 14 Oct 2013 10:47:20 +0100 [thread overview]
Message-ID: <525BBDA8.7070306@eu.citrix.com> (raw)
In-Reply-To: <1381728570-12242-3-git-send-email-juergen.gross@ts.fujitsu.com>
On 10/14/2013 06:29 AM, Juergen Gross wrote:
> Currently only the weight is the only scheduling parameter printed for
> domains in the credit scheduler key handler. Add the cap value to be
> printed as well.
>
> Signed-off-by: Juergen Gross <juergen.gross@ts.fujitsu.com>
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
prev parent reply other threads:[~2013-10-14 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 5:29 Cap related correction and enhancement of credit scheduler Juergen Gross
2013-10-14 5:29 ` [PATCH 1/2] unpause parked vcpu before destroying it Juergen Gross
2013-10-14 9:46 ` George Dunlap
2013-10-14 5:29 ` [PATCH 2/2] Add cap value to credit scheduler debug info Juergen Gross
2013-10-14 9:47 ` George Dunlap [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=525BBDA8.7070306@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--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).