similar to: Max gfn?

Check the return values of the libxc mem_access calls. Free allocated structures (platform_info, domain_info) on errors during initialization and exit. Unbind VIRQ, close event channel and connection to Xen on errors during initialization Signed-off-by: Aravindh Puthiyaparambil <aravindh@virtuata.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> diff -r ea47068fa7a2 -r

Hello, I''m interested in using the mem_event API (or it''s LibVMI wrapper), but I''m interested in capturing write events anywhere in a domU guest''s memory, _and_ not just once for each page write, but every time a page is being written to. To this end, I''ve looked at the xen-access.c example, where at first all the pages are being monitored:

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

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl:

Hello, how can a gfn become 0x555555 as checked in p2m.c:guest_physmap_add_entry() and p2m_alloc_table()? Looking further in p2m.c, audit_p2m() checks only for a 32bit value. So where is that magic number set, and why is it not a define to simplify grepping for users of that value? Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I wanted to run without 2MB and 1GB EPT pages, so I added "hap_2mb=0 hap_1gb=0" to the Xen grub command line. However I see the following on Xen boot: (XEN) EPT supports 2MB super page. When I bring up a guest I see a non-zero number of 2MB pages in the "xl create" output: xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000017af10 TOTAL:

> > After using 'python sdist', can't you use the tarball (in python/dist) > > in order to create a venv directly? > > I think I will be able to install the python library in the venv using > the tarball. However, won't my liguestfs application require some of > the binaries installed as part of 'make install' for running? I am > trying to not

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.

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

# 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

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

Following discussion, and a bit of slip to allow better contributions from those who''ve been away for the Chinese New Year, the plan for 4.1 now looks like this. We intend to go into code freeze at the end of the week, after which patches even for bugfixes will be much harder to get into the tree. We are here: | Feature code freeze | | Bugfixes are allowed provided they are

Two more observations: (adding to my previous below email) 1) Centos 5.6 also showing the same ACPI errors as in CentOS 5.5 2)BIOS-E820 map has a difference in the first line: (0000000000010000 instead of 0000000000000000) ================================ - Centos-5.3 BIOS-E820 memory map is: BIOS-e820: 0000000000000000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000

Patrick, there following patches fix xenpaging for me. Granttable handling is incomplete. If a page is gone, a GNTST_eagain should be returned to the caller to inidcate the hypercall has to be retried after a while, until the page is available again. Please review. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

ging_prep ensures that an mfn is backing the paged-out gfn, and transitions to the next state in the paging state machine for this page. Foreign mappings of the gfn will now succeed. This is the key idea, as it allows the pager to now map the gfn and fill in its contents. Unfortunately, it also allows any other foreign mapper to map the gfn and read its contents. This is particularly dangerous

Signed-off-by: Jan Beulich <jbeulich@novell.com> --- 2009-01-27.orig/xen/drivers/passthrough/amd/iommu_map.c 2009-01-30 08:43:35.000000000 +0100 +++ 2009-01-27/xen/drivers/passthrough/amd/iommu_map.c 2009-01-30 08:46:29.000000000 +0100 @@ -461,8 +461,8 @@ int amd_iommu_map_page(struct domain *d, iommu_l2e = iommu_l2e_from_pfn(hd->root_table, hd->paging_mode, gfn); if (

Hey We have a static analyzer setup for Xen called Coverity. It allows the code to be inspected for bugs and such. Originally I setup this so that we could make sure that there are no bugs that cause security issues - and as such invited only folks on the security Xen mailing list. But there are other folks who I am sure would like to contribute and as Coverity is pretty amazing at analyzing

-- Advanced Micro Devices GmbH Sitz: Dornach, Gemeinde Aschheim, Landkreis München Registergericht München, HRB Nr. 43632 WEEE-Reg-Nr: DE 12919551 Geschäftsführer: Alberto Bozzo, Andrew Bowd _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Jan, Attached patch dumps io page fault flags. The flags show the reason of the fault and tell us if this is an unmapped interrupt fault or a DMA fault. Thanks, Wei signed-off-by: Wei Wang <wei.wang2@amd.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel