From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Thomas Gleixner <tglx@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"H . Peter Anvin" <hpa@zytor.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
bpf@vger.kernel.org, kasan-dev@googlegroups.com,
linux-mm@kvack.org, kernel-team@meta.com
Subject: Re: [PATCH v2 2/5] x86/cpu: Initialize boot CPU cpuinfo defaults early
Date: Tue, 15 Sep 2026 09:34:42 -0700 [thread overview]
Message-ID: <a6f41d17-62f0-4ba6-a8f0-bc18866d2784@linux.dev> (raw)
In-Reply-To: <20260915023115.GFaqit8zcWHGkAdHD5@fat_crate.local>
On 9/14/26 7:31 PM, Borislav Petkov wrote:
> On Fri, Aug 14, 2026 at 04:51:31PM -0700, Ihor Solodrai wrote:
>> early_identify_cpu() clears the capability array, the CPUID table and
>> extended_cpuid_level, but the architectural defaults for the rest of
>> struct cpuinfo_x86 are set only later, in identify_cpu().
>
> And I would've stopped here. I don't think we care too much about a CPU which
> doesn't enumerate CLFLUSH. Or is there an aspect I am missing.
>
> I mean, you can say something along the lines that now things like
> ->x86_cache_alignment are more correct but I don't think you need to go that
> much into detail.
Ok. I don't think you're missing anything.
Should I respin with fixed up messages?
>
>> [...]
>
next prev parent reply other threads:[~2026-09-15 16:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 23:51 [PATCH v2 0/5] x86/cpu: Refactor identify_cpu() Ihor Solodrai
2026-08-14 23:51 ` [PATCH v2 1/5] x86/cpu: Factor init_cpu_info() out of identify_cpu() Ihor Solodrai
2026-09-10 2:32 ` Borislav Petkov
2026-08-14 23:51 ` [PATCH v2 2/5] x86/cpu: Initialize boot CPU cpuinfo defaults early Ihor Solodrai
2026-09-15 2:31 ` Borislav Petkov
2026-09-15 16:34 ` Ihor Solodrai [this message]
2026-09-15 23:44 ` Borislav Petkov
2026-08-14 23:51 ` [PATCH v2 3/5] x86/cpu: Inline generic_identify() into identify_cpu() Ihor Solodrai
2026-08-14 23:51 ` [PATCH v2 4/5] x86/cpu: Move 32-bit SEP setup " Ihor Solodrai
2026-08-17 12:14 ` Nikolay Borisov
2026-08-14 23:51 ` [PATCH v2 5/5] x86/cpu: Don't transiently clear the boot CPU's capabilities Ihor Solodrai
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=a6f41d17-62f0-4ba6-a8f0-bc18866d2784@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kasan-dev@googlegroups.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@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
all inboxes | Powered by JetHome®