linux-kernel - Re: [PATCH 1/1] x86: replace cpu_up hard-coded mdelay with variable

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Apr 2015 08:07:34 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Len Brown <lenb@...nel.org>, X86 ML <x86@...nel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>
Subject: Re: [PATCH 1/1] x86: replace cpu_up hard-coded mdelay with variable


* Paul Gortmaker <paul.gortmaker@...driver.com> wrote:

> On Sat, Apr 18, 2015 at 8:53 PM, Len Brown <lenb@...nel.org> wrote:
> > From: Len Brown <len.brown@...el.com>
> >
> 
> [...]
> 
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index b7d31ca..d2a91da 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -884,6 +884,21 @@ config SCHED_MC
> >           making when dealing with multi-core CPU chips at a cost of slightly
> >           increased overhead in some places. If unsure say N here.
> >
> > +config X86_INIT_MDELAY
> > +       int "Milliseconds to wait to de-assert INIT upon CPU startup" if SMP
> > +       range 0 10
> > +       default "10"
> > +       ---help---
> > +         This allows you to specify how long the BSP will delay
> > +         between asserting INIT and de-asserting INIT when starting another CPU.
> > +         This delay is paid on each cpu-online operation, including boot-time,
> > +         resume from suspend, and resume from hibernate.  The the value of
> 
> Happened to notice a 2x "The the..." when I came across this in 
> linux-next today and was reading the help out of curiousity...

Len, this commit isn't in a permanent Git tree yet, right? We want to 
do this through the x86 tree, and along the suggestions I made.

Thanks,

	Ingo
--
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/