All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Len Brown <lenb@kernel.org>
Cc: x86@kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 0/1] speeding up cpu_up()
Date: Mon, 20 Apr 2015 09:15:56 +0200	[thread overview]
Message-ID: <20150420071556.GB14315@gmail.com> (raw)
In-Reply-To: <1429404795-23260-1-git-send-email-lenb@kernel.org>


* Len Brown <lenb@kernel.org> wrote:

> The following patch...
> 
> [PATCH 1/1] x86: replace cpu_up hard-coded mdelay with variable
> 
> enables reducing cpu_up() time by 10ms on modern systems.
> 
> This means that for every processor in the system,
> boot-time and resume-time can be reduced by 10ms per-processor.
> 
> Once this patch is accepted, I'll send a subsequent patch
> to update the default delay, as appropriate.
> 
> thanks,
> Len Brown, Intel Open Source Technology Center

So instead of playing games with an ancient delay, I'd suggest we 
install the 10 msec INIT assertion wait as a platform quirk instead, 
and activate it for all CPUs/systems that we think might need it, with 
a sufficiently robust and future-proof quirk cutoff condition.

New systems won't have the quirk active and thus won't have to have 
this delay configurable either.

Thanks,

	Ingo

  parent reply	other threads:[~2015-04-20  7:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19  0:53 [PATCH 0/1] speeding up cpu_up() Len Brown
2015-04-19  0:53 ` [PATCH 1/1] x86: replace cpu_up hard-coded mdelay with variable Len Brown
2015-04-20  7:13   ` Ingo Molnar
2015-04-20 12:37     ` Brown, Len
2015-04-20 17:45       ` Ingo Molnar
2015-04-22  5:40   ` Paul Gortmaker
2015-04-22  6:07     ` Ingo Molnar
2015-05-01 21:02       ` Len Brown
2015-04-20  7:15 ` Ingo Molnar [this message]
2015-05-01 21:42   ` [PATCH 0/1] speeding up cpu_up() Len Brown
2015-05-01 22:47     ` Borislav Petkov
2015-05-02  0:42       ` Aravind Gopalakrishnan
2015-05-03 16:13         ` Aravind Gopalakrishnan
2015-05-04 22:45           ` Aravind Gopalakrishnan
2015-05-05  7:15             ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150420071556.GB14315@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.