Hi Brice,
I have discussed the issue internally and we can confirm that CPU topology for
POWER7 as reported by 2.6.32 kernel (in RHEL6.0) is indeed wrong.
I have submitted BZ against RHEL6.0
https://bugzilla.redhat.com/show_bug.cgi?id=621546
to get it fixed. Let's see if the fix can be back-por
Power7 topology isn't properly reported by old kernels. We've been said
that it works fine with 2.6.34. I am not sure which commit fixed this. I
don't see many commits talk about Power7 topology between 2.6.32 and
2.6.34, so it may be this one (from 2.6.34):
commit 4b83c330b4d38e869111bda6e9077d4f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/08/10 08:27, Jirka Hladky wrote:
> which seems to be wrong.
I hope so!
I've sent a query to some of the IBM'ers I know in case
they can shed some light.
On our Power6 box with SLES10 those topology directories
are empty.. :-(
# ls /sys/d
I have just found that
cat /sys/devices/system/cpu/cpu*/topology/physical_package_id
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
-1
which seems to be wrong.
Jirka
On Thursday, August 05, 2010 12:19:41 am Jirka Hladky wrote:
> Hi,
>
> I just
Hi,
I just got access to one POWER7 box. Both hwloc 1.0.2 and latest hwloc 1.1
seem to have problems to detect the sockets correctly.
It's IBM 8406-71Y server equipped with only one socket. On the chip there are
8 cores. lstopo seems to be wrong here, reporting 8 sockets.
I'm not sure if this