From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>,
Dario Faggioli <raistlin@linux.it>,
Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2 of 2 v3] xl: check for meaningful combination of sedf config file parameters
Date: Fri, 8 Jun 2012 12:11:24 +0100 [thread overview]
Message-ID: <4FD1DDDC.6020405@eu.citrix.com> (raw)
In-Reply-To: <20433.56754.133034.440704@mariner.uk.xensource.com>
On 08/06/12 12:10, Ian Jackson wrote:
> Dario Faggioli writes ("[PATCH 2 of 2 v3] xl: check for meaningful combination of sedf config file parameters"):
>> As it happens in the implementation of `xl sched-sedf -d ...', some
>> consistency checking is needed for the scheduling parameters when
>> they come from the config file.
> Thanks, I am happy with this from a libxl point of view. I would like
> to see an ack from George from a scheduler point of view.
I think Dario knows more about what sedf wants than I do; and since it
only does anything when the domain is using sedf, I think it's fine.
So FWIW:
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
next prev parent reply other threads:[~2012-06-08 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 9:08 [PATCH 0 of 2 v3] Sanity checking of scheduling parameters Dario Faggioli
2012-06-08 9:08 ` [PATCH 1 of 2 v3] libxl: propagete down the error from libxl_domain_sched_params_set Dario Faggioli
2012-06-08 11:10 ` Ian Jackson
2012-06-14 15:06 ` [PATCH 2 of 2 v3] xl: check for meaningful combination of sedf config file parameters [and 1 more messages] Ian Jackson
2012-06-14 15:13 ` Dario Faggioli
2012-06-08 9:08 ` [PATCH 2 of 2 v3] xl: check for meaningful combination of sedf config file parameters Dario Faggioli
2012-06-08 11:10 ` Ian Jackson
2012-06-08 11:11 ` George Dunlap [this message]
2012-06-08 14:26 ` Ian Jackson
2012-06-12 14:58 ` Ian Campbell
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=4FD1DDDC.6020405@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--cc=raistlin@linux.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.