Hi,
It appears that when the default policy is preferred local, the two
instances (one helgrind, one drd) are run on the same node.
I thought I could afford more processor/memory access by forcing the
two instances to run on separate nodes. When I succeeded in doing that,
one process starts up fi
I don't follow the details exactly, but FWIW .. valgrind running an
application is "just another normal process". It has no understanding
of or special-casing relating to NUMA, or particular cores/nodes in a
multiprocessor machine.
My conjecture is that the valgrind core is one instance of th
On Wed, 2024-07-17 at 20:47 +0200, Julian Seward wrote:
>
> I don't follow the details exactly, but FWIW .. valgrind running an
> application is "just another normal process". It has no
> understanding
> of or special-casing relating to NUMA, or particular cores/nodes in a
> multiprocessor machin
On Wed, 2024-07-17 at 20:47 +0200, Julian Seward wrote:
>
> I don't follow the details exactly, but FWIW .. valgrind running an
> application is "just another normal process". It has no
> understanding
> of or special-casing relating to NUMA, or particular cores/nodes in a
> multiprocessor machin
On 18/07/2024 00:00, Tsiang Elaine Reisler wrote:
Yes, there is cross-thread synchronization via shared memory, but not
cross-process. I am just running helgrind and drd on exactly the same
stand-alone program.
What CPU are you running this on?
J
