public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: help with understanding GPA/GVA issues
Date: Fri, 10 Aug 2007 19:59:36 +0300	[thread overview]
Message-ID: <46BC9978.3060801@qumranet.com> (raw)
In-Reply-To: <1186756859.4866.31.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>

Gregory Haskins wrote:
>>>   
>>>       
>> Yes, you can pass through any gva.  There are couple of things to be 
>> aware of though.  When passing a gva, you have to be sure that the gva 
>> is actually mapped in memory as KVM cannot cause Linux to fault in a 
>> page.
>>     
>
> Cool!  Ya, I totally understand and agree that it has to be "DMA" class
> memory that is mapped and pinned in guest context.  IIUC you basically
> need to follow the same rules as you would for a DMA based device in a
> bare-metal scenario.
>
>   

Note that passing a virtual address is highly discouraged as its meaning 
can change from vcpu to vcpu, it might not be mapped, translation is 
slow, etc.  Just let the guest do the translation.

> On this topic:  I know there has been talk going on of giving each VM
> its own linux va context.  IIUC, when that happens we wouldn't need the
> gva_to_hpa type functions, right?  We could use things like
> copy_to_user(), etc?  Out of curiosity, what's the status of that
> project?
>   

We have something running at qumranet, will be sent out soon.  I am 
somewhat discouraged in trying to get the thing to page -- Shaohua's 
approach is much simpler.



-------------------------------------------------------------------------
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-08-10 16:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  4:09 help with understanding GPA/GVA issues Gregory Haskins
     [not found] ` <1186718958.4866.15.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-08-10 14:32   ` Anthony Liguori
     [not found]     ` <46BC7709.4030807-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-08-10 14:40       ` Gregory Haskins
     [not found]         ` <1186756859.4866.31.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-08-10 16:59           ` Avi Kivity [this message]
     [not found]             ` <46BC9978.3060801-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-10 19:47               ` Gregory Haskins
     [not found]                 ` <1186775254.4866.52.camel-5CR4LY5GPkvLDviKLk5550HKjMygAv58XqFh9Ls21Oc@public.gmane.org>
2007-08-10 20:12                   ` Anthony Liguori
2007-08-10 15:16 ` Hollis Blanchard

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=46BC9978.3060801@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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