On 07/16/2013 10:17 PM, Matt Turner wrote:
> On Tue, Jul 16, 2013 at 10:34 AM, Richard Henderson wrote:
>> Use WTINT to wait for the next interrupt. Squash the WTINT call
>> if the PALcode doesn't support it (e.g. MILO). No attempt is yet
>> made to skip clock ticks during normal scheduling in
On 07/16/2013 10:17 PM, Matt Turner wrote:
On Tue, Jul 16, 2013 at 10:34 AM, Richard Henderson r...@twiddle.net wrote:
Use WTINT to wait for the next interrupt. Squash the WTINT call
if the PALcode doesn't support it (e.g. MILO). No attempt is yet
made to skip clock ticks during normal
On Tue, Jul 16, 2013 at 10:34 AM, Richard Henderson wrote:
> Use WTINT to wait for the next interrupt. Squash the WTINT call
> if the PALcode doesn't support it (e.g. MILO). No attempt is yet
> made to skip clock ticks during normal scheduling in order to stay
> in power down mode longer.
The
Use WTINT to wait for the next interrupt. Squash the WTINT call
if the PALcode doesn't support it (e.g. MILO). No attempt is yet
made to skip clock ticks during normal scheduling in order to stay
in power down mode longer.
Signed-off-by: Richard Henderson
---
arch/alpha/include/asm/pal.h
Use WTINT to wait for the next interrupt. Squash the WTINT call
if the PALcode doesn't support it (e.g. MILO). No attempt is yet
made to skip clock ticks during normal scheduling in order to stay
in power down mode longer.
Signed-off-by: Richard Henderson r...@twiddle.net
---
On Tue, Jul 16, 2013 at 10:34 AM, Richard Henderson r...@twiddle.net wrote:
Use WTINT to wait for the next interrupt. Squash the WTINT call
if the PALcode doesn't support it (e.g. MILO). No attempt is yet
made to skip clock ticks during normal scheduling in order to stay
in power down mode
6 matches
Mail list logo