<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - cairo-perf does not deal with cpus larger then 1024 well." href="https://bugs.freedesktop.org/show_bug.cgi?id=66783#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - cairo-perf does not deal with cpus larger then 1024 well." href="https://bugs.freedesktop.org/show_bug.cgi?id=66783">bug 66783</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>If CPU_SETSIZE doesn't match the value as used by the kernel, sched_getaffinity() is meant to return -EINVAL. Is that the case on your system? I don't think check_cpu_affinity() is particularly relevant when benchmarking, the impact of thread placement is interesting to study, but it is unclear that actually suggesting a particular placement is beneficial. So I can either fixup check_cpu_affinity() to ignore EINVAL or simply move the warning into the README.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>