[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] xenheap pages mapped by dom0


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
  • Date: Fri, 18 Dec 2009 14:04:02 +0000
  • Delivery-date: Fri, 18 Dec 2009 06:04:25 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=x6ny8pXLbbeX6V9ZwantzZ9lpz+/zKxZgCpm4B0oHc03hA49TCUlUOxN8/fqAOzNOc sBIEX8ucm3BievRsj5xnLg1jWTkhbNo78czGoIWpZNlirYnTQIG1+w/WeqbB0epEBEC0 IQgtKcS2WjWaAippPMrsinRN2gFbyqssmsFhI=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

What's the standard practice regarding freeing xenheap pages that have
been shared with dom0 (and may currently be mapped)?  Do we need to
make sure they're unmapped before we free them, or can we just call
free_xenheap_pages() and let the reference counting take care of
actually freeing them when dom0 unmaps them (if ever)?

I'm looking at allowing xentrace buffers to be resized, and need to
deal with potentially freeing pages which may be mapped by dom0.  If
it's as simple as free-and-forget, I'll include that functionality; if
it's more complicated, I'll punt until another time (as I really only
care about increasing the size of each cpu's buffer, not resizing
buffers).

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.