From: Chao Peng <chao.p.peng@linux.intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: wei.liu2@citrix.com, Ian.Campbell@citrix.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org,
will.auld@intel.com, keir@xen.org, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v2 4/7] x86: add support for COS/CBM manangement
Date: Mon, 23 Mar 2015 16:47:45 +0800 [thread overview]
Message-ID: <20150323084745.GK5371@pengc-linux.bj.intel.com> (raw)
In-Reply-To: <550C6358020000780006C338@mail.emea.novell.com>
On Fri, Mar 20, 2015 at 05:13:44PM +0000, Jan Beulich wrote:
> >>> On 19.03.15 at 11:41, <chao.p.peng@linux.intel.com> wrote:
> > +static unsigned int get_socket_cpu(unsigned int socket)
> > +{
> > + unsigned int cpu;
> > +
> > + for_each_online_cpu ( cpu )
> > + if ( cpu_to_socket(cpu) == socket )
> > + return cpu;
> > + return nr_cpu_ids;
> > +}
>
> This can be a rather long loop for a huge system. I think you need to
> find some better solution for this.
Maintain a socket_cpu_map for each socket? Sounds no existed way.
> > +struct xen_domctl_psr_cat_op {
> > +#define XEN_DOMCTL_PSR_CAT_OP_SET_L3_CBM 0
> > +#define XEN_DOMCTL_PSR_CAT_OP_GET_L3_CBM 1
> > + uint32_t cmd; /* IN: XEN_DOMCTL_PSR_CAT_OP_* */
> > + uint32_t target; /* IN: socket or cpu to be operated on */
>
> How can this be socket _or_ CPU?
This is for future feature like L2 cache which needs to specify cpu but
not socket. Perhaps not mention here to avoid confusing.
Chao
next prev parent reply other threads:[~2015-03-23 8:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 10:41 [PATCH v2 0/7] enable Cache Allocation Technology (CAT) for VMs Chao Peng
2015-03-19 10:41 ` [PATCH v2 1/7] x86: clean up psr boot parameter parsing Chao Peng
2015-03-20 16:47 ` Jan Beulich
2015-03-23 8:32 ` Chao Peng
2015-03-23 8:47 ` Jan Beulich
2015-03-19 10:41 ` [PATCH v2 2/7] x86: improve psr scheduling code Chao Peng
2015-03-19 10:41 ` [PATCH v2 3/7] x86: detect and initialize Intel CAT feature Chao Peng
2015-03-19 11:38 ` Tim Deegan
2015-03-19 12:44 ` Dario Faggioli
2015-03-19 13:35 ` Jan Beulich
2015-03-20 10:24 ` Dario Faggioli
2015-03-23 8:36 ` Chao Peng
2015-03-20 17:00 ` Jan Beulich
2015-03-19 10:41 ` [PATCH v2 4/7] x86: add support for COS/CBM manangement Chao Peng
2015-03-20 17:13 ` Jan Beulich
2015-03-23 8:47 ` Chao Peng [this message]
2015-03-23 9:03 ` Jan Beulich
2015-03-19 10:41 ` [PATCH v2 5/7] x86: add scheduling support for Intel CAT Chao Peng
2015-03-19 10:41 ` [PATCH v2 6/7] xsm: add CAT related xsm policies Chao Peng
2015-03-19 10:41 ` [PATCH v2 7/7] tools: add tools support for Intel CAT Chao Peng
2015-03-19 12:51 ` Ian Campbell
2015-03-24 11:20 ` Chao Peng
2015-03-24 12:22 ` 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=20150323084745.GK5371@pengc-linux.bj.intel.com \
--to=chao.p.peng@linux.intel.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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.