From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, shaohua.li@intel.com,
kvm-devel <kvm-devel@lists.sourceforge.net>,
general@lists.openfabrics.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC]: pte notifiers -- support for external page tables
Date: Thu, 06 Sep 2007 12:28:47 +0100 [thread overview]
Message-ID: <46DFE46F.5020001@goop.org> (raw)
In-Reply-To: <46DF045F.4020806@qumranet.com>
Avi Kivity wrote:
> It is, but the hooks are in much the same places. It could be argued
> that you'd embed pte notifiers in paravirt_ops for a host kernel, but
> that's not doable because pte notifiers use higher-level data
> strutures (like vmas).
Also, I wouldn't like to preclude the possibility of having a kernel
that's both a guest and a host (ie, nested vmms).
J
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-09-06 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 16:38 Avi Kivity
2007-09-05 19:05 ` Rik van Riel
2007-09-05 19:14 ` Avi Kivity
2007-09-05 19:23 ` Rik van Riel
2007-09-05 19:32 ` Avi Kivity
2007-09-06 11:28 ` Jeremy Fitzhardinge [this message]
2007-09-05 20:40 ` Jack Steiner
2007-09-05 20:40 ` Avi Kivity
2007-09-05 20:42 ` Avi Kivity
2007-09-06 6:24 ` [ofa-general] " Gleb Natapov
2007-09-06 8:35 ` Avi Kivity
2007-09-06 8:41 ` Gleb Natapov
2007-09-10 18:17 ` Andrew Hastings
2007-09-11 10:37 ` Daniel J Blueman
2007-09-11 11:19 ` Gleb Natapov
2007-09-05 19:32 [PATCH][RFC] " Avi Kivity
2007-09-06 4:28 ` Shaohua Li
2007-09-06 8:38 ` Avi Kivity
2007-09-06 13:28 ` Andi Kleen
[not found] ` <p73myw09g5w.fsf@bingen.suse.de>
2007-09-06 15:17 ` Avi Kivity
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=46DFE46F.5020001@goop.org \
--to=jeremy@goop.org \
--cc=avi@qumranet.com \
--cc=general@lists.openfabrics.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.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