Re: [Xen-devel] [PATCH 0 of 4] [RFC] x86 shadow: get rid of the need for contiguous memory

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

Hack up the vcpu dand domain structures and handle only being able to
allocate a single-page hypercall compat tranlsation page, and that might be
pretty much it.

 -- Keir

On 20/08/2010 17:29, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> ooohh!!  thank you thank you
> 
> /me wonders how many other order>0 allocations are left now
> that will break a running or newly-launching domain when the
> allocation fails due to fragmentation, and if it will be easy
> to track them down and shoot them
> 
>> -----Original Message-----
>> From: Tim Deegan [mailto:Tim.Deegan@xxxxxxxxxx]
>> Sent: Friday, August 20, 2010 9:58 AM
>> To: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: [Xen-devel] [PATCH 0 of 4] [RFC] x86 shadow: get rid of the
>> need for contiguous memory
>> 
>> 
>> This series of patches removes the need for shadow pagetable memory to
>> be allocated in 4-page contiguous blocks, by reusing the page_info
>> list header for yet one more thing.
>> 
>> It fixes a long-standing issue where on a fairly full machine which has
>> seen a lot of ballooning HVM domain creation can fail because the
>> remaining memory is too fragmented to use for shadows.
>> 
>> Posting as an RFC for now because I haven't had a chance to do any
>> heavy testing (compile tests under 32-bit WinXP seem fine though)
>> and I'm away for the next week.  I hope to fold in any feedback
>> and commit this change the week after that.
>> 
>> Cheers,
>> 
>> Tim.
>> 
>> 5 files changed, 332 insertions(+), 301 deletions(-)
>> xen/arch/x86/mm/shadow/common.c  |  345 +++++++++++++------------------
>> -------
>> xen/arch/x86/mm/shadow/multi.c   |  143 +++++++++------
>> xen/arch/x86/mm/shadow/private.h |  117 +++++++++++-
>> xen/include/asm-x86/domain.h     |    3
>> xen/include/asm-x86/mm.h         |   25 +-
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel