From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jiri Kosina <jkosina@suse.cz>, Adam Osuchowski <adwol@zonk.pl>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Nick Piggin <npiggin@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Is 386 processor still supported?
Date: Thu, 8 Jan 2009 17:45:14 +0100 [thread overview]
Message-ID: <20090108164514.GA18409@uranus.ravnborg.org> (raw)
In-Reply-To: <1231424833.11687.452.camel@twins>
On Thu, Jan 08, 2009 at 03:27:13PM +0100, Peter Zijlstra wrote:
> On Thu, 2009-01-08 at 15:21 +0100, Jiri Kosina wrote:
> > On Thu, 8 Jan 2009, Peter Zijlstra wrote:
> >
> > > > Subject: x86: make spinlocks available on machines without xadd insn
> > > > Current kernel wouldn't compile on ancient x86 machines that don't support
> > > > xadd instruction, as ticket spinlocks implementation unconditionally uses
> > > > it.
> > > > On machines without CONFIG_X86_XADD, use old-style byte spinlock
> > > > implementation instead.
> > > afaik we don't support i386-smp and up spinlocks are trivial
> > > preempt_disable() calls.
> >
> > Hmm. Where in Kconfig is SMP for M386 not allowed?
>
> Dunno, kconfig is too much of a jungle for a simple person like me ;-)
Kconfig for x86 does nothing to prevent us from selecting SMP
when we have selected the 386 processor variant.
But then you need to enable the CONFIG_EXPERT(*) option to
select CPU type - which imply you know what you are doing.
(*) Named CONFIG_EMBEDDED for some reason.
Sam
next prev parent reply other threads:[~2009-01-08 16:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 12:03 Is 386 processor still supported? Adam Osuchowski
2009-01-08 13:05 ` Jiri Kosina
2009-01-08 13:24 ` Cyrill Gorcunov
2009-01-08 13:48 ` Jiri Kosina
2009-01-08 14:13 ` Peter Zijlstra
2009-01-08 14:21 ` Jiri Kosina
2009-01-08 14:27 ` Peter Zijlstra
2009-01-08 15:04 ` Alan Cox
2009-01-08 15:10 ` Ingo Molnar
2009-01-13 1:06 ` Maciej W. Rozycki
2009-01-15 12:36 ` Jan-Benedict Glaw
2009-01-15 13:22 ` Maciej W. Rozycki
2009-01-15 13:32 ` Alan Cox
2009-01-15 14:15 ` Maciej W. Rozycki
2009-01-15 14:17 ` Ingo Molnar
2009-01-16 9:00 ` Pavel Machek
2009-01-16 10:13 ` Jan-Benedict Glaw
2009-01-16 11:18 ` Andrey Panin
2009-01-16 13:46 ` Ingo Molnar
2009-01-16 18:17 ` H. Peter Anvin
2009-01-15 14:20 ` Jan-Benedict Glaw
2009-01-15 14:37 ` Bastien ROUCARIES
2009-01-15 14:25 ` Alan Cox
2009-01-15 14:44 ` Maciej W. Rozycki
2009-01-15 20:11 ` H. Peter Anvin
2009-01-15 14:46 ` Jan-Benedict Glaw
2009-01-08 16:45 ` Sam Ravnborg [this message]
2009-01-08 16:27 ` Andi Kleen
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=20090108164514.GA18409@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=adwol@zonk.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=peterz@infradead.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