Displaying 5 results from an estimated 5 matches for "cpuida".
Did you mean:
cpuid
2012 Nov 07
1
[LLVMdev] New benchmark in test-suite
On 6 November 2012 22:34, Daniel Dunbar <daniel at zuster.org> wrote:
> You are right, the failure on compile_time indicates that the test isn't
> even building. As provided, the tests don't actually define the cpuida() or
> calculateMHz() functions so that seems expected to me.
I defined both functions as NOPs.
I got what it was. The original makefile had a "-o lloops" on the
compile command and I wrongfully copied it to the LDFLAGS, so it was
generating the binary on the current dir, not on the...
2012 Nov 06
0
[LLVMdev] New benchmark in test-suite
Hey Renato,
You are right, the failure on compile_time indicates that the test isn't
even building. As provided, the tests don't actually define the cpuida() or
calculateMHz() functions so that seems expected to me.
The compile failures end up getting buried in the logs, but they will
either be in the test.log file in the top-level sandbox directory, or
inside the <filename>.llvm.o.compile files in the Output directory for that
test (i.e. Singl...
2012 Nov 05
2
[LLVMdev] New benchmark in test-suite
Hi Daniel,
I'm trying to add LivermoreLoops test to the benchmark suite (tar ball
attached), but I'm getting the error below:
--- Tested: 2 tests --
FAIL: SingleSource/Benchmarks/LivermoreLoops/lloops.compile_time (1 of 2)
FAIL: SingleSource/Benchmarks/LivermoreLoops/lloops.execution_time (2 of 2)
When I use the option to only run this test:
--only-test
2013 Sep 06
21
[PATCH v2 0/5] xl: allow for node-wise specification of vcpu pinning
Hi all,
This is the second take of a patch that I submitted some time ago for allowing
specifying vcpu pinning taking NUMA nodes into account. IOW, something like
this:
* "nodes:0-3": all pCPUs of nodes 0,1,2,3;
* "nodes:0-3,^node:2": all pCPUS of nodes 0,1,3;
* "1,nodes:1-2,^6": pCPU 1 plus all pCPUs of nodes 1,2
but not pCPU 6;
v1 was a single patch, this is
2012 Jul 04
53
[PATCH 00 of 10 v3] Automatic NUMA placement for xl
Hello,
Third version of the NUMA placement series Xen 4.2.
All the comments received during v2''s review have been addressed (more details
in single changelogs).
The most notable changes are the following:
- the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the
recent patches that allows us to allocate bitmaps of different sizes;
- the heuristics for deciding