From: Ingo Molnar <mingo@elte.hu>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Zachary Amsden <zach@vmware.com>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
akpm@linux-foundation.org, LKML <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: ABI coupling to hypervisors via CONFIG_PARAVIRT
Date: Sat, 10 Mar 2007 00:02:50 +0100 [thread overview]
Message-ID: <20070309230249.GA31295@elte.hu> (raw)
In-Reply-To: <20070309224640.GW10574@sequoia.sous-sol.org>
* Chris Wright <chrisw@sous-sol.org> wrote:
> > ok, sure, how about the one i mentioned: long-term i'd like to have
> > a paravirt model where the guest does not store /any/ page tables -
> > all paging is managed by the hypervisor. The guest has a vma tree,
> > but otherwise it does not process pagefaults, has no concept of a
> > pte (if in paravirt mode), has no concept of kernel page tables
> > either: there are hypercalls to allocate/free guest-kernel memory,
> > etc. This needs some (serious) MM surgery but it's doable and it's
> > interesting as well. How would you map this to the VMI backend?
>
> Sounds a lot like a userspace process. My immediate thought is, why
> not use containers, a more natural fit. [...]
easy: in my model the hypervisor is isolated from the guest kernel. In
the container model it is not. [ This is a basic quality requirement for
virtualization: a guest kernel does not get to read any hypervisor
crypto keys to HD-DVD smut! ;-) ]
> [...] But if you have _any_ hope of booting this kernel on native
> hardware when it's not running under a hypervisor then I'd expect the
> same pv_ops interfaces that allow it to run on native would allow VMI
> to build and handle the shadow (since you'd have taken it out of the
> kernel). Heh, so in order to run this on native we had to add
> fork/mmap pv ops? I agree it might be interesting, but it's still not
> clear that it's useful w/out some code to back it up, and see the
> value.
progress ;-) But yes, some /really/ high-level pv_ops would be needed.
[ in the end we might be able to simplify it down to a single hook! That
would be: run_native_image / run_guest_image ;-) ]
seriously, most of the body of x86 kernel code is in filesystems, VFS,
networking, scheduler and the core kernel - much of which can be shared
between native and guest. The MM is a significant and very central
chunk, but it is less than 3% of the total codesize.
Ingo
next prev parent reply other threads:[~2007-03-09 23:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 18:02 Ingo Molnar
2007-03-09 18:28 ` Andi Kleen
2007-03-09 18:30 ` Linus Torvalds
2007-03-09 19:24 ` Ingo Molnar
2007-03-09 19:51 ` Linus Torvalds
2007-03-09 20:12 ` Ingo Molnar
2007-03-09 21:05 ` Jeremy Fitzhardinge
2007-03-09 21:06 ` Linus Torvalds
2007-03-09 21:36 ` Ingo Molnar
2007-03-09 21:40 ` Jeremy Fitzhardinge
2007-03-09 22:27 ` Linus Torvalds
2007-03-09 22:50 ` Ingo Molnar
2007-03-09 23:07 ` Zachary Amsden
2007-03-09 23:10 ` Ingo Molnar
2007-03-09 23:38 ` Zachary Amsden
2007-03-09 21:04 ` Ingo Molnar
2007-03-09 21:27 ` Chris Wright
2007-03-09 21:47 ` Ingo Molnar
2007-03-09 21:59 ` Jeremy Fitzhardinge
2007-03-09 22:12 ` Ingo Molnar
2007-03-09 22:30 ` Jeremy Fitzhardinge
2007-03-09 22:10 ` Chris Wright
2007-03-09 22:24 ` Ingo Molnar
2007-03-09 22:36 ` Jeremy Fitzhardinge
2007-03-09 23:38 ` Ingo Molnar
2007-03-09 22:46 ` Chris Wright
2007-03-09 23:02 ` Ingo Molnar [this message]
2007-03-09 23:13 ` Rik van Riel
2007-03-09 20:50 ` Jan Engelhardt
2007-03-09 22:50 ` Lee Revell
2007-03-14 8:41 ` alsa was " Pavel Machek
2007-03-14 15:59 ` Jaroslav Kysela
2007-03-15 9:03 ` Pavel Machek
2007-03-15 9:10 ` Pavel Machek
2007-03-15 9:23 ` Zachary Amsden
2007-03-15 9:32 ` Pavel Machek
2007-03-09 19:00 ` Chris Wright
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=20070309230249.GA31295@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®