Philippe Gerum wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> unfortunately I'm forced to switch to other bugs, but I found out a bit
>> more about the issue that pthread_getschedparam doesn't return the
>> correct policy&prio under trunk - at least when called from threads
>> created via pthread_create a
Jan Kiszka wrote:
> Hi,
>
> unfortunately I'm forced to switch to other bugs, but I found out a bit
> more about the issue that pthread_getschedparam doesn't return the
> correct policy&prio under trunk - at least when called from threads
> created via pthread_create as SCHED_FIFO:
>
> Such threa
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Hi,
>>
>> unfortunately I'm forced to switch to other bugs, but I found out a bit
>> more about the issue that pthread_getschedparam doesn't return the
>> correct policy&prio under trunk - at least when called from threads
>> created via pthread_cr
Jan Kiszka wrote:
> Hi,
>
> unfortunately I'm forced to switch to other bugs, but I found out a bit
> more about the issue that pthread_getschedparam doesn't return the
> correct policy&prio under trunk - at least when called from threads
> created via pthread_create as SCHED_FIFO:
>
> Such threa
Hi,
unfortunately I'm forced to switch to other bugs, but I found out a bit
more about the issue that pthread_getschedparam doesn't return the
correct policy&prio under trunk - at least when called from threads
created via pthread_create as SCHED_FIFO:
Such threads start with SCHED_OTHER, but the
