xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH v2] xen/gntdev, gntalloc: Remove unneeded VM flags
Date: Wed, 09 Mar 2011 13:38:20 -0500	[thread overview]
Message-ID: <4D77C91C.8000000@tycho.nsa.gov> (raw)
In-Reply-To: <20110309170534.GC8049@dumpdata.com>

On 03/09/2011 12:05 PM, Konrad Rzeszutek Wilk wrote:
>>> @@ -471,8 +483,6 @@ static int gntalloc_mmap(struct file *filp, struct vm_area_struct *vma)
>>>  	vma->vm_private_data = gref;
>>>  
>>>  	vma->vm_flags |= VM_RESERVED;
>>> -	vma->vm_flags |= VM_DONTCOPY;
>>> -	vma->vm_flags |= VM_PFNMAP | VM_PFN_AT_MMAP;
> 
> So the gntalloc driver can be used on PV. You remove the DONTCOPY,PFNMAP, and PFN_AT_MMAP
> .. while
> 
>>> -	vma->vm_flags |= VM_RESERVED|VM_DONTCOPY|VM_DONTEXPAND|VM_PFNMAP;
>>> +	vma->vm_flags |= VM_RESERVED|VM_DONTEXPAND;
>>> +
>>> +	if (use_ptemod)
>>> +		vma->vm_flags |= VM_DONTCOPY|VM_PFNMAP;
>>>  
> 
> Here (gntdev) you are more careful. Should we do the same check under PV
> for the gntalloc driver?
> 
> Have you tested this driver in PV <-> HVM env?
> 

I have not run this test case yet; however, I expect that it will work. The
reason that we need to be careful in gntdev on PV guests is because we are
not changing the PFN/MFN mapping on PV; instead, we change the application's
page tables to point to the other domain's memory. This means that the vma
cannot be copied without using another grant mapping hypercall; it also
requires special handling on unmap, which is the reason for gntdev's
dependency on the MMU notifier.

For gntalloc, this is not a concern - the pages are owned by the domain
using the gntalloc device, and can be mapped and unmapped in the same manner
as any other page of memory.

It is possible to use the same PFN/MFN mapping change in PV that we use in
HVM, which would allow PV guests to avoid treating gntdev memory specially.
I found problems with doing this the first time I tried, but I think they
were related to issues with updating the p2m and m2p maps that have since
been addressed. This change would effectively make "use_ptemod" always
false. It's slightly less efficient because the actual map requires two
hypercalls (one to update the p2m, and one to actually set up page tables)
but this doesn't seem like it would be an important issue.

-- 
Daniel De Graaf
National Security Agency

      reply	other threads:[~2011-03-09 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 18:19 [PATCH] xen/gntdev,gntalloc: Remove unneeded VM flags Daniel De Graaf
2011-03-07 19:53 ` Ian Campbell
2011-03-07 20:01   ` [PATCH] xen/gntdev, gntalloc: " Daniel De Graaf
2011-03-07 20:18   ` [PATCH v2] " Daniel De Graaf
2011-03-08  9:54     ` Ian Campbell
2011-03-09 17:05       ` Konrad Rzeszutek Wilk
2011-03-09 18:38         ` Daniel De Graaf [this message]

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=4D77C91C.8000000@tycho.nsa.gov \
    --to=dgdegra@tycho.nsa.gov \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).