Am 02.10.2018 um 07:47 schrieb Brice Goglin:
Le 02/10/2018 à 00:28, Marco Atzeri a écrit :
Am 01.10.2018 um 19:57 schrieb Brice Goglin:
Le 01/10/2018 à 19:22, Marco Atzeri a écrit :

Your own machine doesn't matter. None is these tests look at your CPU or
topology. *All* of them on all x86 machines.
CPUID are emulated by reading files, nothing is read from your local
machine topology. There's just something wrong here that prevents these
emulating CPUID files from being read. "lstopo -i ..." will tell you.

$ /pub/devel/hwloc/hwloc-2.0.2-1.x86_64/build/utils/lstopo/lstopo-no-graphics.exe  -i /pub/devel/hwloc/hwloc-2.0.2-1.x86_64/src/hwloc-2.0.2/tests/hwloc/x86/AMD-15h-Bulldozer-4xOpteron-6272/  --if cpuid --of xml -
Ignoring dumped cpuid directory.

It works instead with "--if xml"

IMHO, should be better to produce an error
instead of the local machine output with a warning,
if the input is not understandable

The input is understandable here, but there's a cygwin-related bug somewhere when we actually try to use it.

--if xml makes no sense here since you're not giving any XML as input.

of course with "--if xml" I used the XML file * input file.

The error message comes from hwloc_x86_check_cpuiddump_input() failing in hwloc/topology-x86.c. That function always prints an error message before returning an error, except when opendir() fails on the given directory. The directory was passed by lstopo to the core using environment variable HWLOC_CPUID_PATH.

Anyway, I have no way to debug this for now so you're stuck with not running make check in that directory :/


Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.

hwloc-devel mailing list

Reply via email to