On Thu, 22 Oct 2015, Yang Yingliang wrote:
> But I found out when the cpu is stalling, basenow.tv64(7676664221321) is
> bigger than ktime_get().tv64(7336008904750) in hrtimer_interrupt() and
> the timer->_softexpires is 733628800. This makes it can not finish
> the while loop until
On Thu, 22 Oct 2015, Yang Yingliang wrote:
> But I found out when the cpu is stalling, basenow.tv64(7676664221321) is
> bigger than ktime_get().tv64(7336008904750) in hrtimer_interrupt() and
> the timer->_softexpires is 733628800. This makes it can not finish
> the while loop until
On 2015/10/22 18:25, Thomas Gleixner wrote:
On Thu, 22 Oct 2015, Ding Tianhong wrote:
On 2015/10/22 15:43, Thomas Gleixner wrote:
Jan 01 00:03:32 Linux kernel: i:0 basenow.tv64:4809284991830
hrtimer_get_softexpires_tv64(timer):444012000 ccpu0
timer:ffdffdec6138,
On Thu, 22 Oct 2015, Ding Tianhong wrote:
> On 2015/10/22 15:43, Thomas Gleixner wrote:
> >> Jan 01 00:03:32 Linux kernel: i:0 basenow.tv64:4809284991830
> >> hrtimer_get_softexpires_tv64(timer):444012000 ccpu0
> >> timer:ffdffdec6138, timer->function:ffc000129b84
> >> Jan 01 00:03:32
On 2015/10/22 15:43, Thomas Gleixner wrote:
> On Thu, 22 Oct 2015, Yang Yingliang wrote:
>> I use the kernel-4.1.6 running on arm64.
>> My testcase is that it calls clock_settime and clock_adjtime alternately with
>> random params on each core. My system has 32 cores.
>>
>> I found the cpu
On Thu, 22 Oct 2015, Yang Yingliang wrote:
> I use the kernel-4.1.6 running on arm64.
> My testcase is that it calls clock_settime and clock_adjtime alternately with
> random params on each core. My system has 32 cores.
>
> I found the cpu stalling in hrtimer_intterrupts(). So I added some debug
Hi Thomas,
I got the following call trace when I called some set time syscalls in
userspace.
---start---
Jan 01 00:02:29 Linux kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Jan 01 00:02:29 Linux kernel: 0: (2 GPs behind) idle=913/1/0
softirq=59289/59291 fqs=488
Jan 01
Hi Thomas,
I got the following call trace when I called some set time syscalls in
userspace.
---start---
Jan 01 00:02:29 Linux kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Jan 01 00:02:29 Linux kernel: 0: (2 GPs behind) idle=913/1/0
softirq=59289/59291 fqs=488
Jan 01
On 2015/10/22 15:43, Thomas Gleixner wrote:
> On Thu, 22 Oct 2015, Yang Yingliang wrote:
>> I use the kernel-4.1.6 running on arm64.
>> My testcase is that it calls clock_settime and clock_adjtime alternately with
>> random params on each core. My system has 32 cores.
>>
>> I found the cpu
On Thu, 22 Oct 2015, Ding Tianhong wrote:
> On 2015/10/22 15:43, Thomas Gleixner wrote:
> >> Jan 01 00:03:32 Linux kernel: i:0 basenow.tv64:4809284991830
> >> hrtimer_get_softexpires_tv64(timer):444012000 ccpu0
> >> timer:ffdffdec6138, timer->function:ffc000129b84
> >> Jan 01 00:03:32
On 2015/10/22 18:25, Thomas Gleixner wrote:
On Thu, 22 Oct 2015, Ding Tianhong wrote:
On 2015/10/22 15:43, Thomas Gleixner wrote:
Jan 01 00:03:32 Linux kernel: i:0 basenow.tv64:4809284991830
hrtimer_get_softexpires_tv64(timer):444012000 ccpu0
timer:ffdffdec6138,
On Thu, 22 Oct 2015, Yang Yingliang wrote:
> I use the kernel-4.1.6 running on arm64.
> My testcase is that it calls clock_settime and clock_adjtime alternately with
> random params on each core. My system has 32 cores.
>
> I found the cpu stalling in hrtimer_intterrupts(). So I added some debug
12 matches
Mail list logo