search

sudkannan / likwid

Automatically exported from code.google.com/p/likwid
GNU General Public License v3.0
0 stars 0 forks source link

socket to bus mapping is not always the same #124

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The Socket to bus mapping is not always correct.
/* Socket to bus mapping
 * Socket  Bus (2S)  Bus (4s)
 *   0        0xff      0x3f
 *   1        0x7f      0x7f
 *   2                  0xbf
 *   3                  0xff
 */

We have two 2-socket systems with different bus addresses.
2x Xeon E5-2690 bus address: 0x7f, 0xff
2x Xeon E5-2670 bus address: 0x3f, 0x7f 

lspci attached from both systems.

Original issue reported on code.google.com by xase...@googlemail.com on 5 Feb 2014 at 1:31

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi, please try the current release 3.1 . There the socket bus mapping is 
determined on the fly and not static as in the previous release. Reopen the 
ticket if you still face problems.

Original comment by jan.trei...@gmail.com on 8 Feb 2014 at 1:08