public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Lawton <kevinlawton2001@yahoo.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: Derek Fawcus <dfawcus@cisco.com>,
	Valdis.Kletnieks@vt.edu, Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: Simple patches for Linux as a guest OS in a plex86 VM (please consider)
Date: Fri, 24 Jan 2003 14:02:41 -0800 (PST)	[thread overview]
Message-ID: <20030124220241.30218.qmail@web80304.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301241256200.10187-100000@dlang.diginsite.com>


--- David Lang <david.lang@digitalinsight.com> wrote:
> it sounds like you are saying that with the plex86 you have two ways to
> load a client OS.
> 
> 1. 'normal', full isolation of VMs no modification of the client OS
> needed.
> 
> 2. 'nice VM'. modification of the client OS required, but with the
> exception of the kernel level commands being eliminated in the
> modification full VM isolation is still provided. Much better performance
> then case #1

No, there's always full isolation.  If a guest is run without
mods similar to the ones I submitted for Linux, the interrupt
behaviour will not work correctly for the guest.  Neither
the host nor other guests will be affected.  Nor do I care,
because this is not for running arbitrary guest OSes.

x86 does not have pure VMability.  So, rather than trying real
hard to get under the hood to make it VM'able with heavy software
techniques, just forget about running all guest OSes and
run ones that can work, like Linux.

If you look, you'll notice my patches do nothing except macroize
the pushf/popf instructions to un-break the handling of eflags.IF
inside PVI mode (since x86 breaks it).  This has nothing to do
with isolation of the guest OS.  Nothing to do with running Windows.
Nothing to do with anything except running Linux as a guest.

-Kevin

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

  reply	other threads:[~2003-01-24 21: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
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 [this message]
     [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=20030124220241.30218.qmail@web80304.mail.yahoo.com \
    --to=kevinlawton2001@yahoo.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=david.lang@digitalinsight.com \
    --cc=dfawcus@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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