From: "Jeff V. Merkey" <jmerkey@timpanogas.org>
To: davej@suse.de, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Installing kernel 2.4
Date: Tue, 07 Nov 2000 16:59:34 -0700 [thread overview]
Message-ID: <3A089766.43FD7CC0@timpanogas.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0011072322120.8187-100000@neo.local> <3A089254.397115FE@timpanogas.org> <3A08947C.1161F13C@timpanogas.org>
"Jeff V. Merkey" wrote:
>
> "Jeff V. Merkey" wrote:
> >
> > davej@suse.de wrote:
> > >
> > > > There are tests for all this in the feature flags for intel and
> > > > non-intel CPUs like AMD -- including MTRR settings. All of this could
> > > > be dynamic. Here's some code that does this, and it's similiar to
> > > > NetWare. It detexts CPU type, feature flags, special instructions,
> > > > etc. All of this on x86 could be dynamically detected.
> > >
> > > Detecting the CPU isn't the issue (we already do all this), it's what to
> > > do when you've figured out what the CPU is. Show me code that can
> > > dynamically adjust the alignment of the routines/variables/structs
> > > dependant upon cacheline size.
>
> ftp.timpanogas.org/manos/manos0817.tar.gz
>
> Look in the PE loader -- Microsoft's PE loader can do this since
> everything is RVA based. If you want to take the loader and put it in
> Linux, be my guest. You can even combine mutiple i86 segments all
> compiled under different options (or architectures) and bundle them into
> a single executable file -- not somthing gcc can do today -- even with
> DLL. This code is almost identical to the PE loader used in NT -- with
> one exception, I omit the fs:_THREAD_DLS startup code...
>
> 8)
>
> Jeff
>
> >
> > If the compiler always aligned all functions and data on 16 byte
> > boundries (NetWare)
> > for all i386 code, it would run a lot faster. Cache line alignment
> > could be an option in the loader .... after all, it's hte loader that
> > locates data in memory. If Linux were PE based, relocation logic would
> > be a snap with this model (like NT).
Also, init.386 has an x86 real mode PE loader as well that could easily
be used to load Linux as a DLL instead of a coff binary. Then you could
combine several executable segments of differing optimizations and
select the correct one at load time. I do this now. It's pretty easy
to do with PE ...
Jeff
> >
> > Jeff
> >
> > >
> > > regards,
> > >
> > > Davej.
> > >
> > > --
> > > | Dave Jones <davej@suse.de> http://www.suse.de/~davej
> > > | SuSE Labs
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 0:03 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 23:24 Installing kernel 2.4 davej
2000-11-07 23:37 ` Jeff V. Merkey
2000-11-07 23:47 ` Jeff V. Merkey
2000-11-07 23:59 ` Jeff V. Merkey [this message]
2000-11-08 0:51 ` David Lang
2000-11-08 0:10 ` Jeff V. Merkey
2000-11-08 3:39 ` davej
2000-11-08 4:41 ` Jeff V. Merkey
2000-11-08 3:57 ` davej
2000-11-08 12:05 ` Horst von Brand
2000-11-08 15:29 ` Eric W. Biederman
2000-11-08 16:51 ` James A. Sutherland
2000-11-08 17:36 ` George Anzinger
2000-11-08 19:43 ` James A. Sutherland
2000-11-08 20:32 ` George Anzinger
2000-11-08 22:01 ` James A. Sutherland
2000-11-09 13:25 ` David Woodhouse
2000-11-09 18:24 ` James A. Sutherland
2000-11-08 3:30 ` davej
2000-11-08 0:03 ` Jeff Garzik
2000-11-08 0:06 ` Jeff V. Merkey
2000-11-08 3:25 ` davej
2000-11-08 4:36 ` Jeff V. Merkey
2000-11-08 3:50 ` davej
-- strict thread matches above, loose matches on Subject: below --
2000-11-08 19:19 David Feuer
2000-11-08 13:49 Bruce_Holzrichter
2000-11-08 15:10 ` davej
2000-11-08 19:16 ` Jeff V. Merkey
2000-11-08 13:43 Jesse Pollard
2000-11-08 18:52 ` Jeff V. Merkey
2000-11-08 2:25 Marty Fouts
2000-11-08 3:43 ` davej
2000-11-08 2:19 Marty Fouts
2000-11-07 22:49 Bruce_Holzrichter
2000-11-07 20:52 Anil kumar
2000-11-07 20:59 ` Jeff V. Merkey
2000-11-07 21:39 ` Tigran Aivazian
2000-11-07 22:28 ` Martin Josefsson
2000-11-07 22:32 ` Jeff V. Merkey
2000-11-07 22:51 ` kernel
2000-11-07 23:10 ` Jeff V. Merkey
2000-11-07 23:57 ` Jeff Garzik
2000-11-08 0:01 ` Jeff V. Merkey
2000-11-08 0:10 ` Jeff Garzik
2000-11-08 0:12 ` Jeff V. Merkey
2000-12-10 8:22 ` Mark W. McClelland
2000-11-09 13:40 ` Alan Cox
2000-11-08 2:18 ` H. Peter Anvin
2000-11-08 7:35 ` Jeff V. Merkey
2000-11-08 0:54 ` Alan Cox
2000-11-08 3:31 ` Matthew Kirkwood
2000-11-08 0:11 ` David Lang
2000-11-07 23:39 ` Jeff V. Merkey
2000-11-07 23:51 ` Sven Koch
2000-11-07 23:59 ` Jeff Garzik
2000-11-08 0:18 ` David Relson
2000-11-08 0:23 ` Jeff V. Merkey
2000-11-08 0:50 ` Jeff Garzik
2000-11-08 0:52 ` Jeff V. Merkey
2000-11-08 0:49 ` Alan Cox
2000-11-08 0:47 ` Jeff V. Merkey
2000-11-08 0:57 ` Alan Cox
2000-11-08 0:54 ` Jeff V. Merkey
2000-11-07 22:52 ` J . A . Magallon
2000-11-07 22:54 ` J Sloan
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=3A089766.43FD7CC0@timpanogas.org \
--to=jmerkey@timpanogas.org \
--cc=davej@suse.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