Thread (38 messages) 38 messages, 6 authors, 2016-03-02

Re: [patch 01/20] idle: Move x86ism out of generic code

From: Will Deacon <hidden>
Date: 2016-02-29 19:48:07
Also in: lkml

On Mon, Feb 29, 2016 at 08:35:41PM +0100, Thomas Gleixner wrote:
On Sat, 27 Feb 2016, Brian Gerst wrote:
quoted
quoted
        arch_cpu_idle_prepare();
        cpu_idle_loop();
 }
Does this actually work with stack protector enabled?
boot_init_stack_canary() is inlined while arch_cpu_idle_prepare() is
not.
Stupid me. No it does of course not. I could have sworn that I tested that,
but obvioulsy not.

I drop that patch, but actually the real question is whether we can drop that
'#ifdef x86' around that boot_init_stack_canary() invocation.

AFAICT, neither arm, arm64 nor mips and sh call it on anything else than the
boot cpu. I can't see why that would be an issue on those architectures and
why it would be a problem if the boot cpu calls it again here.

CC'ed the relevant maintainers. Is there any issue with the patch below?
On arm[64], the canary is unfortunately global, so I don't think it would
be safe to update it live like this without effectively stopping the
machine and forcing everybody into idle.

Will
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help