On Mon, 17 Sep 2007 16:28:31 +1000 Stephen Rothwell <[email protected]> wrote: > > the topology (on my POWERPC5+ box) is not correct: > > cpu0/topology/thread_siblings:0000000f > cpu1/topology/thread_siblings:0000000f > cpu2/topology/thread_siblings:0000000f > cpu3/topology/thread_siblings:0000000f > > it used to be: > > cpu0/topology/thread_siblings:00000003 > cpu1/topology/thread_siblings:00000003 > cpu2/topology/thread_siblings:0000000c > cpu3/topology/thread_siblings:0000000c This would be because we are setting up the cpu_sibling map before we call setup_per_cpu_areas(). -- Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Attachment:
pgpckgIXB1qsS.pgp
Description: PGP signature
- References:
- [PATCH 00/10] x86: Reduce Memory Usage and Inter-Node message traffic (v3)
- From: [email protected]
- [PATCH 09/10] ppc64: Convert cpu_sibling_map to a per_cpu data array (v3)
- From: [email protected]
- Re: [PATCH 09/10] ppc64: Convert cpu_sibling_map to a per_cpu data array (v3)
- From: Stephen Rothwell <[email protected]>
- [PATCH 00/10] x86: Reduce Memory Usage and Inter-Node message traffic (v3)
- Prev by Date: Re: [PATCH 09/10] ppc64: Convert cpu_sibling_map to a per_cpu data array (v3)
- Next by Date: Re: [PATCH] Wake up mandatory locks waiter on chmod
- Previous by thread: Re: [PATCH 09/10] ppc64: Convert cpu_sibling_map to a per_cpu data array (v3)
- Next by thread: Re: [PATCH 09/10] ppc64: Convert cpu_sibling_map to a per_cpu data array (v3)
- Index(es):
 |