Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-11 Thread Arnd Bergmann
On Friday 08 March 2013, Thomas Gleixner wrote: > On Fri, 8 Mar 2013, Daniel Lezcano wrote: > > On 03/06/2013 10:48 AM, Thomas Gleixner wrote: > > I was wondering if it would be possible to take the 3/4 and 4/4 > > otherwise the flag dependency will prevent to send those to the > > maintainer's

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-11 Thread Arnd Bergmann
On Friday 08 March 2013, Thomas Gleixner wrote: On Fri, 8 Mar 2013, Daniel Lezcano wrote: On 03/06/2013 10:48 AM, Thomas Gleixner wrote: I was wondering if it would be possible to take the 3/4 and 4/4 otherwise the flag dependency will prevent to send those to the maintainer's tree until

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-07 Thread Thomas Gleixner
On Fri, 8 Mar 2013, Daniel Lezcano wrote: > On 03/06/2013 10:48 AM, Thomas Gleixner wrote: > I was wondering if it would be possible to take the 3/4 and 4/4 > otherwise the flag dependency will prevent to send those to the > maintainer's tree until they gain visibility on it. I can take them with

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-07 Thread Daniel Lezcano
On 03/06/2013 10:48 AM, Thomas Gleixner wrote: > On Wed, 6 Mar 2013, Daniel Lezcano wrote: >> On 03/05/2013 09:40 PM, Thomas Gleixner wrote: >>> On Sat, 2 Mar 2013, Daniel Lezcano wrote: When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-07 Thread Daniel Lezcano
On 03/06/2013 10:48 AM, Thomas Gleixner wrote: On Wed, 6 Mar 2013, Daniel Lezcano wrote: On 03/05/2013 09:40 PM, Thomas Gleixner wrote: On Sat, 2 Mar 2013, Daniel Lezcano wrote: When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame work to use the

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-07 Thread Thomas Gleixner
On Fri, 8 Mar 2013, Daniel Lezcano wrote: On 03/06/2013 10:48 AM, Thomas Gleixner wrote: I was wondering if it would be possible to take the 3/4 and 4/4 otherwise the flag dependency will prevent to send those to the maintainer's tree until they gain visibility on it. I can take them with the

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-06 Thread Daniel Lezcano
On 03/06/2013 10:48 AM, Thomas Gleixner wrote: > On Wed, 6 Mar 2013, Daniel Lezcano wrote: >> On 03/05/2013 09:40 PM, Thomas Gleixner wrote: >>> On Sat, 2 Mar 2013, Daniel Lezcano wrote: When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-06 Thread Thomas Gleixner
On Wed, 6 Mar 2013, Daniel Lezcano wrote: > On 03/05/2013 09:40 PM, Thomas Gleixner wrote: > > On Sat, 2 Mar 2013, Daniel Lezcano wrote: > >> When a cpu goes to a deep idle state where its local timer is shutdown, > >> it notifies the time frame work to use the broadcast timer instead. > >> > >>

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-06 Thread Daniel Lezcano
On 03/05/2013 09:40 PM, Thomas Gleixner wrote: > On Sat, 2 Mar 2013, Daniel Lezcano wrote: >> When a cpu goes to a deep idle state where its local timer is shutdown, >> it notifies the time frame work to use the broadcast timer instead. >> >> Unfortunately, the broadcast device could wake up any

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-06 Thread Daniel Lezcano
On 03/05/2013 09:40 PM, Thomas Gleixner wrote: On Sat, 2 Mar 2013, Daniel Lezcano wrote: When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame work to use the broadcast timer instead. Unfortunately, the broadcast device could wake up any CPU,

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-06 Thread Thomas Gleixner
On Wed, 6 Mar 2013, Daniel Lezcano wrote: On 03/05/2013 09:40 PM, Thomas Gleixner wrote: On Sat, 2 Mar 2013, Daniel Lezcano wrote: When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame work to use the broadcast timer instead. Unfortunately,

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-06 Thread Daniel Lezcano
On 03/06/2013 10:48 AM, Thomas Gleixner wrote: On Wed, 6 Mar 2013, Daniel Lezcano wrote: On 03/05/2013 09:40 PM, Thomas Gleixner wrote: On Sat, 2 Mar 2013, Daniel Lezcano wrote: When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame work to use the

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-05 Thread Thomas Gleixner
On Sat, 2 Mar 2013, Daniel Lezcano wrote: > When a cpu goes to a deep idle state where its local timer is shutdown, > it notifies the time frame work to use the broadcast timer instead. > > Unfortunately, the broadcast device could wake up any CPU, including an > idle one which is not concerned

Re: [PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-05 Thread Thomas Gleixner
On Sat, 2 Mar 2013, Daniel Lezcano wrote: When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame work to use the broadcast timer instead. Unfortunately, the broadcast device could wake up any CPU, including an idle one which is not concerned by the

[PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-02 Thread Daniel Lezcano
When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame work to use the broadcast timer instead. Unfortunately, the broadcast device could wake up any CPU, including an idle one which is not concerned by the wake up at all. This implies, in the worst

[PATCH 2/4][V2] time : set broadcast irq affinity

2013-03-02 Thread Daniel Lezcano
When a cpu goes to a deep idle state where its local timer is shutdown, it notifies the time frame work to use the broadcast timer instead. Unfortunately, the broadcast device could wake up any CPU, including an idle one which is not concerned by the wake up at all. This implies, in the worst