From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chao Peng <chao.p.peng@linux.intel.com>
Subject: Re: [PATCH v8 03/13] x86: maintain COS to CBM mapping
 for each socket
Date: Mon, 1 Jun 2015 16:56:21 +0800
Message-ID: <20150601085621.GB3773@pengc-linux.bj.intel.com>
References: <1432197704-20816-1-git-send-email-chao.p.peng@linux.intel.com>
	<1432197704-20816-4-git-send-email-chao.p.peng@linux.intel.com>
	<556731A2020000780007E99B@mail.emea.novell.com>
	<20150529024259.GC18422@pengc-linux.bj.intel.com>
	<55683A36020000780007ED4D@mail.emea.novell.com>
	<20150529083831.GF18422@pengc-linux.bj.intel.com>
	<20150601080507.GA3773@pengc-linux.bj.intel.com>
	<556C359F020000780007F8DF@mail.emea.novell.com>
Reply-To: Chao Peng <chao.p.peng@linux.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <556C359F020000780007F8DF@mail.emea.novell.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Jan Beulich <JBeulich@suse.com>
Cc: wei.liu2@citrix.com, Ian.Campbell@citrix.com, stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com, dario.faggioli@citrix.com, Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org, will.auld@intel.com, keir@xen.org, dgdegra@tycho.nsa.gov
List-Id: xen-devel@lists.xenproject.org

On Mon, Jun 01, 2015 at 09:36:15AM +0100, Jan Beulich wrote:
> >>> On 01.06.15 at 10:05, <chao.p.peng@linux.intel.com> wrote:
> > 2)  Unfeasible to allocate memory first and do initialization later in
> > cpu hotplug notifications. My former approach is performing both the
> > allocation and initialization in the CPU_STARTING, which is not a good
> > idea indicated by Jan.
> 
> Considering
> 
>          info->cos_max = min(opt_cos_max, edx & 0xffff);
> 
> I don't see why you couldn't do an allocation using opt_cos_max
> in CPU_UP_PREPARE, potentially not using all of the slots later
> on.

If memory waste is not a problem (especially in most cases opt_cos_max is
its default 255), then this would be a solution.

As you have suggested this, then I think I can go on this path and still
have asymmetry systems been supported.

Thanks,
Chao