From: Len Brown <lenb@kernel.org>
To: x86@kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2 v2] speeding up cpu_up()
Date: Fri, 8 May 2015 02:37:53 -0400 [thread overview]
Message-ID: <1431067075-11449-1-git-send-email-lenb@kernel.org> (raw)
Thanks for testing, Aravind, Borislav,
I went with Ingo's suggestion to made this a quirk.
However, I went with a white-list instead of a black-list,
because fewer comparisons are needed for modern processors.
Families are added infrequently, and finally, we get the option
to stick something other than 0 in the table if it we need to.
Let me know if I got the AMD family #'s right.
thanks,
-Len Brown, Intel Open Source Technology Center
next reply other threads:[~2015-05-08 6:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 6:37 Len Brown [this message]
2015-05-08 6:37 ` [PATCH 1/2] x86: replace cpu_up hard-coded mdelay with variable udelay Len Brown
2015-05-08 6:37 ` [PATCH 2/2] x86: speed cpu_up by quirking cpu_init_udelay Len Brown
2015-05-08 7:51 ` Ingo Molnar
2015-05-08 8:23 ` Borislav Petkov
2015-05-08 8:32 ` Borislav Petkov
2015-05-08 18:15 ` Len Brown
2015-05-08 18:27 ` Borislav Petkov
2015-05-09 7:22 ` Ingo Molnar
2015-05-09 7:24 ` Ingo Molnar
2015-05-09 8:04 ` 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=1431067075-11449-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).