From: Avi Kivity <avi@qumranet.com>
To: Rik van Riel <riel@redhat.com>
Cc: 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: Wed, 05 Sep 2007 22:32:47 +0300 [thread overview]
Message-ID: <46DF045F.4020806@qumranet.com> (raw)
In-Reply-To: <46DF0234.7090504@redhat.com>
Rik van Riel wrote:
>>
>> I imagine that many of the paravirt_ops mmu hooks will need to be
>> exposed as pte notifiers. This can't be done as part of the
>> paravirt_ops code due to the need to pass high level data structures,
>> though.
>
> Wait, I thought that paravirt_ops was all on the side of the
> guest kernel, where these host kernel operations are invisible?
>
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).
--
Any sufficiently difficult bug is indistinguishable from a feature.
next parent reply other threads:[~2007-09-05 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11890103283456-git-send-email-avi@qumranet.com>
[not found] ` <46DEFDF4.5000900@redhat.com>
[not found] ` <46DF0013.4060804@qumranet.com>
[not found] ` <46DF0234.7090504@redhat.com>
2007-09-05 19:32 ` Avi Kivity [this message]
2007-09-06 11:28 ` [PATCH][RFC]: pte notifiers -- support for external page tables Jeremy Fitzhardinge
[not found] ` <20070905204012.GA29272@sgi.com>
2007-09-05 20:42 ` Avi Kivity
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 11:39 ` Andi Kleen
2007-09-06 13:18 ` Avi Kivity
2007-09-06 15:17 ` Avi Kivity
2007-09-06 13:28 ` Andi Kleen
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=46DF045F.4020806@qumranet.com \
--to=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