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
| ||
|
Date: Mon, 6 Feb 2012 18:03:15 -0800 From: Venki Pallipadi <venki@...gle.com> To: "H. Peter Anvin" <hpa@...or.com> Cc: David Daney <ddaney.cavm@...il.com>, Peter Zijlstra <peterz@...radead.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Suresh Siddha <suresh.b.siddha@...el.com>, Aaron Durbin <adurbin@...gle.com>, Paul Turner <pjt@...gle.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [RFC] Extend mwait idle to optimize away IPIs when possible On Mon, Feb 6, 2012 at 5:45 PM, H. Peter Anvin <hpa@...or.com> wrote: > On 02/06/2012 05:34 PM, David Daney wrote: >> >> >> Well I don't know that part. The gist of my comment was to get rid of an >> unneeded new config variable. >> >> If this works just as well for 32-bit, then by all means do it there too. >> >> In any event, I think you want the kernel to automatically do it if the >> CPU is capable, and not have a manual config setting you have to fiddle >> with. >> > > If this is a transitional thing then it might justify it. > There is nothing specific to 64 bit here. Its just that I had only tested this on 64 bit right now and wanted to get early feedback. So, in the spirit of RFC, I sent this out as x86_64 only for the time being. If and when this will be sent for inclusion, this will should work on both 32 bit and 64 bit on x86. Though we will need a config option to not add any run time overhead in generic code (and to not have #ifdef CONFIG_X86 in kernel/). Thanks, Venki -- 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