Re: [PATCH/RFC] KVM: Plan obsolescence of kernel allocated slots, paravirt mmu

[Avi Kivity <avi@redhat.com>]

On 01/27/2010 07:23 PM, Marcelo Tosatti wrote:
>
>>   ----------------------------
>> +What:	KVM memory aliases support
>> +When:	July 2010
>> +Why:	Memory aliasing support is used for speeding up guest vga access
>> +	through the vga windows.
>> +
>> +	Modern userspace no longer uses this feature, so it's just bitrotted
>> +	code and can be removed with no impact.
>> +Who:	Avi Kivity<avi@redhat.com>
>> +----------------------------
>> +What:	KVM kernel-allocated memory slots
>> +When:	July 2010
>> +Why:	Since 2.6.25, kvm supports user-allocated memory slots, which are
>> +	much more flexible than kernel-allocated slots.  All current userspace
>> +	supports the newer interface and this code can be removed with no
>> +	impact.
>>      
> Just a note: can block userspace usage but can't really remove code
> since there are in-kernel users (special purpose vmx pages).
>
>    

Hm, we can add a new ioctl to ask userspace for a gpa range, but require 
it to allocate the memory.

> Otherwise looks good to me.
>    

Okay - applying.

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