public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Osuchowski <adwol@zonk.pl>
To: linux-kernel@vger.kernel.org
Subject: Is 386 processor still supported?
Date: Thu, 8 Jan 2009 13:03:38 +0100	[thread overview]
Message-ID: <20090108120338.6b8b4567@zonk.pl> (raw)

Recently, I found such piece of code in kernel 2.6.28 compiled for 386
processor:

# grep M386 .config
CONFIG_M386=y
# objdump -d vmlinux | grep -A11 '<_spin_lock>:'
c0321827 <_spin_lock>:
c0321827:	89 e2                	mov    %esp,%edx
c0321829:	81 e2 00 f0 ff ff    	and    $0xfffff000,%edx
c032182f:	ff 42 14             	incl   0x14(%edx)
c0321832:	ba 00 01 00 00       	mov    $0x100,%edx
c0321837:	f0 66 0f c1 10       	lock xadd %dx,(%eax)
c032183c:	38 f2                	cmp    %dh,%dl
c032183e:	74 06                	je     c0321846 <_spin_lock+0x1f>
c0321840:	f3 90                	pause  
c0321842:	8a 10                	mov    (%eax),%dl
c0321844:	eb f6                	jmp    c032183c <_spin_lock+0x15>
c0321846:	c3                   	ret    

But there is no xadd instruction on 386 processors. It is available on
486+ only. I have no chance to run this kernel on real 386 box, so I can't
check it in practice, but I think it will not run.

It is not compiler problem because it is explicitly written in assembly
in __raw_spin_lock() function (include/asm-x86/spinlock.h) and there is
no alternative code depending on CONFIG_M386.

Regards.

             reply	other threads:[~2009-01-08 12:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 12:03 Adam Osuchowski [this message]
2009-01-08 13:05 ` Is 386 processor still supported? 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
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=20090108120338.6b8b4567@zonk.pl \
    --to=adwol@zonk.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox