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
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
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
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
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
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
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
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.
> >>
> >>
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
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,
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,
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
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
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
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
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
16 matches
Mail list logo