Hi!
> > > Hummm, wondering how LTP sched tests could trigger this, since a quick
> > > grep into ltp didn't show DEADLINE usage.
> >
> > See kernel/syscalls/sched_setattr/sched_setattr01.c
>
> Right, saw that. I was still thinking though why the report seemed to
> point to sched, and not
Hi!
> > > Hummm, wondering how LTP sched tests could trigger this, since a quick
> > > grep into ltp didn't show DEADLINE usage.
> >
> > See kernel/syscalls/sched_setattr/sched_setattr01.c
>
> Right, saw that. I was still thinking though why the report seemed to
> point to sched, and not
On 25/01/18 13:24, Cyril Hrubis wrote:
> Hi!
> > Hummm, wondering how LTP sched tests could trigger this, since a quick
> > grep into ltp didn't show DEADLINE usage.
>
> See kernel/syscalls/sched_setattr/sched_setattr01.c
Right, saw that. I was still thinking though why the report seemed to
On 25/01/18 13:24, Cyril Hrubis wrote:
> Hi!
> > Hummm, wondering how LTP sched tests could trigger this, since a quick
> > grep into ltp didn't show DEADLINE usage.
>
> See kernel/syscalls/sched_setattr/sched_setattr01.c
Right, saw that. I was still thinking though why the report seemed to
Hi!
> Hummm, wondering how LTP sched tests could trigger this, since a quick
> grep into ltp didn't show DEADLINE usage.
See kernel/syscalls/sched_setattr/sched_setattr01.c
--
Cyril Hrubis
chru...@suse.cz
Hi!
> Hummm, wondering how LTP sched tests could trigger this, since a quick
> grep into ltp didn't show DEADLINE usage.
See kernel/syscalls/sched_setattr/sched_setattr01.c
--
Cyril Hrubis
chru...@suse.cz
6 matches
Mail list logo