Re: [PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-15 Thread xiaofeng.yan
On 2014/8/12 22:52, Ingo Molnar wrote: * xiaofeng.yan wrote: It could be wrong for the precision of runtime and deadline when the precision is within microsecond level. For example: Task runtime deadline period P1 200us 500us 500us This case need enbale HRTICK feature by the next

Re: [PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-15 Thread xiaofeng.yan
On 2014/8/12 22:52, Ingo Molnar wrote: * xiaofeng.yan xiaofeng@huawei.com wrote: It could be wrong for the precision of runtime and deadline when the precision is within microsecond level. For example: Task runtime deadline period P1 200us 500us 500us This case need enbale HRTICK

Re: [PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-12 Thread Ingo Molnar
* xiaofeng.yan wrote: > It could be wrong for the precision of runtime and deadline > when the precision is within microsecond level. For example: > Task runtime deadline period > P1 200us 500us 500us > > This case need enbale HRTICK feature by the next command > > PC#echo "HRTICK" >

Re: [PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-12 Thread Ingo Molnar
* xiaofeng.yan xiaofeng@huawei.com wrote: It could be wrong for the precision of runtime and deadline when the precision is within microsecond level. For example: Task runtime deadline period P1 200us 500us 500us This case need enbale HRTICK feature by the next command

Re: [PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-06 Thread Juri Lelli
Hi all, On 06/08/14 10:08, xiaofeng.yan wrote: > It could be wrong for the precision of runtime and deadline > when the precision is within microsecond level. For example: > Task runtime deadline period > P1 200us 500us 500us > > This case need enbale HRTICK feature by the next command >

[PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-06 Thread xiaofeng.yan
It could be wrong for the precision of runtime and deadline when the precision is within microsecond level. For example: Task runtime deadline period P1 200us 500us 500us This case need enbale HRTICK feature by the next command PC#echo "HRTICK" > /sys/kernel/debug/sched_features

[PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-06 Thread xiaofeng.yan
It could be wrong for the precision of runtime and deadline when the precision is within microsecond level. For example: Task runtime deadline period P1 200us 500us 500us This case need enbale HRTICK feature by the next command PC#echo HRTICK /sys/kernel/debug/sched_features PC#trace-cmd

Re: [PATCH v3] sched/deadline: overrun could happen in start_hrtick_dl

2014-08-06 Thread Juri Lelli
Hi all, On 06/08/14 10:08, xiaofeng.yan wrote: It could be wrong for the precision of runtime and deadline when the precision is within microsecond level. For example: Task runtime deadline period P1 200us 500us 500us This case need enbale HRTICK feature by the next command PC#echo