All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: xenheap pages mapped by dom0
Date: Fri, 18 Dec 2009 16:19:03 +0000	[thread overview]
Message-ID: <4B2BAB77.3020508@eu.citrix.com> (raw)
In-Reply-To: <4B2BB16C0200007800026AB5@vpn.id2.novell.com>

Jan Beulich wrote:
>>>> Keir Fraser <keir.fraser@eu.citrix.com> 18.12.09 16:24 >>>
>>>>         
>> I think the right thing to do would be very roughly:
>> On allocation:
>> page = alloc_xenheap_page();
>> share_xen_page_with_guest(page);
>> On deallocation:
>> if (test_and_clear(PGC_allocated)) put_page();
>> if (page->count_info & PGC_count_mask) return -EBUSY;
>>     
>
> Hmm, and how would you recover from that? I don't think George wants
> his enclosing operation to fail because of a page still being mapped. On
> x86-64, at least, it might be possible to play with PGC_xen_heap, to
> convert a Xen heap page to a domain heap one, but that wouldn't
> cover anyone else (and would seem rather hackish, if it works at all).
>   
I wouldn't really mind the op failing; I just want it to fail cleanly. 
All-or-nothing would be optimal IMHO.  Failing such that everything will 
automatically clean itself up if/when dom0 does unmap the pages would be 
OK too.  Having half the pages freed / marked unallocated, but some 
still allocated doesn't seem very good.

Anyway, I care more about allocating larger buffers than I do about 
re-allocating, so maybe I'll just punt on freeing maybe-mapped buffers 
for now.

However, that brings up another point: suppose that I do several 
allocations, one per cpu, and one fails.  Now I want to go and free the 
buffers I've just allocated (which shouldn't be mapped in dom0 yet).   
Can I not just call free_xenheap_pages()? Do I need to clear 
PGC_allocated before calling?

Is any of this stuff written down somewhere? :-)

 -George

  parent reply	other threads:[~2009-12-18 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 14:04 xenheap pages mapped by dom0 George Dunlap
2009-12-18 14:29 ` Jan Beulich
2009-12-18 15:24   ` Keir Fraser
2009-12-18 15:29     ` George Dunlap
2009-12-18 16:03       ` Keir Fraser
2009-12-18 15:44     ` Jan Beulich
2009-12-18 16:12       ` Keir Fraser
2009-12-18 16:19       ` George Dunlap [this message]
2009-12-18 16:37         ` Jan Beulich
2009-12-18 16:40         ` Keir Fraser
2009-12-18 21:59           ` George Dunlap

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=4B2BAB77.3020508@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=Keir.Fraser@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.