similar to: [PATCH 0/9] tmem: Add transcendent memory to hypervisor

At last year''s Xen North America Summit in Boston, I gave a talk about memory overcommitment in Xen. I showed that the basic mechanisms for moving memory between domains were already present in Xen and that, with a few scripts, it was possible to roughly load-balance memory between domains. During this effort, I discovered that "ballooning" had a lot of weaknesses, even though

Hi Linux kernel folks and Xen folks -- Effective July 5, I will be resigning from Oracle and "retiring" for a minimum of 12-18 months and probably/hopefully much longer. Between now and July 5, I will be tying up loose ends related to my patches but also using up accrued vacation days. If you have a loose end you''d like to see tied, please let me know ASAP and I will do my

Hmmm... It appears I never posted the corrected version of this patch so it never made it upstream. See: http://lists.xen.org/archives/html/xen-devel/2011-11/msg00587.html http://lists.xen.org/archives/html/xen-devel/2011-11/msg02145.html It would be good if this very minor fix was also applied to 4.2 (and, if possible, 4.1). Thanks, Dan =================== The program xen-tmem-list-parse

Hi, I have noticed that, in the code of linux/drivers/xen/balloon.c, there exists the snippet as this: static int __init balloon_init(void) { unsigned long pfn; struct page *page; if (!xen_pv_domain()) return -ENODEV; ..... } Does it means the driver will not work in HVM? If so, where is the HVN-enabled code for that? 2010-11-16 Rui Chu _______________________________________________

If any new Xen developers are interested in a simple project to learn Xen development (and also Xen Transcendent Memory), it would be interesting to test this in Xen. AFAIK, the only extensive use of compression is with Transcendent Memory ("tmem"), so learning about tmem would be a useful side-effect. Thanks, Dan

If any new Xen developers are interested in a simple project to learn Xen development (and also Xen Transcendent Memory), it would be interesting to test this in Xen. AFAIK, the only extensive use of compression is with Transcendent Memory ("tmem"), so learning about tmem would be a useful side-effect. Thanks, Dan

Hi all, this is a non comprehensive list of missing features in libxenlight and\or xl: - xen_platform_pci flag support in VM config files; - relative paths support in VM config files; - hap support in VM config files; - -c option to xl create; - remus; - trigger command; - tmem-* commands; - sched-* commands; - usb-* commands; - scsi-* commands. In general if you execute "xm

This is a fourth cut of the hypervisor patch of the proposed XENMEM_claim_pages hypercall/subop, taking into account feedback from Jan and Keir and IanC, plus some fixes found via runtime debugging (using privcmd only) and some added comments/cleanup. [Logistical note: I will be out tomorrow (Friday) plus US holidays next week so my responsiveness to comments may be slower for awhile. --djm]

Add tmem-* commands, did some simple tests. [PATCH 1/6]xl: Add ''xl tmem-list'' command [PATCH 2/6]xl: Add ''xl tmem-freeze'' command [PATCH 3/6]xl: Add ''xl tmem-destroy'' command [PATCH 4/6]xl: Add ''xl tmem-thaw'' command [PATCH 5/6]xl: Add ''xl tmem-set'' command [PATCH 6/6]xl: Add ''xl

> -----Original Message----- > From: Matt [mailto:jackdachef@gmail.com] > Sent: Tuesday, February 15, 2011 5:12 PM > To: Minchan Kim > Cc: Dan Magenheimer; gregkh@suse.de; Chris Mason; linux- > kernel@vger.kernel.org; linux-mm@kvack.org; ngupta@vflare.org; linux- > btrfs@vger.kernel.org; Josef Bacik; Dan Rosenberg; Yan Zheng; > miaox@cn.fujitsu.com; Li Zefan > Subject:

__map_domain_page() *must* be matched with an unmap_domain_page(). These five static inline functions each map a page (or two), then throw away the context needed to unmap it. Each of the changes are limited to their respective functions. In two cases, this involved replacing a large amount of pointer arithmetic with memcpy() (all callers were relying on memcpy() semantics of positive/negative

Hi, I have allocated few order=9 pages in Xen memory space using alloc_domheap_pages(NULL,9,0) during boot time just before domain is created (dom0 = domain_create(0, DOMCRF_s3_integrity, DOM0_SSIDREF) in xen/arch/x86/setup.c). I got the following virtual addresses in xen log message- (XEN) a2k2: Virt_addr:ffff83011cc00000 MFN:11cc00 (XEN) a2k2: Virt_addr:ffff83011ca00000 MFN:11ca00 (XEN)

tmem is not supported on arm or arm64 yet. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig index 9e02d60..a18f350 100644 --- a/drivers/xen/Kconfig +++ b/drivers/xen/Kconfig @@ -145,7 +146,7 @@ config SWIOTLB_XEN config XEN_TMEM tristate - depends on !ARM + depends on !ARM && !ARM64 default m if

Hello, I am running a functional Xen 4.0 platform. The objective is the project I am currently running is to replace 4 VMWare ESX by 4 Xen 4.0 hypervisors. I have been able to reproduce all the core VMWare features in Xen (but better of course =D) except memory overcommitment. I know this feature has been included since Xen 3.3 but I have found almost no information about it. When I try to

Folks, The second release candidate for Xen 3.4.0 is available at http://xenbits.xensource.com/xen-unstable.hg, tagged as ''3.4.0-rc2''. Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

XEN_DOM0 is a silent option that has been automatically selected when CONFIG_XEN is selected since 6b0661a5e6fbf. If this option was changed to a menu configurable option then it would only give users the ability to compile out about 100 kbytes of code. As that option makes little sense to choose, and the option isn''t menu selectable anyway, then we can clean up some code by simply

Prevent xl from doing any operation if xend daemon is running. That prevents bugs that happened when xl and xend raced to close a domain. Changes since v1: * Add documentation to xl man page. * Permit the execution of commands that don''t modify anything. * Indent error message. Cc: george.dunlap@eu.citrix.com Cc: ian.jackson@eu.citrix.com Signed-off-by: Roger Pau Monne

[7] core tmem code _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel