From: Simon Arlott <simon@fire.lp0.eu>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Claas Langbehn <claas@rootdir.de>,
LKML <linux-kernel@vger.kernel.org>,
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 23:16:58 +0100 [thread overview]
Message-ID: <464CD45A.6090902@simon.arlott.org.uk> (raw)
In-Reply-To: <464CB7CC.8030706@zytor.com>
On 17/05/07 21:15, H. Peter Anvin wrote:
> Simon Arlott wrote:
>> 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.
>>
>
> CX8 isn't cmpxchg; it's cmpxchg8b.
Ok, but I have CONFIG_X86_CMPXCHG64=y too.
--
Simon Arlott
next prev parent reply other threads:[~2007-05-17 22:17 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
2007-05-17 20:15 ` H. Peter Anvin
2007-05-17 22:16 ` Simon Arlott [this message]
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=464CD45A.6090902@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.