Re: [kvm-ppc-devel] RFC/patch portability: split kvm_vm_ioctl v2

[Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>]

Izik Eidus wrote:
> my idea was to let kvm register userspace memory that will hold the 
> guest memory,
> and then much like qemu do with its cpu_register_physical_memory 
> function, run ioctls
> that will tell the kernel how to map this memory,
> what i wanted to achieved is making the memory allocation code shared, 
> but still
> let each arch to use any kind of "arch depended" mapping rules it want,
> but after reading the last posts it seems like you can use the normal 
> memslots, so it is kind of useless i guess and i will
> give up the idea of writing patch to make this, unless you still have 
> problem with the memslots?
Looks like we shared the same misunderstanding about the current 
memslot implementation *shaking hands*. After being educated on 
memslots by Avi, I agree that memslots do the right thing.

cheers,
Carsten

-------------------------------------------------------------------------
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/