Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-10-22 Thread Viresh Kumar
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 http://vge

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-10-04 Thread Sebastian Andrzej Siewior
* 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 --

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-08-07 Thread Viresh Kumar
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 majord...@vger.kernel.org

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-07-24 Thread Viresh Kumar
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? >>> >>

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-06-17 Thread Viresh Kumar
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

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-05-31 Thread Viresh Kumar
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 have

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-05-22 Thread Viresh Kumar
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 >> --- a/

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-05-22 Thread Peter Zijlstra
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 >

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-05-22 Thread Viresh Kumar
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 prop

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-05-13 Thread Thomas Gleixner
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 +05

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-05-13 Thread Viresh Kumar
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!! >>> >>> Remi

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-04-24 Thread Viresh Kumar
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? > >

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-04-09 Thread Viresh Kumar
[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 itself

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2013-03-20 Thread Viresh Kumar
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, &flags); >>

Re: [PATCH V2 Resend 4/4] timer: Migrate running timer

2012-11-27 Thread Steven Rostedt
[ 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 __mod_time