search for: balloon_init

...balloon right after boot. However, the balloon is empty. Briefly looking at this, it would seem to me that, with all pages being reserved when the system starts and only the populated ones getting the reserved status cleared in __free_pages_bootmem(), the condition to put pages into the balloon in balloon_init() is inverted. Also, dying in xen_destroy_contiguous_region() (and similarly in the failure recovery code in xen_create_contiguous_region()) if the space just unmapped can''t be re-populated seems overly harsh (we''re having a case where this actually happens); wouldn''t it...

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 _______________________________________________ Xen-devel mailing list Xen-devel@list...

...rget(unsigned long target) { /* No need for lock. Not read-modify-write updates. */ balloon_stats.target_pages = target; - schedule_work(&balloon_worker); + schedule_delayed_work(&balloon_worker, 0); } static struct xenbus_watch target_watch = @@ -400,10 +394,6 @@ static int __init balloon_init(void) balloon_stats.balloon_low = 0; balloon_stats.balloon_high = 0; - init_timer(&balloon_timer); - balloon_timer.data = 0; - balloon_timer.function = balloon_alarm; - register_balloon(&balloon_sysdev); /* -- 1.5.6.5 _______________________________________________ Xen-dev...

...balloon_set_new_target(unsigned long target) { @@ -543,8 +588,6 @@ static void balloon_set_new_target(unsigned long target) schedule_work(&balloon_worker); } -#endif - static struct xenbus_watch target_watch = { .node = "memory/target" @@ -589,12 +632,16 @@ static int __init balloon_init(void) unsigned long pfn; struct page *page; - if (!xen_pv_domain()) + if (!xen_domain()) return -ENODEV; pr_info("xen_balloon: Initialising balloon driver.\n"); - balloon_stats.current_pages = min(xen_start_info->nr_pages, max_pfn); + if (xen_pv_domain()) + balloon_stat...

make balloon driver not return pages which are in [xen_start_info->nr_pages, max_pfn] on ia64. On ia64 memory might be assigned sparsely. In that case xen_start_info->nr_pages and max_pfn doesn''t match while pages which are in [xen_start_info->nr_pages, max_pfn] are used. -- yamahata _______________________________________________ Xen-devel mailing list

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

Hi, Here is the third version of memory hotplug support for Xen guests patch. This one cleanly applies to git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git repository, xen/memory-hotplug head. On Fri, Aug 06, 2010 at 04:03:18PM +0400, Vasiliy G Tolstov wrote: [...] > Testing on sles 11 sp1 and opensuse 11.3. On results - send e-mail.. Thx. On Fri, Aug 06, 2010 at 12:34:08PM

...t) -nls -test 0 kB [ebuild R ] sys-devel/libtool-1.5.20 0 kB [ebuild R ] sys-kernel/xen-sources-2.6.12.5-r4 -build -doc -symlink 0 kB [ebuild R ] app-emulation/xen-3.0.0_pre20051128 -debug -doc +screen 0 kB COMPILE TIME OUTPUT LD .tmp_vmlinux1 drivers/built-in.o: In function `balloon_init'': balloon.c:(.init.text+0x63fb): undefined reference to `create_xen_proc_entry'' drivers/built-in.o: In function `privcmd_init'': privcmd.c:(.init.text+0x64ca): undefined reference to `create_xen_proc_entry'' drivers/built-in.o: In function `xenbus_probe_init'...

Lots of changes since v2, too much to remember or summarize. Please ignore patch 11/11, it's just for my testing. Rich.

...ng xenbus_probe_backend_init+0x0/0x1f @ 1 [ 36.125403] initcall xenbus_probe_backend_init+0x0/0x1f returned 0 after 0 usecs [ 36.132853] calling xenbus_probe_frontend_init+0x0/0x1f @ 1 [ 36.138574] initcall xenbus_probe_frontend_init+0x0/0x1f returned 0 after 0 usecs [ 36.146110] calling balloon_init+0x0/0x19a @ 1 [ 36.150703] xen_balloon: Initialising balloon driver with page order 0. [ 36.157384] initcall balloon_init+0x0/0x19a returned 0 after 0 usecs [ 36.163790] calling misc_init+0x0/0x95 @ 1 [ 36.168041] initcall misc_init+0x0/0x95 returned 0 after 0 usecs [ 36.174103] calling...