Re: [ANNOUNCE] v4.14.29-rt25

2018-05-03 Thread Grygorii Strashko
On 05/03/2018 10:24 AM, Sebastian Andrzej Siewior wrote: On 2018-05-01 10:04:13 [-0500], Grygorii Strashko wrote: Hi Sebastian, Hi Grygorii, Sry, it took some time as i found some instability - test "stress-ng --class os --all 0 -t 5m " not always finished :( So, I've tried to rollback to

Re: [ANNOUNCE] v4.14.29-rt25

2018-05-03 Thread Grygorii Strashko
On 05/03/2018 10:24 AM, Sebastian Andrzej Siewior wrote: On 2018-05-01 10:04:13 [-0500], Grygorii Strashko wrote: Hi Sebastian, Hi Grygorii, Sry, it took some time as i found some instability - test "stress-ng --class os --all 0 -t 5m " not always finished :( So, I've tried to rollback to

Re: [ANNOUNCE] v4.14.29-rt25

2018-05-03 Thread Sebastian Andrzej Siewior
On 2018-05-01 10:04:13 [-0500], Grygorii Strashko wrote: > Hi Sebastian, Hi Grygorii, > Sry, it took some time as i found some instability - > test "stress-ng --class os --all 0 -t 5m " not always finished :( > So, I've tried to rollback to v4.14.29-rt25 and use as TI RT kernel as > pure

Re: [ANNOUNCE] v4.14.29-rt25

2018-05-03 Thread Sebastian Andrzej Siewior
On 2018-05-01 10:04:13 [-0500], Grygorii Strashko wrote: > Hi Sebastian, Hi Grygorii, > Sry, it took some time as i found some instability - > test "stress-ng --class os --all 0 -t 5m " not always finished :( > So, I've tried to rollback to v4.14.29-rt25 and use as TI RT kernel as > pure

Re: [ANNOUNCE] v4.14.29-rt25

2018-05-01 Thread Grygorii Strashko
Hi Sebastian, On 04/23/2018 02:10 PM, Sebastian Andrzej Siewior wrote: > On 2018-04-23 11:57:39 [-0500], Grygorii Strashko wrote: >> Sry, but I can't apply it. What's you base? > > please try this patch and latest v4.14-RT I've tried this (with v4.14.34-rt27) and I do not see

Re: [ANNOUNCE] v4.14.29-rt25

2018-05-01 Thread Grygorii Strashko
Hi Sebastian, On 04/23/2018 02:10 PM, Sebastian Andrzej Siewior wrote: > On 2018-04-23 11:57:39 [-0500], Grygorii Strashko wrote: >> Sry, but I can't apply it. What's you base? > > please try this patch and latest v4.14-RT I've tried this (with v4.14.34-rt27) and I do not see

Re: [ANNOUNCE] v4.14.29-rt25

2018-04-23 Thread Sebastian Andrzej Siewior
On 2018-04-23 11:57:39 [-0500], Grygorii Strashko wrote: > Sry, but I can't apply it. What's you base? please try this patch and latest v4.14-RT diff --git a/include/linux/sched.h b/include/linux/sched.h index e305a8f8cd7d..0322503084a5 100644 --- a/include/linux/sched.h +++

Re: [ANNOUNCE] v4.14.29-rt25

2018-04-23 Thread Sebastian Andrzej Siewior
On 2018-04-23 11:57:39 [-0500], Grygorii Strashko wrote: > Sry, but I can't apply it. What's you base? please try this patch and latest v4.14-RT diff --git a/include/linux/sched.h b/include/linux/sched.h index e305a8f8cd7d..0322503084a5 100644 --- a/include/linux/sched.h +++

Re: [ANNOUNCE] v4.14.29-rt25

2018-04-23 Thread Grygorii Strashko
On 04/20/2018 12:11 PM, Sebastian Andrzej Siewior wrote: On 2018-03-27 13:01:07 [-0500], Grygorii Strashko wrote: Hi Sebastian, Hi Grygorii, I've took this RT version and applied "[RT] kernel/time/posix-timer: avoid schedule() while holding the RCU lock" [1] on top. Then I run below

Re: [ANNOUNCE] v4.14.29-rt25

2018-04-23 Thread Grygorii Strashko
On 04/20/2018 12:11 PM, Sebastian Andrzej Siewior wrote: On 2018-03-27 13:01:07 [-0500], Grygorii Strashko wrote: Hi Sebastian, Hi Grygorii, I've took this RT version and applied "[RT] kernel/time/posix-timer: avoid schedule() while holding the RCU lock" [1] on top. Then I run below

Re: [ANNOUNCE] v4.14.29-rt25

2018-04-20 Thread Sebastian Andrzej Siewior
On 2018-03-27 13:01:07 [-0500], Grygorii Strashko wrote: > Hi Sebastian, Hi Grygorii, > I've took this RT version and applied "[RT] kernel/time/posix-timer: avoid > schedule() > while holding the RCU lock" [1] on top. Then I run below tests: … > no stall or crashes were observed, but I've caught

Re: [ANNOUNCE] v4.14.29-rt25

2018-04-20 Thread Sebastian Andrzej Siewior
On 2018-03-27 13:01:07 [-0500], Grygorii Strashko wrote: > Hi Sebastian, Hi Grygorii, > I've took this RT version and applied "[RT] kernel/time/posix-timer: avoid > schedule() > while holding the RCU lock" [1] on top. Then I run below tests: … > no stall or crashes were observed, but I've caught

Re: [ANNOUNCE] v4.14.29-rt25

2018-03-27 Thread Grygorii Strashko
Hi Sebastian, On 03/25/2018 05:12 AM, Sebastian Andrzej Siewior wrote: > Dear RT folks! > > I'm pleased to announce the v4.14.29-rt25 patch set. > > Changes since v4.14.29-rt24: > >- There are checks for disabled interrupts in the target code which do > not work on RT. Reported by

Re: [ANNOUNCE] v4.14.29-rt25

2018-03-27 Thread Grygorii Strashko
Hi Sebastian, On 03/25/2018 05:12 AM, Sebastian Andrzej Siewior wrote: > Dear RT folks! > > I'm pleased to announce the v4.14.29-rt25 patch set. > > Changes since v4.14.29-rt24: > >- There are checks for disabled interrupts in the target code which do > not work on RT. Reported by

[ANNOUNCE] v4.14.29-rt25

2018-03-25 Thread Sebastian Andrzej Siewior
Dear RT folks! I'm pleased to announce the v4.14.29-rt25 patch set. Changes since v4.14.29-rt24: - There are checks for disabled interrupts in the target code which do not work on RT. Reported by Arnaldo Carvalho de Melo. Known issues - A warning triggered in

[ANNOUNCE] v4.14.29-rt25

2018-03-25 Thread Sebastian Andrzej Siewior
Dear RT folks! I'm pleased to announce the v4.14.29-rt25 patch set. Changes since v4.14.29-rt24: - There are checks for disabled interrupts in the target code which do not work on RT. Reported by Arnaldo Carvalho de Melo. Known issues - A warning triggered in