Hi Thomas,
* Thomas Gleixner :
> On Tue, 29 Dec 2015, Helge Deller wrote:
> > No, the patch below doesn't help.
> >
> > I still see:
> > [ 644.916000] timerfd_settime: interval (sec=0, nsec=1) it_value
> > (sec=0, nsec=1)
> > [ 645.024000] timerfd_gettime: interval (sec=0, nse
On Tue, 29 Dec 2015, Helge Deller wrote:
> No, the patch below doesn't help.
>
> I still see:
> [ 644.916000] timerfd_settime: interval (sec=0, nsec=1) it_value
> (sec=0, nsec=1)
> [ 645.024000] timerfd_gettime: interval (sec=0, nsec=1) it_value
> (sec=0, nsec=10302994
On 29.12.2015 10:44, Thomas Gleixner wrote:
> On Sat, 26 Dec 2015, Helge Deller wrote:
>> I see a strange behavior on the parisc platform, for which I'm not sure if
>> it's intended or if there is a bug somewhere.
>
>> The program calls timerfd_settime() and sets a timer (e.g. sec=0,
>> nsec=1000
Helge,
On Sat, 26 Dec 2015, Helge Deller wrote:
> I see a strange behavior on the parisc platform, for which I'm not sure if
> it's intended or if there is a bug somewhere.
> The program calls timerfd_settime() and sets a timer (e.g. sec=0,
> nsec=1).
> Directly after setting the timer
Hi Thomas,
I see a strange behavior on the parisc platform, for which I'm not sure if it's
intended or
if there is a bug somewhere.
The program calls timerfd_settime() and sets a timer (e.g. sec=0,
nsec=1).
Directly after setting the timer it calls timerfd_gettime() and receives
(sec=0
5 matches
Mail list logo