linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Emulating i486 on i386 (was: TSCs are a no-no on i386)
Date: Thu, 31 Jul 2003 13:38:39 +0200	[thread overview]
Message-ID: <20030731113838.GU1873@lug-owl.de> (raw)
In-Reply-To: <20030731071719.GA26249@alpha.home.local>

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

On Thu, 2003-07-31 09:17:19 +0200, Willy Tarreau <willy@w.ods.org>
wrote in message <20030731071719.GA26249@alpha.home.local>:
> On Thu, Jul 31, 2003 at 08:22:52AM +0200, Jan-Benedict Glaw wrote:
> > > The 486 emlation patch for 386 is the way to still allow 386's to run 
> > > Debian.
> > 
> > Okay, I'll have a look at it. Where's the 2.6.x version?
> 
> It doesn't exist, but could certainly easily be ported from 2.4.

> So to resume, everything can be done through emulation, but that's probably
> not what we want as a standard for performance reasons. When I have time, I
> may port it to 2.6, but that's not no my priority list.

Thanks for that. In the meantime, I've started to give a try to the
userspace version (using a LD_PRELOAD lib). My current Problem:

amtus:~/sigill_catcher# LD_PRELOAD=./libsigill.so ls
sigill.c:_init():69: sigill started, sigaction() = 0
build.sh  intercept.h  libsigill.so  run.sh  sigill.c  sigill.o
amtus:~/sigill_catcher# LD_PRELOAD=./libsigill.so apt-get update
Illegal instruction

See? It's loaded at the "ls" call, but it seems to be not loaded for
apt-get.

I've tried to put the lib's name into /etc/ld.so.preload, but it seems
it's never loaded then (for apt-get, ls is doing fine...):

amtus:~/sigill_catcher# cat /etc/ld.so.preload 
sigill.c:_init():69: sigill started, sigaction() = 0
/root/sigill_catcher/libsigill.so
amtus:~/sigill_catcher# apt-get update
Illegal instruction

Where's the difference? Seems I don't know enough about ld.so...
Any useful hints for me?

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-31 11:38 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 13:56 TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-30 14:18 ` Maciej W. Rozycki
2003-07-30 14:44   ` Jan-Benedict Glaw
2003-07-30 16:58 ` Matthew Garrett
2003-07-30 17:19   ` Alan Cox
2003-07-30 18:10 ` Adrian Bunk
2003-07-30 18:30   ` Mike Fedyk
2003-07-30 18:45     ` Adrian Bunk
2003-07-30 20:01       ` Alan Cox
2003-07-30 20:33         ` Jan-Benedict Glaw
2003-07-30 22:19           ` J.A. Magallon
2003-07-31  6:11             ` Jan-Benedict Glaw
2003-07-30 23:05           ` Alan Cox
2003-07-31 11:11             ` Richard B. Johnson
2003-07-31 11:26               ` Emulating i486+ insn on i386 (was: TSCs are a no-no on i386) Jan-Benedict Glaw
2003-07-31 11:41             ` TSCs are a no-no on i386 Jan-Benedict Glaw
2003-07-31  0:22           ` Adrian Bunk
2003-07-31  6:22             ` Jan-Benedict Glaw
2003-07-31  7:17               ` Willy Tarreau
2003-07-31 11:38                 ` Jan-Benedict Glaw [this message]
2003-07-31 11:51                   ` Emulating i486 on i386 (was: TSCs are a no-no on i386) Alan Cox
2003-07-31 12:14                     ` Jan-Benedict Glaw
2003-07-31 13:01                       ` Jan-Benedict Glaw
2003-07-31 15:09                         ` Martin Schlemmer
2003-07-31 15:33                           ` Jan-Benedict Glaw
2003-08-01  5:37                             ` Martin Schlemmer
2003-07-31 15:12                     ` Jamie Lokier
2003-07-31 15:32                       ` Jan-Benedict Glaw
2003-07-31 15:07                 ` TSCs are a no-no on i386 Jamie Lokier
2003-07-31 15:23                   ` Willy Tarreau
2003-07-31 15:50                   ` Richard B. Johnson
2003-07-31 16:24                     ` Jan-Benedict Glaw
2003-08-06 11:08         ` Pavel Machek
2003-08-06 14:33           ` Maciej W. Rozycki
2003-07-30 20:28       ` Jan-Benedict Glaw
2003-07-30 21:50         ` Petr Vandrovec
2003-07-30 23:10           ` Alan Cox
2003-07-31 15:10             ` Jamie Lokier
2003-07-31 16:01               ` Alan Cox
2003-07-31 18:37                 ` Jamie Lokier
2003-07-31 19:10                   ` Alan Cox
2003-07-31  6:29           ` Jan-Benedict Glaw
2003-07-30 20:27   ` Jan-Benedict Glaw
     [not found] <f41P.374.9@gated-at.bofh.it>
     [not found] ` <f4bw.3eu.13@gated-at.bofh.it>
     [not found]   ` <f5Az.4tG.3@gated-at.bofh.it>
     [not found]     ` <f5TZ.4Hq.11@gated-at.bofh.it>
     [not found]       ` <f9uz.Ll.5@gated-at.bofh.it>
     [not found]         ` <ff6X.6qi.3@gated-at.bofh.it>
     [not found]           ` <ffTk.734.15@gated-at.bofh.it>
     [not found]             ` <fk6A.241.7@gated-at.bofh.it>
     [not found]               ` <fkgp.2aL.29@gated-at.bofh.it>
     [not found]                 ` <fnnW.4QQ.43@gated-at.bofh.it>
     [not found]                   ` <fnQP.5bE.5@gated-at.bofh.it>
2003-07-31 17:35                     ` Emulating i486 on i386 (was: TSCs are a no-no on i386) Ben Pfaff

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=20030731113838.GU1873@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --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;
as well as URLs for NNTP newsgroup(s).