From: Rusty Russell <rusty@rustcorp.com.au>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: [ofa-general] Re: [kvm-devel] [PATCH][RFC] pte notifiers -- support for external page tables
Date: Thu, 06 Sep 2007 05:56:23 +1000 [thread overview]
Message-ID: <1189022183.10802.184.camel@localhost.localdomain> (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).
And lguest. I can't tell until I've actually implemented it, but I
think it will seriously reduce the need for page pinning which is why
only root can currently launch guests.
My concern is locking: this is called with the page lock held, and I
guess we have to bump the guest out if it's currently running.
(Oh, and this means lguest needs to do a reverse mapping somehow, but
I'll come up with something).
Cheers,
Rusty.
next prev parent reply other threads:[~2007-09-05 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 19:32 [PATCH][RFC] pte notifiers -- support for external page tables Avi Kivity
2007-09-05 19:56 ` Rusty Russell [this message]
[not found] ` <1189022183.10802.184.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-09-05 20:17 ` Avi Kivity
[not found] ` <11890207643068-git-send-email-avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-06 4:28 ` Shaohua Li
2007-09-06 8:38 ` [ofa-general] " Avi Kivity
[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=1189022183.10802.184.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--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