From: Dario Faggioli <raistlin@linux.it>
To: xen-devel@lists.xen.org
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Juergen Gross <juergen.gross@ts.fujitsu.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: [PATCH 0 of 2 v3] Sanity checking of scheduling parameters
Date: Fri, 08 Jun 2012 11:08:07 +0200 [thread overview]
Message-ID: <patchbomb.1339146487@Solace> (raw)
Hi,
This small series achieves two goals:
- check the return value of libxl_domain_sched_params_set() in
libxl__build_post() and deal with the error, if that is the
case (patch #1);
- check and ensue we are passing along a meaningful set of sedf
scheduling parameters when they come directly from the config file
(patch #2)
Tested on both credit and sedf schedulers.
Changes from v2:
* actually propagate the error correctly instead of always returning
INVAL (in patch #1).
Changes from v1:
* patch #1: it was not there at all in v1! :-P
* patch #2: the if-s have been moved into an helper function. Also,
they only happen if the domain is actually being scheduled with
sedf (IanC, yes, I decided to do it... At the end of the day, it is
simple enough I think).
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
next reply other threads:[~2012-06-08 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 9:08 Dario Faggioli [this message]
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
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=patchbomb.1339146487@Solace \
--to=raistlin@linux.it \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@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 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.