On 4 October 2013 18:09, Sebastian Andrzej Siewior
wrote:
> tglx, could you please take a look at this patch / thread?
Thomas, Ping!!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 4 October 2013 18:09, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
tglx, could you please take a look at this patch / thread?
Thomas, Ping!!
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
* Viresh Kumar | 2013-08-07 15:25:55 [+0530]:
>On 24 July 2013 14:47, Viresh Kumar wrote:
>> On 18 June 2013 10:21, Viresh Kumar wrote:
>
>> Hi Thomas,
>>
>> Do you still see some light of hope in this patch :) ?
>
>Ping!!
tglx, could you please take a look at this patch / thread?
Sebastian
* Viresh Kumar | 2013-08-07 15:25:55 [+0530]:
On 24 July 2013 14:47, Viresh Kumar viresh.ku...@linaro.org wrote:
On 18 June 2013 10:21, Viresh Kumar viresh.ku...@linaro.org wrote:
Hi Thomas,
Do you still see some light of hope in this patch :) ?
Ping!!
tglx, could you please take a look at
On 24 July 2013 14:47, Viresh Kumar wrote:
> On 18 June 2013 10:21, Viresh Kumar wrote:
> Hi Thomas,
>
> Do you still see some light of hope in this patch :) ?
Ping!!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 24 July 2013 14:47, Viresh Kumar viresh.ku...@linaro.org wrote:
On 18 June 2013 10:21, Viresh Kumar viresh.ku...@linaro.org wrote:
Hi Thomas,
Do you still see some light of hope in this patch :) ?
Ping!!
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On 18 June 2013 10:21, Viresh Kumar wrote:
> On 31 May 2013 16:19, Viresh Kumar wrote:
>> On 22 May 2013 14:04, Viresh Kumar wrote:
>>> Sorry for being late in replying to your queries.
>>>
>>> On 13 May 2013 16:05, Thomas Gleixner wrote:
Which mechanism is migrating the timer away?
>>>
On 18 June 2013 10:21, Viresh Kumar viresh.ku...@linaro.org wrote:
On 31 May 2013 16:19, Viresh Kumar viresh.ku...@linaro.org wrote:
On 22 May 2013 14:04, Viresh Kumar viresh.ku...@linaro.org wrote:
Sorry for being late in replying to your queries.
On 13 May 2013 16:05, Thomas Gleixner
On 31 May 2013 16:19, Viresh Kumar wrote:
> On 22 May 2013 14:04, Viresh Kumar wrote:
>> Sorry for being late in replying to your queries.
>>
>> On 13 May 2013 16:05, Thomas Gleixner wrote:
>>> Which mechanism is migrating the timer away?
>>
>> It will be the same: get_nohz_timer_target() which
On 31 May 2013 16:19, Viresh Kumar viresh.ku...@linaro.org wrote:
On 22 May 2013 14:04, Viresh Kumar viresh.ku...@linaro.org wrote:
Sorry for being late in replying to your queries.
On 13 May 2013 16:05, Thomas Gleixner t...@linutronix.de wrote:
Which mechanism is migrating the timer away?
On 22 May 2013 14:04, Viresh Kumar wrote:
> Sorry for being late in replying to your queries.
>
> On 13 May 2013 16:05, Thomas Gleixner wrote:
>> Which mechanism is migrating the timer away?
>
> It will be the same: get_nohz_timer_target() which will decide target
> cpu for migration.
>
>> I
On 22 May 2013 14:04, Viresh Kumar viresh.ku...@linaro.org wrote:
Sorry for being late in replying to your queries.
On 13 May 2013 16:05, Thomas Gleixner t...@linutronix.de wrote:
Which mechanism is migrating the timer away?
It will be the same: get_nohz_timer_target() which will decide
On 22 May 2013 14:36, Peter Zijlstra wrote:
> On Wed, May 22, 2013 at 02:04:16PM +0530, Viresh Kumar wrote:
>
>> So, this is the clean draft for the idea I had.. (Naming is poor for
>> now):
>>
>> diff --git a/include/linux/timer.h b/include/linux/timer.h
>> index 8c5a197..ad00ebe 100644
>> ---
On Wed, May 22, 2013 at 02:04:16PM +0530, Viresh Kumar wrote:
> So, this is the clean draft for the idea I had.. (Naming is poor for
> now):
>
> diff --git a/include/linux/timer.h b/include/linux/timer.h
> index 8c5a197..ad00ebe 100644
> --- a/include/linux/timer.h
> +++ b/include/linux/timer.h
Sorry for being late in replying to your queries.
On 13 May 2013 16:05, Thomas Gleixner wrote:
> Which mechanism is migrating the timer away?
It will be the same: get_nohz_timer_target() which will decide target
cpu for migration.
> I have no objections to the functionality per se, but the
Sorry for being late in replying to your queries.
On 13 May 2013 16:05, Thomas Gleixner t...@linutronix.de wrote:
Which mechanism is migrating the timer away?
It will be the same: get_nohz_timer_target() which will decide target
cpu for migration.
I have no objections to the functionality per
On Wed, May 22, 2013 at 02:04:16PM +0530, Viresh Kumar wrote:
So, this is the clean draft for the idea I had.. (Naming is poor for
now):
diff --git a/include/linux/timer.h b/include/linux/timer.h
index 8c5a197..ad00ebe 100644
--- a/include/linux/timer.h
+++ b/include/linux/timer.h
@@
On 22 May 2013 14:36, Peter Zijlstra pet...@infradead.org wrote:
On Wed, May 22, 2013 at 02:04:16PM +0530, Viresh Kumar wrote:
So, this is the clean draft for the idea I had.. (Naming is poor for
now):
diff --git a/include/linux/timer.h b/include/linux/timer.h
index 8c5a197..ad00ebe 100644
On Mon, 13 May 2013, Viresh Kumar wrote:
> On 24 April 2013 16:52, Viresh Kumar wrote:
> > On 9 April 2013 20:22, Viresh Kumar wrote:
> >> [Steven replied to a personal Ping!!, including everybody again]
> >>
> >> On 9 April 2013 19:25, Steven Rostedt wrote:
> >>> On Tue, 2013-04-09 at 14:05
On 24 April 2013 16:52, Viresh Kumar wrote:
> On 9 April 2013 20:22, Viresh Kumar wrote:
>> [Steven replied to a personal Ping!!, including everybody again]
>>
>> On 9 April 2013 19:25, Steven Rostedt wrote:
>>> On Tue, 2013-04-09 at 14:05 +0530, Viresh Kumar wrote:
Ping!!
>>>
>>>
On 24 April 2013 16:52, Viresh Kumar viresh.ku...@linaro.org wrote:
On 9 April 2013 20:22, Viresh Kumar viresh.ku...@linaro.org wrote:
[Steven replied to a personal Ping!!, including everybody again]
On 9 April 2013 19:25, Steven Rostedt rost...@goodmis.org wrote:
On Tue, 2013-04-09 at 14:05
On Mon, 13 May 2013, Viresh Kumar wrote:
On 24 April 2013 16:52, Viresh Kumar viresh.ku...@linaro.org wrote:
On 9 April 2013 20:22, Viresh Kumar viresh.ku...@linaro.org wrote:
[Steven replied to a personal Ping!!, including everybody again]
On 9 April 2013 19:25, Steven Rostedt
On 9 April 2013 20:22, Viresh Kumar wrote:
> [Steven replied to a personal Ping!!, including everybody again]
>
> On 9 April 2013 19:25, Steven Rostedt wrote:
>> On Tue, 2013-04-09 at 14:05 +0530, Viresh Kumar wrote:
>>> Ping!!
>>>
>>
>> Remind me again. What problem are you trying to solve?
>
>
On 9 April 2013 20:22, Viresh Kumar viresh.ku...@linaro.org wrote:
[Steven replied to a personal Ping!!, including everybody again]
On 9 April 2013 19:25, Steven Rostedt rost...@goodmis.org wrote:
On Tue, 2013-04-09 at 14:05 +0530, Viresh Kumar wrote:
Ping!!
Remind me again. What problem
[Steven replied to a personal Ping!!, including everybody again]
On 9 April 2013 19:25, Steven Rostedt wrote:
> On Tue, 2013-04-09 at 14:05 +0530, Viresh Kumar wrote:
>> Ping!!
>>
>
> Remind me again. What problem are you trying to solve?
I was trying to migrate a running timer which arms
[Steven replied to a personal Ping!!, including everybody again]
On 9 April 2013 19:25, Steven Rostedt rost...@goodmis.org wrote:
On Tue, 2013-04-09 at 14:05 +0530, Viresh Kumar wrote:
Ping!!
Remind me again. What problem are you trying to solve?
I was trying to migrate a running timer
On 27 November 2012 19:17, Steven Rostedt wrote:
> On Tue, 2012-11-06 at 16:08 +0530, Viresh Kumar wrote:
>> diff --git a/kernel/timer.c b/kernel/timer.c
>> @@ -729,6 +730,12 @@ __mod_timer(struct timer_list *timer, unsigned long
>> expires,
>>
>> base = lock_timer_base(timer, );
>>
>> +
On 27 November 2012 19:17, Steven Rostedt rost...@goodmis.org wrote:
On Tue, 2012-11-06 at 16:08 +0530, Viresh Kumar wrote:
diff --git a/kernel/timer.c b/kernel/timer.c
@@ -729,6 +730,12 @@ __mod_timer(struct timer_list *timer, unsigned long
expires,
base = lock_timer_base(timer,
[ Added John Stultz ]
On Tue, 2012-11-06 at 16:08 +0530, Viresh Kumar wrote:
> Till now, we weren't migrating a running timer because with migration
> del_timer_sync() can't detect that the timer's handler yet has not finished.
>
> Now, when can we actually to reach to the code (inside
[ Added John Stultz ]
On Tue, 2012-11-06 at 16:08 +0530, Viresh Kumar wrote:
Till now, we weren't migrating a running timer because with migration
del_timer_sync() can't detect that the timer's handler yet has not finished.
Now, when can we actually to reach to the code (inside
Till now, we weren't migrating a running timer because with migration
del_timer_sync() can't detect that the timer's handler yet has not finished.
Now, when can we actually to reach to the code (inside __mod_timer()) where
base->running_timer == timer ? i.e. We are trying to migrate current
Till now, we weren't migrating a running timer because with migration
del_timer_sync() can't detect that the timer's handler yet has not finished.
Now, when can we actually to reach to the code (inside __mod_timer()) where
base-running_timer == timer ? i.e. We are trying to migrate current timer
32 matches
Mail list logo
