|
From: Nicholas N. <nj...@ca...> - 2004-07-05 08:57:58
|
On Sun, 4 Jul 2004, Tom Hughes wrote: > As a result it typically seems to get allocated in the valgrind part > of the address space which can't be accessed by the client while > pointer checking is turned on. As libaio tries to peek at it in order > to avoid entering the kernel when io_getevents is called and there > are no events pending this is a problem... > > Anybody got any suggestions for a way of handling this? Something Julian suggested: instead of partitioning the address space, as we currently do -- part for the client, part for Valgrind+tool -- instead virtualize it, by introducing a software MMU. Every address would have to be converted before use, though... it would be a lot of infrastructure and probably quite tricky, and possibly very slow. However, it would get rid of the problems with the client and Valgrind banging heads in the address space. N |