similar to: Bye bye Mr tmem guy

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

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

This patch series implements the hypervisor portion of transcendent memory as described at http://oss.oracle.com/projects/tmem Tools patches to follow. All patches are sent as attachments as my mailer tends to mess with attached text. Apologies to those for whom this is inconvenient. Signed-off-by: Dan Magenheimer <dan.magenheimer.com> [1] Public interface for tmem [2] add pointer to

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

From: Ian Campbell <ian.campbell@citrix.com> There are many hypercalls which make no sense or which are not supported on ARM systems but it''s not all that obvious which ones we do support. So lets try and document the hypercalls which are useful on ARM. I''m not sure this is the best way to go about this, I''m open to other ideas. Signed-off-by: Ian Campbell

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

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

I noted a possible problem restoring a machine. In xc_domain_restore (xc_domain_restore.c) if it''s not the last checkpoint we set O_NONBLOCK flag (search for fcntl) that we can call pagebuf_get or just load other pages (see following "goto loadpages;" line). Now we could ending up calling xc_tmem_restore/xc_tmem_restore_extra (xc_tmem.c) which call read_extract (xc_private.c)

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 _______________________________________________

Hi, I''ve been trying to boot stefano''s minimal dom0 kernel from git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git 2.6.36-rc1-initial-domain-v2+pat On xen-unstable, I get the following WARN_ON()''s from Xen when bringing up the NIC''s, then the machine hangs forever when trying to login either over serial or NIC. (XEN) Xen WARN at msi.c:649 (XEN) ----[

Hello, I''ve hit known problem with dynamic memory management - memory fragmentation... This dynamic memory management basically does xl mem-set to balance memory. After some time of running system, xen memory is so fragmented that it is impossible to start new VM with PCI device. Sometimes it crashes during boot (no 64MB contiguous memory for SWIOTLB), or later - eg. iwlagn cannot

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

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]

> -----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:

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

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

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)

Updated set of patches for coverage. Changes: - change copyright lines - use gcov: instead of cover: in commit comment - use #ifdef in xen/common/sysctl.c instead of dummy inline function - added base documentation in docs/misc - added -h option to xencov