All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [xen-unstable test] 2521: all pass
Date: Wed, 3 Nov 2010 18:17:22 +0100	[thread overview]
Message-ID: <20101103171722.GA31149@aepfle.de> (raw)
In-Reply-To: <19665.38016.762514.487518@mariner.uk.xensource.com>

On Wed, Nov 03, Ian Jackson wrote:

> Olaf Hering writes ("Re: [Xen-devel] [xen-unstable test] 2521: all pass"):
> > I just checked my quilt queue and wonder why I still need this patch to
> > get around the assert in the python code?
> > http://lists.xensource.com/archives/html/xen-devel/2010-08/msg01461.html
> 
> I don't know.
> 
> > A fix for this is here:
> > http://lists.xensource.com/archives/html/xen-devel/2010-08/msg01813.html
> 
> That's in xen-unstable, too.

Are you sure?
My copy looks like this, and the patch still applies.

686         # Convert scheduling parameters to vcpus_params
687         if 'vcpus_params' not in cfg:
688             cfg['vcpus_params'] = {}
689         if not cfg["vcpus_params"].has_key("weight"):
690             cfg["vcpus_params"]["weight"] = \
691                 int(sxp.child_value(sxp_cfg, "cpu_weight", 256))
692         if not cfg["vcpus_params"].has_key("cap"):
693             cfg["vcpus_params"]["cap"] = \
694                 int(sxp.child_value(sxp_cfg, "cpu_cap", 0))

Olaf

  reply	other threads:[~2010-11-03 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03  6:39 [xen-unstable test] 2521: all pass xen.org
2010-11-03 14:29 ` Olaf Hering
2010-11-03 16:57   ` Ian Jackson
2010-11-03 17:17     ` Olaf Hering [this message]
2010-11-03 17:24       ` Ian Jackson

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=20101103171722.GA31149@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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.