jreiser@BitWagon.com said:
> In order to prevent races between valgrind for UML and kernel
> allocators which valgrind does not "know", then the VALGRIND_*
> declarations being added to kernel allocators should allow for
> expressing the concept "atomically change state in both allocator and
> valgrind".
What are you talking about?
There are no atomicity problems between UML and valgrind.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Dec 23 2002 - 22:00:29 EST