similar to: [PATCH] xenpaging: remove XOPEN_SOURCE

Added two new sets of compile flags, and pass them to the check scripts, so libraries and includes are searched there also. Resend this patches because they suffered some modifications and where scattered along the mailing list. Please review, thanks Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

# HG changeset patch # User h00166998@h00166998.china.huawei.com # Date 1328777881 -28800 # Node ID 68eae0b487aef8349f168518f56264ce61afb0a1 # Parent 9f4640e40d4f31563885427a5a8d9eae2e110514 xenpaging:add the dealing of MEM_EVENT_FLAG_EVICT_FAIL request in tools/xenpaging If a page is nominated but not evicted,then dom0 accesses the page,it will change the page''s p2mt to be

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1333120147 -7200 # Node ID 34d9828185501f6e7ea2c3c2a397176a8e54ef0a # Parent 80653c8ea1d19dfe6130396bbc77f766eb9f9fab xenpaging: add error code to indicate iommem passthrough Similar to the existing ENODEV and EXDEV error codes, add EMDEV to indicate that iommu passthrough is not compatible with paging. All error codes are

# HG changeset patch # User hongkaixing<hongkaixing@huawei.com> # Date 1325149704 -28800 # Node ID 052727b8165ce6e05002184ae894096214c8b537 # Parent 54a5e994a241a506900ee0e197bb42e5f1d8e759 xenpaging:add a new array to speed up page-in in xenpaging This patch adds a new array named page_out_index to reserve the victim''s index. When page in a page,it has to go through a for loop

Hi,Olaf, I have some questions about event channel in Xenpaging to ask you. 1) In xenpaging it uses Inter-Domainain Commnication (IDC) between dom0 and domU to build bidirectional connection,but I found there is only an event channel notification from xen to dom0 when page faults happens.It seems that xenpaging_resume_page()->xc_evtchn_notify() doesn''t make any difference.So why

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1318335991 -7200 # Node ID 2fb4bf8c16cd35ddc0bf7ddc7ff8fda4b9678211 # Parent 64f17c7e6c33e5f1c22711ae9cbdcbe191c20062 libxl: reimplement buffer for bootloading and drop data if buffer is full. Implement a buffer for the bootloading process that appends data to the end until it''s full. Drop output from

Hi, Olaf we have tested the xenpaging feature and found some problems. (1) the test case like this : when we start a VM with POD enable, the xenpaging is started at the same time. this case will cause many problems ,finally, we fixed the BUG, the patch is attached below. (2) there is a very serious problem. we have observed many VM crash examples, the error code is not always the same.

26470:acaf29203cf9 "tools+stubdom: install under /usr/local by default" moved more stuff under /usr/local than was desirable. In particular SYSCONFIG_DIR (configuration for initscripts) moved to /usr/local/etc/{sysconfig,defaults} while the initscripts themselves (correctly) remained in /etc/init.d. Moving /etc/xen/scripts breaks the udev bakcned rules file. Lastly stuff under /var was

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.

I am building xen-unstable (23860:a422e2a4451e) on Ubuntu 11.10. I noticed that the "make install" does not create lib entries in /usr/lib/. I see them only in /usr/lib64/. This is causing program like xenpaging to not find the xenctrl library (error while loading shared libraries: libxenctrl.so.4.2: cannot open shared object file: No such file or directory) Is this expected behavior or

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

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1324385575 -3600 # Node ID 716d6d48e647d1d4352f7206e74e693152a4f8fa # Parent f72b99fccfca694674259cc1c03c526a827b67ec libxl: add support for yajl 2.x This patch adds support for yajl versions 2.x, while retaining 1.x compatibility. This patch adds quite a lot of #ifdefs all over the json code, so I''m open

flight 13439 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13439/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl-qemuu-winxpsp3 9 guest-localmigrate fail REGR. vs. 13379 test-amd64-amd64-xl-qemuu-win7-amd64 9 guest-localmigrate fail REGR. vs. 13376 Regressions which are regarded as

Hi all, I''m trying to update my RPMs of 4.1.3 to work with 4.2.0, but I''m having some interesting problems with the packaging side of things. in 4.1.3, xenpaging was being built as /usr/sbin/xenpaging, however in 4.2.0 it is being built as /usr/lib/xen/bin/xenpaging. I''m currently using the following configure options in my .spec: ./configure --libdir=/%{_libdir}

# HG changeset patch # User h00166998@h00166998.china.huawei.com # Date 1329462865 -28800 # Node ID 9fd12f919ddbd15927117eff42149664dba698ca # Parent b75664e5390583c5d2075c82a14245bc941b3aaf x86/mm: Make sure the event channel is released accurately In xenpaging source code,there is an interdomain communication between dom0 and domU. In mem_event_enable(),the function

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1326454799 -3600 # Node ID 58c924a72ab7af658a888ff39411229a9e6a12f6 # Parent 887a3229fd7a50c04981e29709bc7210dafef38f libxl: fix parse_backend_path and device_backend_path to be mutual Currently if libxl__parse_backend_path is used and then you try to get the original path again with libxl__device_backend_path the

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1326606960 -3600 # Node ID a1986ef30b7dab4f60fe5cda70856f5751a9fde2 # Parent cd47dde439e688cac244c7eb9f55d826c85c844f libxl: add support for yajl 2.x This patch adds support for yajl versions 2.x, while retaining 1.x compatibility. All the needed ifdefs can be found in libxl_json.h. Tested with yajl 2.0.3 and

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1326564288 -3600 # Node ID 259112aee618753552056e398f940d1fd9fcc6f7 # Parent f581bb82fecd51e8fbd9c2e4ae9e76b08a695587 libxl: fix mutex initialization The macro PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP is not defined on NetBSD, so define mutex attributes manually. Changes since v1: * Fix leak of mutex attr.

vif interfaces allows the user to specify the domain that should run the backend (also known as driver domain) using the ''backend'' parameter. This is not compatible with run_hotplug_scripts=1, since libxl can only run the hotplug scripts from the Domain 0. Signed-off-by: Roger Pau Monne <roger.pau@citrix.com> --- docs/misc/xl-network-configuration.markdown | 6 ++++--

When using a vtsc, hvm_set_guest_time changes hvm_vcpu.stime_offset, which is used in the vcpu time structure to calculate the tsc_timestamp, so after updating stime_offset we need to propagate the change to vcpu_time in order for the guest to get the right time if using the PV clock. This was not done correctly, since in context_switch update_vcpu_system_time was called before vmx_do_resume,