From: Shaohua Li <shaohua.li@intel.com>
To: Avi Kivity <avi@qumranet.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kvm-devel@lists.sourceforge.net, general@lists.openfabrics.org
Subject: Re: [PATCH][RFC] pte notifiers -- support for external page tables
Date: Thu, 06 Sep 2007 12:28:19 +0800 [thread overview]
Message-ID: <1189052899.6224.5.camel@sli10-conroe.sh.intel.com> (raw)
In-Reply-To: <11890207643068-git-send-email-avi@qumranet.com>
On Wed, 2007-09-05 at 22:32 +0300, Avi Kivity wrote:
> [resend due to bad alias expansion resulting in some recipients
> being bogus]
>
> Some hardware and software systems maintain page tables outside the normal
> Linux page tables, which reference userspace memory. This includes
> Infiniband, other RDMA-capable devices, and kvm (with a pending patch).
>
> Because these systems maintain external page tables (and external tlbs),
> Linux cannot demand page this memory and it must be locked. For kvm at
> least, this is a significant reduction in functionality.
>
> This sample patch adds a new mechanism, pte notifiers, that allows drivers
> to register an interest in a changes to ptes. Whenever Linux changes a
> pte, it will call a notifier to allow the driver to adjust the external
> page table and flush its tlb.
>
> Note that only one notifier is implemented, ->clear(), but others should be
> similar.
>
> pte notifiers are different from paravirt_ops: they extend the normal
> page tables rather than replace them; and they provide high-level
> information
> such as the vma and the virtual address for the driver to use.
Looks great. So for kvm, all guest pages will be vma mapped?
There are lock issues in kvm between kvm lock and page lock.
Will shadow page table be still stored in page->private? If yes, the
page->private must be cleaned before add_to_swap.
Thanks,
Shaohua
--
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 4:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 19:32 Avi Kivity
2007-09-05 19:56 ` [kvm-devel] " Rusty Russell
2007-09-05 20:17 ` Avi Kivity
2007-09-06 4:28 ` Shaohua Li [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-09-05 16:38 [PATCH][RFC]: " 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
2007-09-05 20:40 ` Jack Steiner
2007-09-05 20:40 ` Avi Kivity
2007-09-05 20:42 ` 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=1189052899.6224.5.camel@sli10-conroe.sh.intel.com \
--to=shaohua.li@intel.com \
--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 \
/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