Anthony Liguori wrote:
> Izik Eidus wrote:
>> Anthony Liguori wrote:
>>>
>>> I think it's just a matter of calling do_mmap() with the appropriate 
>>> parameters.  It looks likes there's some drivers call do_mmap() 
>>> directly.
>>>
>> yea, i think you right, this is excellent idea!, when we will merge 
>> the swapping to kvm, we will add swapping support to older userspace.
>
> Here's a patch against your series.  The memset in kvmctl ends up 
> making the guest use all physical memory to start off with but I did 
> confirm that once the system is under memory pressure, the guest's 
> memory becomes swappable.  Of course, it's quite painful :-)
>
> A nice thing though is that a lot of the code becomes a bit cleaner 
> and we can eliminate the phys_mem array entirely.
>
> Regards,
>
> Anthony Liguori
>
>
great, this sound good, i will test it as soon as i can :)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to