From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: wei.liu2@citrix.com, 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,
Chao Peng <chao.p.peng@linux.intel.com>,
dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v5 12/13] tools: add tools support for Intel CAT
Date: Tue, 21 Apr 2015 16:39:05 +0200 [thread overview]
Message-ID: <1429627145.18926.107.camel@citrix.com> (raw)
In-Reply-To: <1429624874.4743.101.camel@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]
On Tue, 2015-04-21 at 15:01 +0100, Ian Campbell wrote:
> On Tue, 2015-04-21 at 17:49 +0800, Chao Peng wrote:
> > I do like this suggestion and I have ever considered it actually. The
> > only thing prevents me is that we need an extra _get_socket_count in xl
> > for TARGET_ALL case. So libxl__count_physical_sockets is needed to be
> > public. If Ian/Wei have no concerns for this, then I'm glad to do this.
>
> I don't think you need libxl__count_physical_sockets for this,
>
I also don't think that is necessary.
> the
> existing xl code for similar things just uses libxl_bitmap_set_any to
> handle the all case.
>
That or, if you want to do something similar to what we have in *libxl*
now you can look at the implementation of libxl_cpu_bitmap_alloc() (or
libxl_node_bitmap_alloc() ) and define yours
libxl_socket_bitmap_alloc().
In there, libxl_get_max_cpus() ( *_nodes()) is used, internally, to
determine the size of the bitmap, if the user did not provide it
explicitly. In your case, you can use libxl__count_physical_sockets() to
the same effect, without the need for it to be public.
But then again, that is probably even not necessary.
Regards,
Dario
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-04-21 14:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 14:33 [PATCH v5 00/13] enable Cache Allocation Technology (CAT) for VMs Chao Peng
2015-04-17 14:33 ` [PATCH v5 01/13] x86: add socket_to_cpumask Chao Peng
2015-04-17 14:33 ` [PATCH v5 02/13] x86: improve psr scheduling code Chao Peng
2015-04-20 15:42 ` Dario Faggioli
2015-04-17 14:33 ` [PATCH v5 03/13] x86: detect and initialize Intel CAT feature Chao Peng
2015-04-20 16:13 ` Dario Faggioli
2015-04-21 9:39 ` Chao Peng
2015-04-17 14:33 ` [PATCH v5 04/13] x86: maintain COS to CBM mapping for each socket Chao Peng
2015-04-17 14:33 ` [PATCH v5 05/13] x86: add COS information for each domain Chao Peng
2015-04-20 15:50 ` Andrew Cooper
2015-04-17 14:33 ` [PATCH v5 06/13] x86: expose CBM length and COS number information Chao Peng
2015-04-17 14:33 ` [PATCH v5 07/13] x86: dynamically get/set CBM for a domain Chao Peng
2015-04-20 15:52 ` Andrew Cooper
2015-04-21 9:42 ` Chao Peng
2015-04-17 14:33 ` [PATCH v5 08/13] x86: add scheduling support for Intel CAT Chao Peng
2015-04-17 14:33 ` [PATCH v5 09/13] xsm: add CAT related xsm policies Chao Peng
2015-04-17 14:33 ` [PATCH v5 10/13] tools/libxl: minor name changes for CMT commands Chao Peng
2015-04-20 16:07 ` Dario Faggioli
2015-04-21 13:56 ` Ian Campbell
2015-04-17 14:33 ` [PATCH v5 11/13] tools/libxl: add command to show CMT hardware info Chao Peng
2015-04-21 0:37 ` Dario Faggioli
2015-04-21 9:42 ` Chao Peng
2015-04-21 13:57 ` Ian Campbell
2015-04-17 14:33 ` [PATCH v5 12/13] tools: add tools support for Intel CAT Chao Peng
2015-04-21 1:24 ` Dario Faggioli
2015-04-21 9:49 ` Chao Peng
2015-04-21 14:01 ` Ian Campbell
2015-04-21 14:39 ` Dario Faggioli [this message]
2015-04-22 13:09 ` Chao Peng
2015-04-21 15:15 ` Dario Faggioli
2015-04-22 13:37 ` Chao Peng
2015-04-17 14:33 ` [PATCH v5 13/13] docs: add xl-psr.markdown Chao Peng
2015-04-21 14:05 ` 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=1429627145.18926.107.camel@citrix.com \
--to=dario.faggioli@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=ian.campbell@citrix.com \
--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.