| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090401114146.GS11935@one.firstfloor.org> Date: Wed, 1 Apr 2009 13:41:46 +0200 From: Andi Kleen <andi@...stfloor.org> To: Arun R Bharadwaj <arun@...ux.vnet.ibm.com> Cc: linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org, a.p.zijlstra@...llo.nl, ego@...ibm.com, tglx@...utronix.de, mingo@...e.hu, andi@...stfloor.org, venkatesh.pallipadi@...el.com, vatsa@...ux.vnet.ibm.com, arjan@...radead.org, svaidy@...ux.vnet.ibm.com Subject: Re: [v4 RFC PATCH 1/4] timers: Framework for identifying pinned timers On Wed, Apr 01, 2009 at 05:02:58PM +0530, Arun R Bharadwaj wrote: > * Arun R Bharadwaj <arun@...ux.vnet.ibm.com> [2009-04-01 17:01:28]: > > This patch creates a new framework for identifying cpu-pinned timers > and hrtimers. > > > This framework is needed because pinned timers are expected to fire on > the same CPU on which they are queued. So it is essential to identify > these and not migrate them, in case there are any. How would that interact with add_timer_on()? You currently only support the current CPU, don't you? e.g. the new tip x86 machine check polling code relies on add_timer_on staying on that CPU. -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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