[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <52A5C846.30308@linaro.org>
Date: Mon, 09 Dec 2013 21:40:22 +0800
From: Alex Shi <alex.shi@...aro.org>
To: Daniel Lezcano <daniel.lezcano@...aro.org>,
Frederic Weisbecker <fweisbec@...il.com>,
LAK <linux-arm-kernel@...ts.infradead.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
preeti@...ux.vnet.ibm.com,
LAK <linux-arm-kernel@...ts.infradead.org>,
"len.brown@...el.com" <len.brown@...el.com>
Subject: questions of cpuidle
Sorry for a idiot of cpuidle.
I just find few cpu set TIMER_STOP on cpuidle, like omap4 and big.Little
driver. Does that mean other ARM cpu or x86 cpu can get the timer
interrupt in cpuidle?
If the timer stopped during cpuidle, does that means at least one cpu
cann't get into deep c-state since system need a cpu to wake up other
deep c-state cpu? Or sth I missed?
If the cpu stopped the interrupt during deep c-state and without
monitor/mwait support, which kind of ipi can wake the cpu? I mean like a
x86 cpu, APIC stopped in c3 mode, but actually ipi send via apic bus. So
I don't know which ipi work?
--
Thanks
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists