On Thursday, June 25, 2015 09:05:49 AM Preeti U Murthy wrote:
> On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote:
> > On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
> > wrote:
> >> On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
> >>> 4.2 material I suppose?
> >>
> >> And
On Thursday, June 25, 2015 09:05:49 AM Preeti U Murthy wrote:
On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote:
On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
4.2 material I suppose?
On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote:
> On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
> wrote:
>> On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
>>> 4.2 material I suppose?
>>
>> And stable. Without this, if you configure without TICK_ONESHOT, the
>> machine
On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
wrote:
> On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
>> 4.2 material I suppose?
>
> And stable. Without this, if you configure without TICK_ONESHOT, the
> machine will hang.
OK, which -stable? All of them or any specific
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
> 4.2 material I suppose?
And stable. Without this, if you configure without TICK_ONESHOT, the
machine will hang.
Cheers,
Ben.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, Jun 25, 2015 at 12:10 AM, Michael Ellerman
wrote:
>
>
> On 24 June 2015 23:50:40 GMT+10:00, "Rafael J. Wysocki"
> wrote:
>>On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
>>> On some archs, the local clockevent device stops in deep cpuidle
>>states.
>>> The broadcast
On 24 June 2015 23:50:40 GMT+10:00, "Rafael J. Wysocki"
wrote:
>On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
>> On some archs, the local clockevent device stops in deep cpuidle
>states.
>> The broadcast framework is used to wakeup cpus in these idle states,
>in
>> which
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
> On some archs, the local clockevent device stops in deep cpuidle states.
> The broadcast framework is used to wakeup cpus in these idle states, in
> which either an external clockevent device is used to send wakeup ipis
> or the
On some archs, the local clockevent device stops in deep cpuidle states.
The broadcast framework is used to wakeup cpus in these idle states, in
which either an external clockevent device is used to send wakeup ipis
or the hrtimer broadcast framework kicks in in the absence of such a
device. One
On some archs, the local clockevent device stops in deep cpuidle states.
The broadcast framework is used to wakeup cpus in these idle states, in
which either an external clockevent device is used to send wakeup ipis
or the hrtimer broadcast framework kicks in in the absence of such a
device. One
On 24 June 2015 23:50:40 GMT+10:00, Rafael J. Wysocki r...@rjwysocki.net
wrote:
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
On some archs, the local clockevent device stops in deep cpuidle
states.
The broadcast framework is used to wakeup cpus in these idle states,
in
On Thu, Jun 25, 2015 at 12:10 AM, Michael Ellerman
mich...@ellerman.id.au wrote:
On 24 June 2015 23:50:40 GMT+10:00, Rafael J. Wysocki r...@rjwysocki.net
wrote:
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
On some archs, the local clockevent device stops in deep cpuidle
On Wednesday, June 24, 2015 01:48:01 AM Preeti U Murthy wrote:
On some archs, the local clockevent device stops in deep cpuidle states.
The broadcast framework is used to wakeup cpus in these idle states, in
which either an external clockevent device is used to send wakeup ipis
or the hrtimer
On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
4.2 material I suppose?
And stable. Without this, if you configure without TICK_ONESHOT, the
machine will hang.
OK, which -stable? All of them
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
4.2 material I suppose?
And stable. Without this, if you configure without TICK_ONESHOT, the
machine will hang.
Cheers,
Ben.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On 06/25/2015 05:36 AM, Rafael J. Wysocki wrote:
On Thu, Jun 25, 2015 at 12:06 AM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
On Wed, 2015-06-24 at 15:50 +0200, Rafael J. Wysocki wrote:
4.2 material I suppose?
And stable. Without this, if you configure without TICK_ONESHOT, the
16 matches
Mail list logo
