From: Zachary Amsden <zach@vmware.com>
To: Greg KH <greg@kroah.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
Rusty Russell <rusty@rustcorp.com.au>, Jack Lo <jlo@vmware.com>
Subject: Re: A proposal - binary
Date: Thu, 03 Aug 2006 15:49:50 -0700 [thread overview]
Message-ID: <44D27D8E.8070702@vmware.com> (raw)
In-Reply-To: <20060803223035.GA26366@kroah.com>
Greg KH wrote:
> And the PowerPC hypervisor interface :)
>
> Have you discussed this with those two groups to make sure you aren't
> doing something that would merely duplicate what they have already done?
>
I haven't personally.
There's nothing anybody has done that can be considered sufficient to
address virtualizing i386. Most of these other architectures have a
prom / lpar / hypervisor support layer already, which is what we are
trying to create for i386. And it is just about 100% architecture
specific because of the weird non-virtualizable parts of x86. Page
tables are completely different beasts when you are using a hashed page
table scheme versus hardware page tables, so there is not even common
ground in the MMU. About the only common ground would be the cede /
prod for remote notifications, but it is all so architecture dependent
that I really think any idea of creating a common cross architecture
hypervisor layer is just impossible at this time.
We need to focus on establishing that lower layer interface for i386
instead of trying to come up with the grand unified hypervisor
interface, which could be years away. For now, I think it's fair to say
there is about zero duplication, and any that we find along the way can
go into common Linux interfaces.
Zach
next prev parent reply other threads:[~2006-08-03 22:50 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 10:14 A proposal - binary Zachary Amsden
2006-08-03 11:16 ` Arjan van de Ven
2006-08-03 12:16 ` Antonio Vargas
2006-08-03 15:17 ` Rik van Riel
2006-08-03 16:05 ` Chris Wright
2006-08-03 17:57 ` Zachary Amsden
2006-08-03 18:29 ` Antonio Vargas
2006-08-03 18:47 ` Zachary Amsden
2006-08-03 18:08 ` Zachary Amsden
2006-08-03 19:03 ` Greg KH
2006-08-03 19:14 ` Zachary Amsden
2006-08-03 19:36 ` Greg KH
2006-08-03 19:56 ` Dave Jones
2006-08-03 19:59 ` Greg KH
2006-08-03 20:25 ` Options depending on STANDALONE Adrian Bunk
2006-08-03 20:28 ` Greg KH
2006-08-03 20:41 ` Dave Jones
2006-08-03 23:40 ` [v4l-dvb-maintainer] " Trent Piepho
2006-08-05 10:51 ` Adrian Bunk
2006-08-06 11:18 ` Oliver Endriss
2006-08-13 16:36 ` Adrian Bunk
2006-08-14 21:15 ` Trent Piepho
2006-08-27 21:45 ` Adrian Bunk
2006-08-03 19:48 ` A proposal - binary linux-os (Dick Johnson)
2006-08-04 6:13 ` Jan Engelhardt
2006-08-03 21:03 ` Alan Cox
2006-08-03 13:21 ` Alan Cox
2006-08-03 20:29 ` Willy Tarreau
2006-08-03 21:12 ` Alan Cox
2006-08-03 21:27 ` Zachary Amsden
2006-08-03 15:35 ` Rik van Riel
2006-08-03 18:36 ` Zachary Amsden
2006-08-05 10:45 ` Pavel Machek
2006-08-06 22:45 ` Zachary Amsden
2006-08-06 22:59 ` Greg KH
2006-08-08 0:12 ` Pavel Machek
2006-08-08 0:42 ` Zachary Amsden
2006-08-09 7:43 ` Pavel Machek
2006-08-03 19:06 ` Greg KH
2006-08-03 19:26 ` Zachary Amsden
2006-08-03 20:01 ` Greg KH
2006-08-03 21:41 ` Zachary Amsden
2006-08-03 22:33 ` Alan Cox
2006-08-03 22:30 ` Greg KH
2006-08-03 22:49 ` Zachary Amsden [this message]
2006-08-03 22:31 ` Zachary Amsden
2006-08-03 23:30 ` Alan Cox
2006-08-03 23:40 ` Zachary Amsden
2006-08-04 10:21 ` Alan Cox
2006-08-04 14:34 ` Theodore Tso
2006-08-05 0:06 ` Paul Mackerras
2006-08-04 8:56 ` Christoph Hellwig
2006-08-04 2:52 ` Jeremy Fitzhardinge
2006-08-04 4:18 ` Andrew Morton
2006-08-04 5:04 ` Rusty Russell
2006-08-04 5:53 ` Andrew Morton
2006-08-04 7:04 ` Rusty Russell
2006-08-04 7:21 ` Andrew Morton
2006-08-04 8:29 ` Rusty Russell
2006-08-04 16:57 ` David Lang
2006-08-04 18:38 ` Jeremy Fitzhardinge
2006-08-04 18:46 ` Antonio Vargas
2006-08-04 19:06 ` David Lang
2006-08-04 19:26 ` Arjan van de Ven
2006-08-04 19:45 ` David Lang
2006-08-04 20:11 ` Jeremy Fitzhardinge
2006-08-04 20:31 ` David Lang
2006-08-04 21:26 ` Jeremy Fitzhardinge
2006-08-04 21:40 ` Bill Rugolsky Jr.
2006-08-04 22:00 ` Arjan van de Ven
2006-08-04 22:45 ` David Lang
2006-08-04 19:45 ` Jeff Dike
2006-08-04 19:49 ` David Lang
2006-08-04 21:46 ` Jeff Dike
2006-08-04 22:40 ` David Lang
2006-08-04 5:40 ` Chris Wright
2006-08-04 6:28 ` Antonio Vargas
2006-08-04 7:01 ` Chris Wright
2006-08-04 7:19 ` Antonio Vargas
2006-08-04 7:37 ` Chris Wright
2006-08-04 18:34 ` Chris Wright
2006-08-04 20:41 ` Zachary Amsden
2006-08-04 20:52 ` Chris Wright
2006-08-04 21:26 ` Alan Cox
2006-08-05 1:14 ` James Bottomley
2006-08-05 5:37 ` Zachary Amsden
2006-08-05 10:42 ` Adrian Bunk
2006-08-05 11:50 ` Alan Cox
2006-08-04 22:01 ` Andi Kleen
2006-08-04 22:39 ` Zachary Amsden
2006-08-04 22:52 ` Andi Kleen
2006-08-04 22:43 ` David Lang
2006-08-05 10:47 ` Adrian Bunk
2006-08-05 11:57 ` Andi Kleen
2006-08-05 1:30 ` James Bottomley
2006-08-05 4:33 ` Zachary Amsden
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=44D27D8E.8070702@vmware.com \
--to=zach@vmware.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jlo@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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