From: Ian Campbell <ian.campbell@citrix.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: keir@xen.org, stefano.stabellini@eu.citrix.com,
andrew.cooper3@citrix.com, Ian.Jackson@eu.citrix.com,
xen-devel@lists.xen.org, will.auld@intel.com, JBeulich@suse.com,
Wei Liu <wei.liu2@citrix.com>,
dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v3 7/8] tools/libxl: introduce libxl_count_physical_sockets
Date: Tue, 31 Mar 2015 17:11:48 +0100 [thread overview]
Message-ID: <1427818308.2115.179.camel@citrix.com> (raw)
In-Reply-To: <20150331085122.GB5816@pengc-linux.bj.intel.com>
On Tue, 2015-03-31 at 16:51 +0800, Chao Peng wrote:
> > I think Ian suggested you make this an internal function not a public
> > API. But if I misunderstand Ian's intention, please make this function
> > return libxl error code. The socket number can be returned from an out
> > parameter. I.e.
> >
> > int libxl_count_physical_sockets(libxl_ctx *ctx, uint32_t *nr_sockets);
> >
> Making it public is the need of supporting LIBXL_PSR_TARGET_ALL in
> libxl_psr_cat_set_cbm(), which is suggested by Ian as well. In such
> case, both xl/libxl need to get socket_count. Introduce it in libxl so
> that both can make use of it.
My expectation was that adding LIBXL_PSR_TARGET_ALL would remove the
need for xl to get the socket count, I expected that passing
LIBXL_PSR_TARGET_ALL would cause libxl to do all of that internally.
I've not looked at the next patch to see why that isn't the case though.
Ian.
>
> Except this, I would like to adopt your suggestions(#ifdef to x86 only
> and return error code).
>
> Chao
next prev parent reply other threads:[~2015-03-31 16:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 12:38 [PATCH v3 0/8] enable Cache Allocation Technology (CAT) for VMs Chao Peng
2015-03-26 12:38 ` [PATCH v3 1/8] x86: clean up psr boot parameter parsing Chao Peng
2015-03-26 20:42 ` Andrew Cooper
2015-03-26 12:38 ` [PATCH v3 2/8] x86: improve psr scheduling code Chao Peng
2015-03-27 18:15 ` Andrew Cooper
2015-03-26 12:38 ` [PATCH v3 3/8] x86: detect and initialize Intel CAT feature Chao Peng
2015-03-27 18:31 ` Andrew Cooper
2015-04-13 10:51 ` Jan Beulich
2015-04-13 10:58 ` Andrew Cooper
2015-03-26 12:38 ` [PATCH v3 4/8] x86: add support for COS/CBM manangement Chao Peng
2015-03-27 20:16 ` Andrew Cooper
2015-03-31 8:40 ` Chao Peng
2015-03-26 12:38 ` [PATCH v3 5/8] x86: add scheduling support for Intel CAT Chao Peng
2015-03-26 12:38 ` [PATCH v3 6/8] xsm: add CAT related xsm policies Chao Peng
2015-03-26 12:38 ` [PATCH v3 7/8] tools/libxl: introduce libxl_count_physical_sockets Chao Peng
2015-03-30 14:51 ` Wei Liu
2015-03-31 8:51 ` Chao Peng
2015-03-31 16:11 ` Ian Campbell [this message]
2015-03-26 12:38 ` [PATCH v3 8/8] tools: add tools support for Intel CAT Chao Peng
2015-03-31 16:28 ` Ian Campbell
2015-04-01 7:55 ` Chao Peng
2015-04-01 8:41 ` Ian Campbell
2015-04-01 9:06 ` Chao Peng
2015-04-01 9:23 ` Ian Campbell
2015-04-02 3:15 ` Chao Peng
2015-04-07 8:57 ` Chao Peng
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=1427818308.2115.179.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=will.auld@intel.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.