From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: linux-tip-commits@vger.kernel.org, david@saggiorato.net,
brgerst@gmail.com, peterz@infradead.org, dave@sr71.net,
dvlasenk@redhat.com, mingo@kernel.org, jpoimboe@redhat.com,
hpa@zytor.com, luto@kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [tip:x86/urgent] x86/boot: Initialize FPU and X86_FEATURE_ALWAYS even if we don't have CPUID
Date: Fri, 30 Sep 2016 17:15:38 +0200 [thread overview]
Message-ID: <20160930151538.GA14423@nazgul.tnic> (raw)
In-Reply-To: <tip-05fb3c199bb09f5b85de56cc3ede194ac95c5e1f@git.kernel.org>
On Fri, Sep 30, 2016 at 05:06:46AM -0700, tip-bot for Andy Lutomirski wrote:
> Commit-ID: 05fb3c199bb09f5b85de56cc3ede194ac95c5e1f
> Gitweb: http://git.kernel.org/tip/05fb3c199bb09f5b85de56cc3ede194ac95c5e1f
> Author: Andy Lutomirski <luto@kernel.org>
> AuthorDate: Wed, 28 Sep 2016 16:06:33 -0700
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitDate: Fri, 30 Sep 2016 13:53:04 +0200
>
> x86/boot: Initialize FPU and X86_FEATURE_ALWAYS even if we don't have CPUID
>
> Otherwise arch_task_struct_size == 0 and we die. While we're at it,
> set X86_FEATURE_ALWAYS, too.
...
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index 809eda0..bcc9ccc 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -804,21 +804,20 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
> identify_cpu_without_cpuid(c);
>
> /* cyrix could have cpuid enabled via c_identify()*/
> - if (!have_cpuid_p())
> - return;
> + if (have_cpuid_p()) {
Let's make it even simpler:
---
From: Borislav Petkov <bp@suse.de>
Date: Fri, 30 Sep 2016 17:08:10 +0200
Subject: [PATCH] x86/boot: Streamline CPUID check conditional
We have now:
if (!have_cpuid_p())
...
if (have_cpuid_p())
...
Turn it into a good, ole if-else conditional which is much more
readable.
No functionality change.
Signed-off-by: Borislav Petkov <bp@suse.de>
---
arch/x86/kernel/cpu/common.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index 9bd910a7dd0a..0a6fa6174ed8 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -800,9 +800,6 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
memset(&c->x86_capability, 0, sizeof c->x86_capability);
c->extended_cpuid_level = 0;
- if (!have_cpuid_p())
- identify_cpu_without_cpuid(c);
-
/* cyrix could have cpuid enabled via c_identify()*/
if (have_cpuid_p()) {
cpu_detect(c);
@@ -817,6 +814,8 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
if (this_cpu->c_bsp_init)
this_cpu->c_bsp_init(c);
+ } else {
+ identify_cpu_without_cpuid(c);
}
setup_force_cpu_cap(X86_FEATURE_ALWAYS);
--
2.8.4
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
prev parent reply other threads:[~2016-09-30 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 23:06 [RFC PATCH] " Andy Lutomirski
2016-09-30 8:32 ` David Saggiorato
2016-09-30 12:06 ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2016-09-30 15:15 ` Borislav Petkov [this message]
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=20160930151538.GA14423@nazgul.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave@sr71.net \
--cc=david@saggiorato.net \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®