|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] HVM support for e820_host (Was: Bug: Limitation of <=2GB RAM in domU persists with 4.3.0)
On Tue, 3 Sep 2013 17:08:33 -0400, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> wrote: You are missing the hypervisor patch to set the E820 for HVM guests. http://lists.xen.org/archives/html/xen-devel/2013-05/msg01603.htmlAnd that should make it possible to "stash" the E820 in the hypervisor. Regarding Jan's comment on the thread here: http://lists.xen.org/archives/html/xen-devel/2013-05/msg01649.html Should this not instead of: === @@ -595,7 +595,7 @@ void arch_domain_destroy(struct domain *d) if ( is_hvm_domain(d) ) hvm_domain_destroy(d); else - xfree(d->arch.pv_domain.e820); + xfree(d->arch.e820); free_domain_pirqs(d); if ( !is_idle_domain(d) ) === be something like: === @@ -595,7 +595,6 @@ void arch_domain_destroy(struct domain *d) if ( is_hvm_domain(d) ) hvm_domain_destroy(d); - else - xfree(d->arch.pv_domain.e820); + xfree(d->arch.e820); free_domain_pirqs(d); if ( !is_idle_domain(d) ) === The question I have is will d->arch.e820 always be there and set even with e820_host=0? Or does there need to be an extra check here? Then after that you will need to implement in the hvmloader.c the XENMEM_memory_map hypercall to get the E820 and do something with it.Oh, and something like this probably should do it - not compile tested Thanks. :) Will try that when I've verified the first two patches (mine and Mukesh's) build cleanly in my 4.3.0 package build. Gordan _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |