On 2015/10/29 15:36, Yang Yingliang wrote:
On 2015/10/27 22:03, Mark Rutland wrote:
On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
In multi-core system, if the clock is not sync perfectly, it
will make cycle_last that recorded by CPU-A is a little more
than cycle_now that
On 2015/10/27 22:03, Mark Rutland wrote:
On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
In multi-core system, if the clock is not sync perfectly, it
will make cycle_last that recorded by CPU-A is a little more
than cycle_now that read by CPU-B.
If that is happening, that
On 2015/10/27 22:03, Mark Rutland wrote:
On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
In multi-core system, if the clock is not sync perfectly, it
will make cycle_last that recorded by CPU-A is a little more
than cycle_now that read by CPU-B.
If that is happening, that
On 2015/10/29 15:36, Yang Yingliang wrote:
On 2015/10/27 22:03, Mark Rutland wrote:
On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
In multi-core system, if the clock is not sync perfectly, it
will make cycle_last that recorded by CPU-A is a little more
than cycle_now that
On 2015/10/27 22:03, Mark Rutland wrote:
> On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
>> In multi-core system, if the clock is not sync perfectly, it
>> will make cycle_last that recorded by CPU-A is a little more
>> than cycle_now that read by CPU-B.
>
> If that is
On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
> In multi-core system, if the clock is not sync perfectly, it
> will make cycle_last that recorded by CPU-A is a little more
> than cycle_now that read by CPU-B.
If that is happening, that sounds like a hardware and/or firmware bug.
In multi-core system, if the clock is not sync perfectly, it
will make cycle_last that recorded by CPU-A is a little more
than cycle_now that read by CPU-B. With the negative result,
hrtimer_update_base() return a huge and wrong time. It leads
to the cpu can not finish the while loop in
In multi-core system, if the clock is not sync perfectly, it
will make cycle_last that recorded by CPU-A is a little more
than cycle_now that read by CPU-B. With the negative result,
hrtimer_update_base() return a huge and wrong time. It leads
to the cpu can not finish the while loop in
On 2015/10/27 22:03, Mark Rutland wrote:
> On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
>> In multi-core system, if the clock is not sync perfectly, it
>> will make cycle_last that recorded by CPU-A is a little more
>> than cycle_now that read by CPU-B.
>
> If that is
On Tue, Oct 27, 2015 at 09:21:13PM +0800, Yang Yingliang wrote:
> In multi-core system, if the clock is not sync perfectly, it
> will make cycle_last that recorded by CPU-A is a little more
> than cycle_now that read by CPU-B.
If that is happening, that sounds like a hardware and/or firmware bug.
10 matches
Mail list logo