From: Mikael Pettersson <mikpe@it.uu.se>
To: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
venkatesh.pallipadi@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.26-rc1 lies about PAT not being available
Date: Tue, 6 May 2008 10:18:01 +0200 [thread overview]
Message-ID: <18464.5177.649312.999486@harpo.it.uu.se> (raw)
Booting 2.6.26-rc1 on an old Coppermine PIII, I'm greeted with:
>Linux version 2.6.26-rc1 (mikpe@dryhop) (gcc version 4.2.3) #1 Mon May 5 21:49:49 CEST 2008
>BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009c000 (usable)
> BIOS-e820: 000000000009c000 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000002ffec000 (usable)
> BIOS-e820: 000000002ffec000 - 000000002ffef000 (ACPI data)
> BIOS-e820: 000000002ffef000 - 000000002ffff000 (reserved)
> BIOS-e820: 000000002ffff000 - 0000000030000000 (ACPI NVS)
> BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
>CPU and/or kernel does not support PAT.
I know about Intel's PAT erratum (only 4 PAT entries work) and
understand that the kernel might not want to use a half-broken
PAT implementation, but the statement above is blatantly false:
the kernel IS built with PAT support and the CPU DOES have
(half-broken) PAT HW support as /proc/cpuinfo from earlier kernels
confirms.
arch/x86/kernel/cpu/common.c unconditionally disables PAT and
then reenables it for certain vendor/family/model combinations.(*)
Then mm/pat.c comes along, finds !cpu_has_pat, and prints the
bogus message above.
IMO, it would be a lot nicer if common.c printed a warning when
it disables PAT due to the erratum, then the printk() in pat.c
could be something like "PAT support absent or disabled".
(*) common.c enables PAT for all Intel family 15 CPUs. Is that
correct? I don't have the spec updates in front of me, but I
seem to recall the PAT erratum existed also in early P4s.
/Mikael
next reply other threads:[~2008-05-06 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 8:18 Mikael Pettersson [this message]
2008-05-06 11:48 ` Ingo Molnar
2008-05-06 15:17 ` H. Peter Anvin
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=18464.5177.649312.999486@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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®