From: Antonio Vargas <windenntw@gmail.com>
To: Zachary Amsden <zach@vmware.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Chris Wright <chrisw@osdl.org>, Martin Bligh <mbligh@mbligh.org>,
Pratap Subrahmanyam <pratap@vmware.com>,
Christopher Li <chrisl@vmware.com>
Subject: Re: [PATCH 0/5] Virtualization patches, set 4
Date: Wed, 24 Aug 2005 21:38:56 +0200 [thread overview]
Message-ID: <69304d1105082412384bde82f7@mail.gmail.com> (raw)
In-Reply-To: <200508241839.j7OIdp5A001866@zach-dev.vmware.com>
On 8/24/05, Zachary Amsden <zach@vmware.com> wrote:
> Transparent paravirtualization patches, set 4. This batch includes
> mostly MMU hooks that can be used by the hypervisor for page allocation,
> and allows the kernel to be compiled to step out of the way of the
> hypervisor by making a hole in linear address space.
>
> Patches are based off 2.6.13-rc6-mm2; I've tested i386 PAE and non-PAE
> as well as um-i386. Although these are mostly i386 specific, some of
> the concepts are starting to apply to virtualization of other
> architectures as well.
Zach, have you had a look at the mac-on-linux virtualizer? It's coded
for arch-ppc but most probably some of these generic concepts could
get merged together...
--
Greetz, Antonio Vargas aka winden of network
http://wind.codepixel.com/
Las cosas no son lo que parecen, excepto cuando parecen lo que si son.
prev parent reply other threads:[~2005-08-24 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 18:39 [PATCH 0/5] Virtualization patches, set 4 Zachary Amsden
2005-08-24 19:38 ` Antonio Vargas [this message]
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=69304d1105082412384bde82f7@mail.gmail.com \
--to=windenntw@gmail.com \
--cc=akpm@osdl.org \
--cc=chrisl@vmware.com \
--cc=chrisw@osdl.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=pratap@vmware.com \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
--cc=zwane@arm.linux.org.uk \
/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.