On Tue, Apr 21, 2015 at 11:07 PM, Ingo Molnar wrote:
>
> * Paul Gortmaker wrote:
>> 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 thi
* Paul Gortmaker wrote:
> On Sat, Apr 18, 2015 at 8:53 PM, Len Brown wrote:
> > From: Len Brown
> >
>
> [...]
>
> > 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_M
On Sat, Apr 18, 2015 at 8:53 PM, Len Brown wrote:
> From: Len Brown
>
[...]
> 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
* Brown, Len wrote:
> > What's the cutoff for 'modern hardware' - which CPUs stopped requiring
> > the delay?
>
> This is the topic of ongoing research, and I'm not ready to send
> the patch setting a new default until I've heard back from a few more HW
> people.
>
> Every system I've tested
> What's the cutoff for 'modern hardware' - which CPUs stopped requiring
> the delay?
This is the topic of ongoing research, and I'm not ready to send
the patch setting a new default until I've heard back from a few more HW people.
Every system I've tested appears to work with delay 0.
Were I to
* Len Brown wrote:
> +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
6 matches
Mail list logo
