search for: xenpaging_teardown

...quot;free(dom_path);free(watch_targetpages)" in PATCH 9,but I think we should firstly judge if dom_path and watch_targetpages variables are NULL.what''s more ,if it initializes paging successfully，before "return paging",we should free (dom_path),and free(watch_targetpages) in xenpaging_teardown() lastly. c、when initializing xenpaging fails,and goes to err,it returns NULL to main() then exit main(). If it has already opened event channel,bind event notification,opened connections to xen successfully when goes to err in xenpaging_init()，how about dealing with these resources such as xenpagi...

The following two patches are about how to speed up in xenpaging when page in pages. On suse11-64 with 4G memory,if we page out 2G pages,it will cost about 15.5 seconds, but take 2088 seconds to finish paging in.If page-in costs too much time,it will cause unmesurable problems when vm or dom0 access the paged_out page,such as BSOD,crash. What鈥檚 more,the dom0 is always in high I/O pressure.

...{ @@ -798,7 +805,15 @@ out: close(fd); unlink_pagefile(); - free(victims); + if ( NULL != victims ) + { + free(victims); + } + + if ( NULL != page_out_index ) + { + free(page_out_index); + } /* Tear down domain paging */ rc1 = xenpaging_teardown(paging); diff -r 54a5e994a241 -r 052727b8165c tools/xenpaging/xenpaging.h --- a/tools/xenpaging/xenpaging.h Wed Nov 02 17:09:09 2011 +0000 +++ b/tools/xenpaging/xenpaging.h Thu Dec 29 17:08:24 2011 +0800 @@ -54,6 +54,10 @@ unsigned long pagein_queue[XENPAGING_PAGEIN_QUEUE_SIZE]; } xenpaging_t...

The following two patches allow the parallel use of memsharing, xenpaging and xen-access by using an independent ring buffer for each feature. Please review. v2: - update mem_event_check_ring arguments, check domain rather than domain_id - check ring_full first because its value was just evaluated - check if ring buffer is initialized before calling mem_access_domctl/mem_paging_domctl