From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Chao Peng <chao.p.peng@linux.intel.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xen.org, keir@xen.org, andrew.cooper3@citrix.com
Subject: Re: [PATCH] x86: correct socket_cpumask allocation for AP
Date: Wed, 8 Jul 2015 18:17:36 +0200 [thread overview]
Message-ID: <1436372256.22672.246.camel@citrix.com> (raw)
In-Reply-To: <559D602C020000780008E585@mail.emea.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2107 bytes --]
On Wed, 2015-07-08 at 16:38 +0100, Jan Beulich wrote:
> >>> On 08.07.15 at 17:11, <dario.faggioli@citrix.com> wrote:
> > On Wed, 2015-07-08 at 13:38 +0100, Jan Beulich wrote:
> >> >>> On 08.07.15 at 11:36, <chao.p.peng@linux.intel.com> wrote:
> >> > @@ -84,11 +85,21 @@ void *stack_base[NR_CPUS];
> >> > static void smp_store_cpu_info(int id)
> >> > {
> >> > struct cpuinfo_x86 *c = cpu_data + id;
> >> > + unsigned int socket;
> >> >
> >> > *c = boot_cpu_data;
> >> > if ( id != 0 )
> >> > + {
> >> > identify_cpu(c);
> >> >
> >> > + socket = cpu_to_socket(id);
> >> > + if ( !socket_cpumask[socket] )
> >> > + {
> >> > + socket_cpumask[socket] = secondary_socket_cpumask;
> >> > + secondary_socket_cpumask = NULL;
> >>
> >> I don't think this will build with small enough NR_CPUS.
> >>
> > And it *does* *not* fix the issue on my box.
>
> I.e. bad analysis (albeit it seemed correct to me)
>
Same here, and in fact I triple checked that I had the patch really
applied... and, yes, it is, and it's still crashing, with the same
(reported) dump as the one we find in Osstest's failure, as reported by
Ian.
> _and_ new code not tested.
>
Looking another time, both me and Osstest are probably seeing a
different issue, than the one Boris is facing. I don't see Boris' Oops,
so I can't be sure, but in my case, this is happening in
set_cpu_sibling_map(), called from smp_prepare_cpus() on the boot CPU,
not during secondary CPUs bringup.
I think it has to do with the fact that I've got CPU #0 on socket #1,
while Boris' (and perhaps Chao's too) test box have it on socket #0.
I'd be happy to test patches on my box, if that helps (although, I'm
about to leave right now, so that will be tomorrow).
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- 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-07-08 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 9:36 [PATCH] x86: correct socket_cpumask allocation for AP Chao Peng
2015-07-08 12:38 ` Jan Beulich
2015-07-08 15:11 ` Dario Faggioli
2015-07-08 15:38 ` Jan Beulich
2015-07-08 15:45 ` Boris Ostrovsky
2015-07-08 16:17 ` Dario Faggioli [this message]
2015-07-08 16:32 ` Jan Beulich
2015-07-09 1:58 ` Chao Peng
2015-07-09 8:39 ` Dario Faggioli
2015-07-08 18:24 ` Boris Ostrovsky
2015-07-09 1:47 ` 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=1436372256.22672.246.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chao.p.peng@linux.intel.com \
--cc=keir@xen.org \
--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.