From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
mingo@redhat.com, dave.hansen@linux.intel.com, bp@alien8.de,
hpa@zytor.com, tglx@kernel.org, sohil.mehta@intel.com,
andrew.cooper3@citrix.com, linux-kernel@vger.kernel.org,
x86@kernel.org, john.ogness@linutronix.de, ludloff@gmail.com,
x86-cpuid@lists.linux.dev
Subject: Re: [PATCH v2 2/2] x86/cpuid: Update bitfields to x86-cpuid-db v3.1
Date: Mon, 8 Jun 2026 11:55:39 +0200 [thread overview]
Message-ID: <aiaRm2CWtOANhAR-@lx-t490> (raw)
In-Reply-To: <aiaGHc8V4tLK-Rn4@wieczorr-mobl1.localdomain>
On Mon, 08 Jun 2026, Maciej Wieczor-Retman wrote:
>
> I see the patches were already merged to tip but perhaps in the next release we
> could put the character limit information in a comment somewhere in the
> tools/arch/x86/kcpuid?
>
Nah, please, it's not worthwhile.
That's the first time we hit the limit, and that's with a CPUID database of
64 leaves and 1104 bitfields.
Thanks,
Ahmed
prev parent reply other threads:[~2026-06-08 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 17:10 [PATCH v2 0/2] x86/cpuid: kcpuid: v3.1 x86-cpuid-db update with fixes Maciej Wieczor-Retman
2026-06-03 17:10 ` [PATCH v2 1/2] tools/x86/kcpuid: Update bitfields to x86-cpuid-db v3.1 Maciej Wieczor-Retman
2026-06-03 17:10 ` [PATCH v2 2/2] x86/cpuid: " Maciej Wieczor-Retman
2026-06-04 7:41 ` Ingo Molnar
2026-06-08 6:34 ` Ahmed S. Darwish
2026-06-08 9:22 ` Maciej Wieczor-Retman
2026-06-08 9:55 ` Ahmed S. Darwish [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=aiaRm2CWtOANhAR-@lx-t490 \
--to=darwi@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ludloff@gmail.com \
--cc=m.wieczorretman@pm.me \
--cc=maciej.wieczor-retman@intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.org \
--cc=x86-cpuid@lists.linux.dev \
--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