Hi,
Sorry for the basic mistakes, posted new patch V1.
On 1/17/2018 5:39 PM, Thomas Gleixner wrote:
On Wed, 17 Jan 2018, Thomas Gleixner wrote:
On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote:
And please fix the subject line:
kernel: time:
is not the proper subsystem prefix.
git log
Hi,
Sorry for the basic mistakes, posted new patch V1.
On 1/17/2018 5:39 PM, Thomas Gleixner wrote:
On Wed, 17 Jan 2018, Thomas Gleixner wrote:
On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote:
And please fix the subject line:
kernel: time:
is not the proper subsystem prefix.
git log
On Wed, 17 Jan 2018, Thomas Gleixner wrote:
> On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote:
And please fix the subject line:
kernel: time:
is not the proper subsystem prefix.
git log should give you a hint.
Aside of that the text after the prefix starts with an uppercase letter.
On Wed, 17 Jan 2018, Thomas Gleixner wrote:
> On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote:
And please fix the subject line:
kernel: time:
is not the proper subsystem prefix.
git log should give you a hint.
Aside of that the text after the prefix starts with an uppercase letter.
On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote:
> In case when timers are migrated to a CPU, after it exits
> idle, but before timer base is forwarded, either from
> run_timer_softirq()/mod_timer()/add_timer_on(), it's
> possible that migrated timers are queued, based on older
> clock value.
On Wed, 17 Jan 2018, Lingutla Chandrasekhar wrote:
> In case when timers are migrated to a CPU, after it exits
> idle, but before timer base is forwarded, either from
> run_timer_softirq()/mod_timer()/add_timer_on(), it's
> possible that migrated timers are queued, based on older
> clock value.
In case when timers are migrated to a CPU, after it exits
idle, but before timer base is forwarded, either from
run_timer_softirq()/mod_timer()/add_timer_on(), it's
possible that migrated timers are queued, based on older
clock value. This can cause delays in handling those timers.
For example,
In case when timers are migrated to a CPU, after it exits
idle, but before timer base is forwarded, either from
run_timer_softirq()/mod_timer()/add_timer_on(), it's
possible that migrated timers are queued, based on older
clock value. This can cause delays in handling those timers.
For example,
8 matches
Mail list logo