public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org
Subject: Re: [PATCH][RFC] pte notifiers -- support for external page tables
Date: Wed, 05 Sep 2007 23:17:06 +0300	[thread overview]
Message-ID: <46DF0EC2.7090408@qumranet.com> (raw)
In-Reply-To: <1189022183.10802.184.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

Rusty Russell wrote:
> 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.
>
>   

Ah yes, lguest.

> 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.
>   

This will complicate kvm's locking too.  We usually take kvm->lock to do 
mmu ops, but that is now a mutex.


-- 
Any sufficiently difficult bug is indistinguishable from a feature.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-09-05 20:17 UTC|newest]

Thread overview: 7+ 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 ` [ofa-general] Re: [kvm-devel] " Rusty Russell
     [not found]   ` <1189022183.10802.184.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-09-05 20:17     ` Avi Kivity [this message]
     [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
     [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       ` [ofa-general] Re: [PATCH][RFC]: " Avi Kivity
     [not found]         ` <46DF045F.4020806-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-06 11:28           ` Jeremy Fitzhardinge

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=46DF0EC2.7090408@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=general-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.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