On 05/13/2014 02:11 PM, Juri Lelli wrote:
> On Tue, 13 May 2014 12:43:07 +0200
> Peter Zijlstra wrote:
>
>> On Tue, May 13, 2014 at 11:57:49AM +0200, Juri Lelli wrote:
>>> static bool
>>> __checkparam_dl(const struct sched_attr *attr)
>>> {
>>> return attr && attr->sched_deadline != 0 &&
>
On Tue, 13 May 2014 12:43:07 +0200
Peter Zijlstra wrote:
> On Tue, May 13, 2014 at 11:57:49AM +0200, Juri Lelli wrote:
> > static bool
> > __checkparam_dl(const struct sched_attr *attr)
> > {
> > return attr && attr->sched_deadline != 0 &&
> > (attr->sched_period == 0 ||
> > -
On Tue, May 13, 2014 at 11:57:49AM +0200, Juri Lelli wrote:
> static bool
> __checkparam_dl(const struct sched_attr *attr)
> {
> return attr && attr->sched_deadline != 0 &&
> (attr->sched_period == 0 ||
> - (s64)(attr->sched_period - attr->sched_deadline) >= 0)
Hi all,
On Mon, 12 May 2014 14:30:32 +0200
Peter Zijlstra wrote:
> On Mon, May 12, 2014 at 11:19:39AM +0200, Michael Kerrisk (man-pages) wrote:
> > Hi Peter,
> >
> > On Mon, May 12, 2014 at 10:47 AM, Peter Zijlstra
> > wrote:
> > > On Mon, May 12, 2014 at 08:53:59AM +0200, Michael Kerrisk (ma
On Mon, May 12, 2014 at 11:19:39AM +0200, Michael Kerrisk (man-pages) wrote:
> Hi Peter,
>
> On Mon, May 12, 2014 at 10:47 AM, Peter Zijlstra wrote:
> > On Mon, May 12, 2014 at 08:53:59AM +0200, Michael Kerrisk (man-pages) wrote:
> >> On 05/11/2014 04:54 PM, Michael Kerrisk (man-pages) wrote:
> >
Hi Peter,
On Mon, May 12, 2014 at 10:47 AM, Peter Zijlstra wrote:
> On Mon, May 12, 2014 at 08:53:59AM +0200, Michael Kerrisk (man-pages) wrote:
>> On 05/11/2014 04:54 PM, Michael Kerrisk (man-pages) wrote:
>
>> > $ time sudo ./t_sched_setattr d 18446744072 18446744072 18446744073
>>
>> I realize
On Mon, May 12, 2014 at 08:53:59AM +0200, Michael Kerrisk (man-pages) wrote:
> On 05/11/2014 04:54 PM, Michael Kerrisk (man-pages) wrote:
> > $ time sudo ./t_sched_setattr d 18446744072 18446744072 18446744073
>
> I realize my speculation was completely off the mark. time(2) really
> is reportin
On 05/11/2014 04:54 PM, Michael Kerrisk (man-pages) wrote:
> [Dave: I wonder if there's anything trinity can add in the way of
> a test here?]
>
> Hi Peter,
>
> This looks like another bug in sched_setattr(). Using the program
> below (which you might find generally helpful for testing), I'm
>
On 05/11/2014 04:54 PM, Michael Kerrisk (man-pages) wrote:
> $ time sudo ./t_sched_setattr d 18446744072 18446744072 18446744073
>
> 'd' here means use SCHED_DEADLINE, then the remaining arguments
> are the Runtime, Deadline, and Period, expressed in *seconds*.
> (Those number by the way are just
[Dave: I wonder if there's anything trinity can add in the way of
a test here?]
Hi Peter,
This looks like another bug in sched_setattr(). Using the program
below (which you might find generally helpful for testing), I'm
able to reliably freeze up my x64 (Intel Core i7-3520M Processor)
system f
10 matches
Mail list logo
