Re: [Valgrind-users] thread scheduling

[Julian S. <js...@ac...>]

> > priority thread is scheduled. Two threads will run interleaved (one with
> > possibly a lower priority). Is my concern grounded?
>
> Well set_sleeping will write to the pipe that all the other threads
> that are ready to run (ie not blocked in a system call made by the
> client) are trying to read from.
>
> How the kernel chooses which of threads which are trying to read from
> the pipe to wake up is up to it - but I assume it would respect the
> currently active scheduler algorithm?

I agree with Tom.  Valgrind only really provides a lock which stops 
more than one thread running at once.  It doesn't mess with scheduling
or priorities in any other way.  So unless the kernel is doing something
strange, your priorities should be observed.  Can you create a small
test case that shows the problem?

J