All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Kevin Lawton <kevinlawton2001@yahoo.com>
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:56:41 -0800	[thread overview]
Message-ID: <20030122115641.1be444fa.akpm@digeo.com> (raw)
In-Reply-To: <20030122182341.66324.qmail@web80309.mail.yahoo.com>

Kevin Lawton <kevinlawton2001@yahoo.com> wrote:
>
> Hello all,
> 
> 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
> the essentials via kernel configuration, since a guest
> OS doesn't need to drive much hardware.
> 
> For this, there's a few critical but simple diffs to
> macro'ize the use of the PUSHF and POPF instructions,
> due to broken semantics of running stuff using
> PVI (protected mode virtual interrupts).  The rest of
> the stuff I believe can be monitored effectively by
> the VM monitor.
> 
> Would you please consider integrating these diffs before 2.6?
> There's only one new header file, and macro substitution for
> a few cases where these instructions are used.  For a normal
> compile, there are zero logic changes.  Just 1:1 macros.

I'm wondering if this can this be done a lot more simply with assembler
macros.

The below example generates the right code.  It's then just a matter of
getting the redefined pushfl and popfl macros into kernel-wide scope. 
Possibly an explicit `-include' in the makefile system.


asm("
	.macro	popfl
	testl	$(1<<9), 0(%esp)
	jz	69003f
	.byte	0x9d		# popfl
	sti
	jmp	69004f
69003:
	.byte	0x9d		# popfl
	cli
69004:                
	.endm
");

foo()
{
	asm("popfl\n");
}


  reply	other threads:[~2003-01-22 19:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22 18:23 Simple patches for Linux as a guest OS in a plex86 VM (please consider) Kevin Lawton
2003-01-22 19:56 ` Andrew Morton [this message]
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
     [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
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
  -- strict thread matches above, loose matches on Subject: below --
2003-01-24  3:32 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=20030122115641.1be444fa.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=kevinlawton2001@yahoo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.