linux-kernel - [Xen-devel] [PATCH][v2.6.29][XEN] Return unused memory to hypervisor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19085.6134.99317.256150@gianluca.uk.xensource.com>
Date:	Thu, 20 Aug 2009 10:31:34 +0100
From:	Gianluca Guida <gianluca.guida@...rix.com>
To:	Miroslav Rezanina <mrezanin@...hat.com>
Cc:	"jeremy@...p.org" <jeremy@...p.org>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [Xen-devel] [PATCH][v2.6.29][XEN] Return unused memory to hypervisor

Miroslav Rezanina writes:
 > Hi,
 > 
 > when running linux as XEN guest and use boot parameter mem= to set memory lower then is assigned to guest, not used memory should be returned to hypervisor as free. This is working with kernel available on xen.org pages, but is not working with kernel 2.6.29. Comparing both kernels I found code for returning unused memory to hypervisor is missing. Following patch add this functionality to 2.6.29 kernel.
 > 

A good idea would be to avoid putting this code in the generic kernel
code. For now just placing it in at the end of Xen's post-allocator
init would make it completely transparent to the non-xen kernel.

There's a patch in Jeremy's rebase/master (at the moment reverted)
that allows guest to boot ballooned (which is the opposite of this
case, roughly) which does this kind of calculations while walking the
e820 table. Perhaps this can be moved there after things get to work
again.

Thanks,
Gianluca

 > Miroslav Rezanina <mrezanin@...hat.com>
 > --
 > diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
 > index 6a8811a..fd6b0e7 100644
 > --- a/arch/x86/kernel/setup.c
 > +++ b/arch/x86/kernel/setup.c
 > @@ -118,6 +118,10 @@ struct boot_params __initdata boot_params;
 >  struct boot_params boot_params;
 >  #endif
 >  
 > +#ifdef CONFIG_XEN
 > +void __init xen_return_unused_mem(void);
 > +#endif
 > +
 >  /*
 >   * Machine setup..
 >   */
 > @@ -920,6 +924,9 @@ void __init setup_arch(char **cmdline_p)
 >  	paging_init();
 >  	paravirt_pagetable_setup_done(swapper_pg_dir);
 >  	paravirt_post_allocator_init();
 > +#ifdef CONFIG_XEN
 > +	xen_return_unused_mem();
 > +#endif
 >  
 >  #ifdef CONFIG_X86_64
 >  	map_vsyscall();
 > diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
 > index 15c6c68..bc5d2bc 100644
 > --- a/arch/x86/xen/setup.c
 > +++ b/arch/x86/xen/setup.c
 > @@ -20,6 +20,7 @@
 >  #include <xen/page.h>
 >  #include <xen/interface/callback.h>
 >  #include <xen/interface/physdev.h>
 > +#include <xen/interface/memory.h>
 >  #include <xen/features.h>
 >  
 >  #include "xen-ops.h"
 > @@ -34,6 +35,36 @@ extern void xen_syscall32_target(void);
 >  
 >  
 >  /**
 > + * Author: Miroslav Rezanina <mrezanin@...hat.com>
 > + * Function retuns unused memory to hypevisor
 > + **/
 > +void __init xen_return_unused_mem(void)
 > +{
 > +	if (xen_start_info->nr_pages > max_pfn) {
 > +        /*
 > +	* the max_pfn was shrunk (probably by mem=
 > +	* kernel parameter); shrink reservation with the HV
 > +	*/
 > +	struct xen_memory_reservation reservation = {
 > +	.address_bits = 0,
 > +	.extent_order = 0,
 > +	.domid = DOMID_SELF
 > +	};
 > +	unsigned int difference;
 > +	int ret;
 > +
 > +	difference = xen_start_info->nr_pages - max_pfn;
 > +
 > +	set_xen_guest_handle(reservation.extent_start,
 > +		((unsigned long *)xen_start_info->mfn_list) + max_pfn);
 > +	reservation.nr_extents = difference;
 > +	ret = HYPERVISOR_memory_op(XENMEM_decrease_reservation,
 > +		&reservation);
 > +	BUG_ON (ret != difference);
 > +	}
 > +}
 > +
 > +/**
 >   * machine_specific_memory_setup - Hook for machine specific memory setup.
 >   **/
 >  
 > 
 > _______________________________________________
 > Xen-devel mailing list
 > Xen-devel@...ts.xensource.com
 > http://lists.xensource.com/xen-devel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/