From: Simon Arlott <simon@fire.lp0.eu>
To: Claas Langbehn <claas@rootdir.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
hpa@zytor.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: This kernel requires the following features not present on the CPU... (on a VIA C7 CPU)
Date: Thu, 17 May 2007 21:12:22 +0100 [thread overview]
Message-ID: <464CB726.6090201@simon.arlott.org.uk> (raw)
In-Reply-To: <464C4A22.7040709@rootdir.de>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
On 17/05/07 13:27, Claas Langbehn wrote:
> I have got a VIA EPIA EX15000G Mini-ITX mainboard with a C7 VIA Esther
> processor (1500MHz).
I have Jetway's J7F4K with the same CPU.
> C7 CMPXCHG8 - enable/disable (Disable to install windows NT 4.0) and
> C7 No Execute (NX) - enable/disable
Without those options in the BIOS setup.
> > This kernel requires the following features not present on the CPU:
> > 0:8
> I attached a cpuinfo.txt. When the two flags are disabled, cx8 and nx
> are not listed there.
I don't have cx8, but I do have nx (which is unused because I have PAE
disabled...).
On 17/05/07 19:33, H. Peter Anvin wrote:
>> Claas Langbehn wrote:
>> Would it be possible to override the BIOS settings of cx8 and nx and
>> > activate it with linux anyway?
>> > The CPU supports it and I don't see any reason to disable it.
>> >
>
> Yes, that code is already in the git.newsetup tree.
Is it automatic? I have CONFIG_X86_CMPXCHG=y without cx8 showing in
cpuinfo, and it appears to work fine.
Will your changes needlessly prevent the kernel running? Would I be
right in thinking that the kernel is successfully using cmpxchg even
though it's considered disabled? I realise people compile kernels
for the wrong CPU but preventing them working when it's been chosen
correctly seems wrong.
processor : 0
vendor_id : CentaurHauls
cpu family : 6
model : 10
model name : VIA Esther processor 1500MHz
stepping : 9
cpu MHz : 800.000 (cpufreq)
cache size : 128 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce apic sep mtrr pge cmov pat clflush acpi mmx fxsr sse sse2 tm nx pni est tm2 rng rng_en ace ace_en ace2 ace2_en phe phe_en pmm pmm_en
bogomips : 1601.18
clflush size : 64
--
Simon Arlott
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 10555 bytes --]
next prev parent reply other threads:[~2007-05-17 20:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 12:27 This kernel requires the following features not present on the CPU... (on a VIA C7 CPU) Claas Langbehn
2007-05-17 15:24 ` Alan Cox
2007-05-17 15:41 ` Claas Langbehn
2007-05-17 18:33 ` H. Peter Anvin
2007-05-18 11:17 ` Claas Langbehn
2007-05-17 20:12 ` Simon Arlott [this message]
2007-05-17 20:15 ` H. Peter Anvin
2007-05-17 22:16 ` Simon Arlott
2007-05-17 22:19 ` H. Peter Anvin
2007-05-18 6:24 ` Jan Engelhardt
2007-05-17 20:13 ` Simon Arlott
-- strict thread matches above, loose matches on Subject: below --
2007-05-20 1:30 Artur Kedzierski
2007-05-22 6:55 ` Claas Langbehn
2007-05-22 15:53 ` Christian Volkmann
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=464CB726.6090201@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=akpm@linux-foundation.org \
--cc=claas@rootdir.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.