All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] xl: fix broken cpupool-numa-split (part 2)
Date: Mon, 31 Jan 2011 07:56:27 +0100	[thread overview]
Message-ID: <4D465D1B.1010504@ts.fujitsu.com> (raw)
In-Reply-To: <4D4360EA.1090807@amd.com>

On 01/29/11 01:35, Andre Przywara wrote:
> On 01/28/2011 07:26 AM, Juergen Gross wrote:
>> On 01/27/11 22:36, Andre Przywara wrote:
>>> Hi,
>>>
>>> the implementation of xl cpupool-numa-split is broken. It basically
>>> deals with only one poolid, but there are two to consider: the one from
>>> the original root CPUpool, the other from the newly created one.
>>
>> Uhh, silly copy and paste error! I think it happened when I introduced
>> libxl_cpupool_cpuadd_node()...
>> The correction is much easier. The root poolid is always 0.
> Why do you save this value then?
> poolid = poolinfo[0].poolid;
> Reading this made me think it can be an arbitrary value.

Sorry, must be a relict...

>
>> See attached patch.
> Easier, but that only solves one part of the problem (not populating the
> newly created pool). The second bug still persists, because poolid is
> not zeroed out again after the first creation. So the second iteration
> will try to reuse the just assigned value and abort with an error.
>
> Ian, please apply the attached patch on top of Jürgens one.
>
> ----------
> Before the creation and population of a new CPU pool we have to clear
> the poolid variable, which still contains the value from the previous
> iteration.
> This fixes the execution of xl cpupool-numa-split on machines with more
> than two nodes.
>
> Signed-off-by: Andre Przywara <andre.przywara@amd.com>

Acked-by: juergen.gross@ts.fujitsu.com

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2011-01-31  6:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-27 21:36 [PATCH]: xl: fix broken cpupool-numa-split Andre Przywara
2011-01-28  6:26 ` Juergen Gross
2011-01-28 10:53   ` George Dunlap
2011-01-28 11:01     ` Juergen Gross
2011-01-28 17:41     ` Ian Jackson
2011-01-29  0:35   ` [PATCH] xl: fix broken cpupool-numa-split (part 2) Andre Przywara
2011-01-31  6:56     ` Juergen Gross [this message]
2011-02-01 19:07       ` 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=4D465D1B.1010504@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andre.przywara@amd.com \
    --cc=george.dunlap@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.