xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, KeirFraser <keir@xen.org>,
	Tim Deegan <tim@xen.org>,
	ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] xen/mm: Unmap page for direct mapped domain on decrease reservation
Date: Tue, 27 Oct 2015 13:54:04 +0000	[thread overview]
Message-ID: <562F81FC.3000800@citrix.com> (raw)
In-Reply-To: <562F855D02000078000AF1F9@prv-mh.provo.novell.com>

On 27/10/15 13:08, Jan Beulich wrote:
>> --- a/xen/common/memory.c
>> +++ b/xen/common/memory.c
>> @@ -257,8 +257,16 @@ int guest_remove_page(struct domain *d, unsigned long gmfn)
>>  
>>      if ( test_and_clear_bit(_PGT_pinned, &page->u.inuse.type_info) )
>>          put_page_and_type(page);
>> -            
>> -    if ( test_and_clear_bit(_PGC_allocated, &page->count_info) )
>> +
>> +    /*
>> +     * With the lack for iommu on some ARM platform, domain with DMA-capable
> 
> I think it's "lack of", and I also wonder whether calling out ARM here
> is really meaningful.
> 
>> +     * device must retrieve the same pfn when the hypercall populate_physmap
>> +     * is called.
>> +     *
>> +     * For this purpose, the page is kept allocated.
> 
> ..., to match populate_physmap() behavior. (or some such)

I saw that your already committed the patch. FWIW, I'm fine with both
changes.

Regards,

-- 
Julien Grall

      reply	other threads:[~2015-10-27 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 11:33 [PATCH] xen/mm: Unmap page for direct mapped domain on decrease reservation Julien Grall
2015-10-27 13:08 ` Jan Beulich
2015-10-27 13:54   ` Julien Grall [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=562F81FC.3000800@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).