Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1562091 > unrolled thread
| Started by | Andy Lutomirski <luto@kernel.org> |
|---|---|
| First post | 2017-01-18 20:20 +0100 |
| Last post | 2017-01-25 12:50 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
[PATCH v2 3/6] x86/cpu: Re-apply forced caps every time cpu caps are re-read Andy Lutomirski <luto@kernel.org> - 2017-01-18 20:20 +0100
Re: [PATCH v2 3/6] x86/cpu: Re-apply forced caps every time cpu caps are re-read Borislav Petkov <bp@alien8.de> - 2017-01-19 12:50 +0100
[tip:x86/fpu] x86/cpu: Re-apply forced caps every time CPU caps are re-read tip-bot for Andy Lutomirski <tipbot@zytor.com> - 2017-01-25 12:50 +0100
| From | Andy Lutomirski <luto@kernel.org> |
|---|---|
| Date | 2017-01-18 20:20 +0100 |
| Subject | [PATCH v2 3/6] x86/cpu: Re-apply forced caps every time cpu caps are re-read |
| Message-ID | <t13W3-83l-45@gated-at.bofh.it> |
Calling get_cpu_cap() will reset a bunch of CPU features. This will cause the system to lose track of force-set and force-cleared featueres in the words that are reset until the end of CPU initialization. This can cause X86_FEATURE_FPU, for example, to change back and forth during boot and potentially confuse CPU setup. To minimize the chance of confusion, re-apply forced caps every time get_cpu_cap() is called. Signed-off-by: Andy Lutomirski <luto@kernel.org> --- arch/x86/kernel/cpu/common.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c index 337eac606f39..8efe6e77f91d 100644 --- a/arch/x86/kernel/cpu/common.c +++ b/arch/x86/kernel/cpu/common.c @@ -757,6 +757,13 @@ void get_cpu_cap(struct cpuinfo_x86 *c) c->x86_capability[CPUID_8000_000A_EDX] = cpuid_edx(0x8000000a); init_scattered_cpuid_features(c); + + /* + * Clear/Set all flags overridden by options, after probe. + * This needs to happen each time we re-probe, which may happen + * several times during CPU initialization. + */ + apply_forced_caps(c); } static void identify_cpu_without_cpuid(struct cpuinfo_x86 *c) -- 2.9.3
[toc] | [next] | [standalone]
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Date | 2017-01-19 12:50 +0100 |
| Subject | Re: [PATCH v2 3/6] x86/cpu: Re-apply forced caps every time cpu caps are re-read |
| Message-ID | <t1jo6-10B-7@gated-at.bofh.it> |
| In reply to | #1562091 |
On Wed, Jan 18, 2017 at 11:15:39AM -0800, Andy Lutomirski wrote:
> Calling get_cpu_cap() will reset a bunch of CPU features. This will
> cause the system to lose track of force-set and force-cleared
> featueres in the words that are reset until the end of CPU
features
> initialization. This can cause X86_FEATURE_FPU, for example, to
> change back and forth during boot and potentially confuse CPU setup.
>
> To minimize the chance of confusion, re-apply forced caps every time
> get_cpu_cap() is called.
>
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
[toc] | [prev] | [next] | [standalone]
| From | tip-bot for Andy Lutomirski <tipbot@zytor.com> |
|---|---|
| Date | 2017-01-25 12:50 +0100 |
| Subject | [tip:x86/fpu] x86/cpu: Re-apply forced caps every time CPU caps are re-read |
| Message-ID | <t3ufp-1eA-31@gated-at.bofh.it> |
| In reply to | #1562091 |
Commit-ID: 60d3450167433f2d099ce2869dc52dd9e7dc9b29 Gitweb: http://git.kernel.org/tip/60d3450167433f2d099ce2869dc52dd9e7dc9b29 Author: Andy Lutomirski <luto@kernel.org> AuthorDate: Wed, 18 Jan 2017 11:15:39 -0800 Committer: Ingo Molnar <mingo@kernel.org> CommitDate: Wed, 25 Jan 2017 10:12:41 +0100 x86/cpu: Re-apply forced caps every time CPU caps are re-read Calling get_cpu_cap() will reset a bunch of CPU features. This will cause the system to lose track of force-set and force-cleared features in the words that are reset until the end of CPU initialization. This can cause X86_FEATURE_FPU, for example, to change back and forth during boot and potentially confuse CPU setup. To minimize the chance of confusion, re-apply forced caps every time get_cpu_cap() is called. Signed-off-by: Andy Lutomirski <luto@kernel.org> Reviewed-by: Borislav Petkov <bp@suse.de> Cc: Borislav Petkov <bp@alien8.de> Cc: Brian Gerst <brgerst@gmail.com> Cc: Dave Hansen <dave.hansen@linux.intel.com> Cc: Fenghua Yu <fenghua.yu@intel.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Matthew Whitehead <tedheadster@gmail.com> Cc: Oleg Nesterov <oleg@redhat.com> Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Rik van Riel <riel@redhat.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Yu-cheng Yu <yu-cheng.yu@intel.com> Link: http://lkml.kernel.org/r/c817eb373d2c67c2c81413a70fc9b845fa34a37e.1484705016.git.luto@kernel.org Signed-off-by: Ingo Molnar <mingo@kernel.org> --- arch/x86/kernel/cpu/common.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c index 2ea16e0..d09b5ee 100644 --- a/arch/x86/kernel/cpu/common.c +++ b/arch/x86/kernel/cpu/common.c @@ -758,6 +758,13 @@ void get_cpu_cap(struct cpuinfo_x86 *c) c->x86_capability[CPUID_8000_000A_EDX] = cpuid_edx(0x8000000a); init_scattered_cpuid_features(c); + + /* + * Clear/Set all flags overridden by options, after probe. + * This needs to happen each time we re-probe, which may happen + * several times during CPU initialization. + */ + apply_forced_caps(c); } static void identify_cpu_without_cpuid(struct cpuinfo_x86 *c)
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web