Re: memory hotplug for guests?

[Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>]

Arnd Bergmann wrote:
> On Thursday 05 April 2007, Dor Laor wrote:
>   
>> Currently the only memory-over-commit mechanism is the balloon.
>> In the future we will add all the wise spectrum of host demand pages,
>> shared pages, etc.
>>     
>
> Ok, just as another hint: you should definitely take a look at
> pfault_interrupt() in arch/s390/mm/fault.c, which manages notifications
> about host memory manangement, so that the guest can put a task to
> sleep that accesses a page on the host block device, instead of suspending
> the entire guest, while waiting for the page to come back.
>   

It's a lot simpler than I would have guessed... this could be quite 
easily ported to kvm, once we have guest swap.


> arch/s390/mm/extmem.c has another very interesting concept, though the
> hcall interfaces used there are not as flexible as they should be in
> kvm. It's basically about mapping host files into the guest real address
> space, e.g. for shared memory between guests.
>   

This, too, is interesting, though it means guest apps need to be written 
to take advantage of it.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV