[Valgrind-users] thread scheduling

[Pim N. <pn...@ai...>]

Hi,

First of all. Valgrind works great! However I'm having some trouble with 
thread scheduling.

I noticed that Valgrinds scheduler yields the processor to another 
thread after excecuting N basic blocks. Does someone know why Valgrinds 
scheduler uses slices instead of just relying on the scheduling of the 
threads?

I try to run Valgrind 3.2.1 on an embedded system (ppc32) where the 
application sets a fifo scheduling policy for the threads.
Since I need to keep fifo scheduling I need to disable this slice 
system. Is it save to comment out the following lines in the scheduler?

  while(!VG_(is_exiting)(tid)) {
       if (VG_(dispatch_ctr) == 1) {
	 VG_(set_sleeping)(tid, VgTs_Yielding); // <-- comment out
	 /* nothing */
	 VG_(set_running)(tid);                 // <-- comment out
	...

This seemed to me the least aggresive change. Running this seems to be 
fine, but I figured there would be a reason for this slice business and 
maybe I screw it up.

-- 
Do you know about the dangers of DRM? Find out at
http://www.defectivebydesign.org/what_is_drm

-- 
This message has been scanned for viruses and is believed to be clean