From: Kevin Lawton <kevinlawton2001@yahoo.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Simple patches for Linux as a guest OS in a plex86 VM (please consider)
Date: Wed, 22 Jan 2003 11:30:12 -0800 (PST) [thread overview]
Message-ID: <20030122193012.88140.qmail@web80311.mail.yahoo.com> (raw)
In-Reply-To: <p7365sh0zcw.fsf@oldwotan.suse.de>
--- Andi Kleen <ak@suse.de> wrote:
> Kevin Lawton <kevinlawton2001@yahoo.com> writes:
> >
> > I'm working on running Linux as a guest OS inside a
> > lightweight cut-down plex86 environment. My goal is to
> > run a stock Linux kernel, which can be slimmed down to
>
> Wouldn't it be easier if you just compile the kernel
> with a simple gcc wrapper that replaces all pushfl and popfl with your new
> sequences in the assembly code generated by gcc and also in assembly files
> compiled with the gcc wrapper?
I'm not big on the idea of scripts massaging code - especially when
they do something unintended. It's easier to run a periodic find
script that greps for use of such instructions, if new cases
are introduced. Anyways, there were really only a few cases where
pushf/popf would have even mattered. Some stuff was just
EFLAGS.{ID/AC} identification. I greatly prefer the #define mods.
The new kernel source was quite clean of this stuff, and did a great
job centrailizing stuff in include/asm-i386.
-Kevin
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
next prev parent reply other threads:[~2003-01-22 19:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030122182341.66324.qmail@web80309.mail.yahoo.com.suse.lists.linux.kernel>
2003-01-22 19:16 ` Andi Kleen
2003-01-22 19:30 ` Kevin Lawton [this message]
2003-01-23 5:11 ` Kevin Lawton
2003-01-23 5:50 ` Kai Germaschewski
2003-01-23 7:00 ` Kevin Lawton
2003-01-23 7:24 ` Andrew Morton
2003-01-23 15:41 ` Kevin Lawton
2003-01-24 15:49 ` Pavel Machek
2003-01-24 17:14 ` Kevin Lawton
2003-01-24 18:02 ` Lars Marowsky-Bree
2003-01-25 1:46 ` David Wagner
2003-01-25 12:00 ` Jan Hudec
2003-01-27 12:42 ` Pavel Machek
2003-01-26 20:00 ` Pavel Machek
2003-01-26 20:05 ` Lars Marowsky-Bree
2003-01-27 5:42 ` Nuno Silva
2003-01-24 3:32 Kevin Lawton
-- strict thread matches above, loose matches on Subject: below --
2003-01-22 18:23 Kevin Lawton
2003-01-22 19:56 ` Andrew Morton
2003-01-22 20:11 ` Kevin Lawton
2003-01-22 20:17 ` Andrew Morton
2003-01-22 20:35 ` Kai Germaschewski
2003-01-23 18:28 ` Ingo Oeser
2003-01-23 22:26 ` Jamie Lokier
2003-01-24 3:21 ` Kevin Lawton
2003-01-24 15:46 ` Pavel Machek
2003-01-24 16:52 ` Kevin Lawton
2003-01-24 19:01 ` Valdis.Kletnieks
2003-01-24 19:09 ` Kevin Lawton
2003-01-24 20:18 ` Derek Fawcus
2003-01-24 20:56 ` Kevin Lawton
2003-01-24 21:00 ` David Lang
2003-01-24 22:02 ` Kevin Lawton
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=20030122193012.88140.qmail@web80311.mail.yahoo.com \
--to=kevinlawton2001@yahoo.com \
--cc=ak@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
all inboxes | Powered by JetHome®