From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jeremy Fitzhardinge <jeremy@xensource.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com,
Zachary Amsden <zach@vmware.com>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [patch 7/8] Add a bootparameter to reserve high linear address space.
Date: Tue, 04 May 2010 16:37:38 -0700 [thread overview]
Message-ID: <4BE0AFC2.2090207@goop.org> (raw)
In-Reply-To: <19700101001522.GA3999@ucw.cz>
On 12/31/1969 04:15 PM, Pavel Machek wrote:
> Dynamically loaded hypervisor? Do we really want to support that?
>
(Missed this because your datestamp was 1969...)
The idea was that you could boot a guest under VMWare fully virtualized
then switch it to a VMI guest by loading a module. I don't think it
ever worked out - the transition was too trick to get right (especially
applying all the pvops patching to a live system).
J
next prev parent reply other threads:[~2010-05-04 23:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 0:25 [patch 0/8] Basic infrastructure patches for a paravirtualized kernel Jeremy Fitzhardinge
2006-08-03 0:25 ` [patch 1/8] Remove locally-defined ldt structure in favour of standard type Jeremy Fitzhardinge
2006-08-03 0:25 ` [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor Jeremy Fitzhardinge
2006-08-03 0:28 ` Christoph Lameter
2006-08-03 0:35 ` Jeremy Fitzhardinge
2006-08-03 1:06 ` Christoph Lameter
2006-08-03 1:18 ` Zachary Amsden
2006-08-03 1:25 ` Christoph Lameter
2006-08-03 3:55 ` Andi Kleen
2006-08-03 4:25 ` Christoph Lameter
2006-08-03 4:47 ` Andi Kleen
2006-08-03 2:45 ` Andi Kleen
2006-08-03 4:27 ` Christoph Lameter
2006-08-03 4:49 ` Andi Kleen
2006-08-03 5:19 ` Christoph Lameter
2006-08-03 5:25 ` Andi Kleen
2006-08-03 5:32 ` Christoph Lameter
2006-08-03 5:39 ` Andi Kleen
2006-08-03 5:54 ` Christoph Lameter
2006-08-03 6:02 ` Andi Kleen
2006-08-03 16:49 ` Christoph Lameter
2006-08-03 17:18 ` Chris Wright
2006-08-04 0:47 ` Andi Kleen
2006-08-04 2:16 ` Christoph Lameter
2006-08-03 0:25 ` [patch 3/8] Allow a kernel to not be in ring 0 Jeremy Fitzhardinge
2006-08-03 0:25 ` [patch 4/8] Replace sensitive instructions with macros Jeremy Fitzhardinge
2006-08-03 0:25 ` [patch 5/8] Roll all the cpuid asm into one __cpuid call Jeremy Fitzhardinge
2006-08-03 0:25 ` [patch 6/8] Make __FIXADDR_TOP variable to allow it to make space for a hypervisor Jeremy Fitzhardinge
2006-08-03 0:25 ` [patch 7/8] Add a bootparameter to reserve high linear address space Jeremy Fitzhardinge
1970-01-01 0:15 ` Pavel Machek
2006-08-07 2:10 ` Andi Kleen
2010-05-04 23:37 ` Jeremy Fitzhardinge [this message]
2006-08-03 6:19 ` Andrew Morton
2006-08-03 7:33 ` Zachary Amsden
2006-08-03 7:41 ` Andrew Morton
2006-08-03 8:58 ` Zachary Amsden
2006-08-05 21:58 ` Andrew Morton
2006-08-05 22:52 ` Zachary Amsden
2006-08-05 23:17 ` Rusty Russell
2006-08-03 0:25 ` [patch 8/8] Put .note.* sections into a PT_NOTE segment in vmlinux Jeremy Fitzhardinge
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=4BE0AFC2.2090207@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.com \
/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