linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: x86@kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2 v3] speed up cpu_up()
Date: Fri,  8 May 2015 13:48:05 -0400	[thread overview]
Message-ID: <1431107287-22022-1-git-send-email-lenb@kernel.org> (raw)

Thanks for the feedback, here is a simplifed pair of patches.

I also like the x2apic optimization, since it addresses additional delays.
 -- though we may be able to optimize those in the non-x2apic case too.

thanks,
Len Brown, Intel Open Source Technology Center

             reply	other threads:[~2015-05-08 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 17:48 Len Brown [this message]
2015-05-08 17:48 ` [PATCH 1/2] x86: Add cmdline "cpu_init_udelay=N" to specify cpu_up() delay Len Brown
2015-05-08 17:48   ` [PATCH 2/2] x86: remove 10ms delay from cpu_up() on modern processors Len Brown
2015-05-08 20:43 ` [PATCH 0/2 v3] speed up cpu_up() Rafael J. Wysocki
2015-05-10 10:44 ` Ingo Molnar

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=1431107287-22022-1-git-send-email-lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).