xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel@lists.xen.org
Cc: Dario.Faggioli@citrix.com, Ian.Jackson@citrix.com,
	Juergen Gross <juergen.gross@ts.fujitsu.com>,
	George.Dunlap@citrix.com
Subject: [PATCH 0 of 3] libxl: make it possible to explicitly specify default sched params
Date: Wed, 23 May 2012 10:26:47 +0100	[thread overview]
Message-ID: <patchbomb.1337765207@cosworth.uk.xensource.com> (raw)

This series defines a descriminating value for each scheduler paramter
and uses it to fix a warning when starting a guest:
  "Cpu weight out of range, valid values are within range from 1 to 65535"

It also cleans up a few things and adds some convience interfaces for
cpupools.

I'm slightly reticent about this change during the freeze, but since
it fixes a warning which needs to be fixed for release and makes
(useful, I think) changes to the libxl API I think it is ok.

             reply	other threads:[~2012-05-23  9:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23  9:26 Ian Campbell [this message]
2012-05-23  9:26 ` [PATCH 1 of 3] libxl: add internal function to get a domain's scheduler Ian Campbell
2012-05-23 19:47   ` George Dunlap
2012-05-24  8:55     ` Ian Campbell
2012-05-24  9:16       ` Dario Faggioli
2012-05-23  9:26 ` [PATCH 2 of 3] libxl: rename libxl_sched_params to libxl_sched_domain_params Ian Campbell
2012-05-23 19:49   ` George Dunlap
2012-05-23  9:26 ` [PATCH 3 of 3] libxl: make it possible to explicitly specify default sched params Ian Campbell
2012-05-23 10:51   ` Ian Jackson
2012-05-23 11:12   ` Dario Faggioli
2012-05-24  8:52     ` Ian Campbell
2012-05-24  9:15       ` Dario Faggioli
2012-05-23 19:28   ` George Dunlap
2012-05-23 19:34     ` George Dunlap
2012-05-23 21:19     ` Dario Faggioli
2012-05-24  9:13       ` Ian Campbell
2012-05-24  9:36         ` Dario Faggioli
2012-05-24 13:57     ` Ian Jackson
2012-05-24 14:02       ` 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.1337765207@cosworth.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=Dario.Faggioli@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Ian.Jackson@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).