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,
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
Subject: Re: [PATCH v8 01/13] x86: add socket_cpumask
Date: Tue, 2 Jun 2015 15:19:55 +0800 [thread overview]
Message-ID: <20150602071955.GD3773@pengc-linux.bj.intel.com> (raw)
In-Reply-To: <556D70130200007800080068@mail.emea.novell.com>
On Tue, Jun 02, 2015 at 07:57:55AM +0100, Jan Beulich wrote:
> >>> On 02.06.15 at 08:35, <chao.p.peng@linux.intel.com> wrote:
> > On Fri, May 29, 2015 at 09:52:03AM +0100, Jan Beulich wrote:
> >> >>> On 29.05.15 at 10:28, <chao.p.peng@linux.intel.com> wrote:
> >> > On Fri, May 29, 2015 at 09:01:53AM +0100, Jan Beulich wrote:
> >> >> >>> On 29.05.15 at 04:35, <chao.p.peng@linux.intel.com> wrote:
> >> >> > On Thu, May 28, 2015 at 01:38:05PM +0100, Jan Beulich wrote:
> >> >> >> >>> On 21.05.15 at 10:41, <chao.p.peng@linux.intel.com> wrote:
> >> >> >> > --- a/xen/arch/x86/mpparse.c
> >> >> >> > +++ b/xen/arch/x86/mpparse.c
> >> >> >> > @@ -87,6 +87,18 @@ void __init set_nr_cpu_ids(unsigned int max_cpus)
> >> >> >> > #endif
> >> >> >> > }
> >> >> >> >
> >> >> >> > +void __init set_nr_sockets(void)
> >> >> >> > +{
> >> >> >> > + unsigned int cpus = bitmap_weight(phys_cpu_present_map.mask,
> >> >> >> > + boot_cpu_data.x86_max_cores *
> >> >> >> > + boot_cpu_data.x86_num_siblings);
> >> >> >> > +
> >> >> >> > + if ( cpus == 0 )
> >> >> >> > + cpus = 1;
> >> >> >> > +
> >> >> >> > + nr_sockets = DIV_ROUND_UP(num_processors + disabled_cpus, cpus);
> >> >> >> > +}
> >> >> >>
> >> >> >> Is there a reason why this can't just be added to the end of the
> >> >> >> immediately preceding set_nr_cpu_ids()?
> >> >> >
> >> >> > You mean the declaration or invocation? If the former I have no special
> >> >> > reason for it (e.g. I can change it).
> >> >>
> >> >> Neither - I just don't see the need for a new function.
> >> >
> >> > In which case the invocation of set_nr_cpu_ids() should move to the
> >> > place where now set_nr_sockets() is invoked, to make sure
> >> > boot_cpu_data.x86_max_cores/x86_num_siblings available, which may not be
> >> > your expectation.
> >>
> >> Ah, in which case this _is_ the explanation, albeit only provided the
> >> use of the two boot_cpu_data fields has to remain (which I had put
> >> under question). And if these have to remain, couldn't this be done
> >> in a presmp initcall instead of an explicitly called function?
> >
> > presmp is too late. nr_sockets will get used in smp_prepare_cpus()
> > before calling set_cpu_sibling_map for cpu 0.
>
> Okay. In which case - why not calculate the value there?
Okay, then I just need move the invocation of set_nr_sockets() from
__start_xen() to smp_prepare_cpus().
Chao
next prev parent reply other threads:[~2015-06-02 7:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 8:41 [PATCH v8 00/13] enable Cache Allocation Technology (CAT) for VMs Chao Peng
2015-05-21 8:41 ` [PATCH v8 01/13] x86: add socket_cpumask Chao Peng
2015-05-28 12:38 ` Jan Beulich
2015-05-29 2:35 ` Chao Peng
2015-05-29 8:01 ` Jan Beulich
2015-05-29 8:28 ` Chao Peng
2015-05-29 8:52 ` Jan Beulich
2015-06-02 6:35 ` Chao Peng
2015-06-02 6:57 ` Jan Beulich
2015-06-02 7:19 ` Chao Peng [this message]
2015-05-21 8:41 ` [PATCH v8 02/13] x86: detect and initialize Intel CAT feature Chao Peng
2015-05-28 12:54 ` Jan Beulich
2015-05-29 2:40 ` Chao Peng
2015-05-29 8:03 ` Jan Beulich
2015-05-21 8:41 ` [PATCH v8 03/13] x86: maintain COS to CBM mapping for each socket Chao Peng
2015-05-28 13:17 ` Jan Beulich
2015-05-29 2:43 ` Chao Peng
2015-05-29 8:06 ` Jan Beulich
2015-05-29 8:38 ` Chao Peng
2015-06-01 8:05 ` Chao Peng
2015-06-01 8:36 ` Jan Beulich
2015-06-01 8:56 ` Chao Peng
2015-05-21 8:41 ` [PATCH v8 04/13] x86: add COS information for each domain Chao Peng
2015-05-21 8:41 ` [PATCH v8 05/13] x86: expose CBM length and COS number information Chao Peng
2015-05-28 13:26 ` Jan Beulich
2015-05-28 15:46 ` Dario Faggioli
2015-05-29 2:47 ` Chao Peng
2015-05-29 8:07 ` Jan Beulich
2015-05-29 9:23 ` Dario Faggioli
2015-05-29 9:29 ` Jan Beulich
2015-05-21 8:41 ` [PATCH v8 06/13] x86: dynamically get/set CBM for a domain Chao Peng
2015-05-21 8:41 ` [PATCH v8 07/13] x86: add scheduling support for Intel CAT Chao Peng
2015-05-21 8:41 ` [PATCH v8 08/13] xsm: add CAT related xsm policies Chao Peng
2015-05-21 8:41 ` [PATCH v8 09/13] tools/libxl: minor name changes for CMT commands Chao Peng
2015-05-21 8:41 ` [PATCH v8 10/13] tools/libxl: add command to show PSR hardware info Chao Peng
2015-05-21 8:41 ` [PATCH v8 11/13] tools/libxl: introduce some socket helpers Chao Peng
2015-05-21 8:41 ` [PATCH v8 12/13] tools: add tools support for Intel CAT Chao Peng
2015-05-21 8:41 ` [PATCH v8 13/13] docs: add xl-psr.markdown 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=20150602071955.GD3773@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=dario.faggioli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).