search for: current_target

...4.1 > > Thanks. I''ve pushed this into xen.git as xen/memory-hotplug so people > can play with it more easily (but I haven''t merged it into any of the > other branches yet). Thx. > >+#ifdef CONFIG_XEN_BALLOON_MEMORY_HOTPLUG > >+static inline unsigned long current_target(void) > >+{ > >+ return balloon_stats.target_pages; > > Why does this need its own version? Because original version return values not bigger then initial memory allocation which does not allow memory hotplug to function. > >+int __ref xen_add_memory(int nid, u64 start, u6...

...try too hard since that can trigger the oom killer. */ @@ -172,11 +171,6 @@ static struct page *balloon_next_page(struct page *page) return list_entry(next, struct page, lru); } -static void balloon_alarm(unsigned long unused) -{ - schedule_work(&balloon_worker); -} - static unsigned long current_target(void) { unsigned long target = balloon_stats.target_pages; @@ -333,7 +327,7 @@ static void balloon_process(struct work_struct *work) /* Schedule more work if there is some still to be done. */ if (current_target() != balloon_stats.current_pages) - mod_timer(&balloon_timer, jiffies + H...

...you have some specific tests for "xen_pv_domain()" - > are there many differences between pv and hvm? No. Only those changes are needed where xen_domain()/xen_pv_domain() is used. > >>>+#ifdef CONFIG_XEN_BALLOON_MEMORY_HOTPLUG > >>>+static inline unsigned long current_target(void) > >>>+{ > >>>+ return balloon_stats.target_pages; > >>Why does this need its own version? > >Because original version return values not bigger > >then initial memory allocation which does not allow > >memory hotplug to function. > > But...