From: Alejandro Colomar <alx@kernel.org>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] cpuid.4: note which CPUs don't support CPUID and what happens
Date: Fri, 5 Jan 2024 00:27:45 +0100 [thread overview]
Message-ID: <ZZc-8e-9ul4FiXS_@debian> (raw)
In-Reply-To: <kyyfpi3qhcyvxvj6jhevlx5m3st4hufo6f4xbqz45wmzpe5fgr@tarta.nabijaczleweli.xyz>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Hi,
On Thu, Jan 04, 2024 at 11:31:21PM +0100, наб wrote:
> "Early 486" comes from an uncited wikipedia table, added in
> https://en.wikipedia.org/w/index.php?title=CPUID&diff=prev&oldid=592047209
> https://en.wikipedia.org/w/index.php?title=CPUID&diff=prev&oldid=592047978
> but I spot-checked the rest of the table accurate to CPUs in my house
> (the oldest of which is an original Celeron, so no 486),
> and "early 486" is better than "early x86" which can mean anything.
>
> This does leave earlier x86 unmentioned,
> but Linux hasn't targeted those in over a decade,
> so they're out of scope anyway.
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Patch applied. Thanks!
Have a lovely day,
Alex
> ---
> man4/cpuid.4 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/man4/cpuid.4 b/man4/cpuid.4
> index bd883e6d3..0b38fabe3 100644
> --- a/man4/cpuid.4
> +++ b/man4/cpuid.4
> @@ -69,7 +69,9 @@ .SH NOTES
> There is no support for CPUID functions that require additional
> input registers.
> .P
> -Very old x86 CPUs don't support CPUID.
> +Early i486 CPUs do not support the CPUID instruction;
> +.\" arch/x86/kernel/cpuid.c cpuid_open()
> +opening this device for those CPUs fails with EIO.
> .SH SEE ALSO
> .BR cpuid (1)
> .P
> --
> 2.39.2
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-04 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 22:31 [PATCH] cpuid.4: note which CPUs don't support CPUID and what happens наб
2024-01-04 23:27 ` Alejandro Colomar [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=ZZc-8e-9ul4FiXS_@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).