mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	John Ogness <john.ogness@linutronix.de>,
	x86@kernel.org, x86-cpuid@lists.linux.dev,
	LKML <linux-kernel@vger.kernel.org>
Subject: [x86/cpuid] Question regarding historic leaf 0x80000000 code
Date: Thu, 20 Mar 2025 20:33:16 +0100	[thread overview]
Message-ID: <Z9xtfC5pL-g4LYvK@lx-t490> (raw)

Hi hpa,

As you probably know by now, we're working on a centralized "CPUID table"
data model, on top of the cleanups at:

    https://lore.kernel.org/x86-cpuid/20250304085152.51092-1-darwi@linutronix.de
    https://lore.kernel.org/x86-cpuid/20250319122137.4004-1-darwi@linutronix.de
    https://lore.kernel.org/x86-cpuid/20250312143738.458507-1-darwi@linutronix.de

The idea is to remove all the direct CPUID queries from the x86 code, and
access a pre-filled table instead (with caveats outside the scope of this
question.)

While changing the CPUID queries one by one, I've stumbled with:

    => arch/x86/kernel/cpu/common.c
    void get_cpu_cap(struct cpuinfo_x86 *c)
    {
	...
	/* AMD-defined flags: level 0x80000001 */
	eax = cpuid_eax(0x80000000);
	c->extended_cpuid_level = eax;

	if ((eax & 0xffff0000) == 0x80000000) {
		if (eax >= 0x80000001) {
			cpuid(0x80000001, &eax, &ebx, &ecx, &edx);

			c->x86_capability[CPUID_8000_0001_ECX] = ecx;
			c->x86_capability[CPUID_8000_0001_EDX] = edx;
		}
	}
	...
    }

You've contributed that snippet here:

    https://git.kernel.org/pub/scm/linux/kernel/git/history/history.git/commit/?h=2.4.0-test11pre5&id=67ad24e6d39c3

Do you remember what was the rationale for the "if (eax & 0xffff0000) ==
0x80000000" check?

You've also contriubted a similar check to head_32.S:

    https://lore.kernel.org/r/1258154897-6770-2-git-send-email-hpa@zytor.com

    /* Check if extended functions are implemented */
    movl $0x80000000, %eax
    cpuid
    /* Value must be in the range 0x80000001 to 0x8000ffff */
    subl $0x80000001, %eax
    cmpl $(0x8000ffff-0x80000001), %eax
    ja .Lenable_paging

So I would assume, it would be safe to have a similar check in our
centralized "system CPUID table" scanner.

In all cases, if you know more details, it would be great to know, so
that I add it in the centralized CPUID table patch queue changelog (in a
separate patch.)

Thanks a lot!

--
Ahmed S. Darwish
Linutronix GmbH

             reply	other threads:[~2025-03-20 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 19:33 Ahmed S. Darwish [this message]
2025-03-20 19:42 ` Andrew Cooper
2025-03-20 19:56   ` Ahmed S. Darwish

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=Z9xtfC5pL-g4LYvK@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=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®