Re: [PATCH] kvm-userspace: fix memslot assignment

[Avi Kivity <avi@qumranet.com>]

Christian Borntraeger wrote:
> Am Sonntag, 27. Juli 2008 schrieb Avi Kivity:
>   
>> This is really a no-op, since s390 will nack a KVM_CAP_SET_TSS_ADDR 
>> query.  Of course, the change is an improvement.
>>
>>     
>>> @@ -92,8 +92,11 @@ int get_free_slot(kvm_context_t kvm)
>>>  	if (tss_ext > 0)
>>>  		i = 0;
>>>  	else
>>> +#if !defined(__s390__)
>>>  		i = 1;
>>> -
>>> +#else
>>> +		i = 0;
>>> +#endif
>>>   
>>>       
>> ppc and ia64 also don't care about TSS_ADDR.  Care to make this depend 
>> on x86, rather than on s390?
>>     
>
> Can do. Should ppc and ia64 start with i=1 or i=0, do they need a reserved 
> slot?
>
>   

They all start with 0 AFAIK (kvm also starts with 0, it just wants it to 
be a special slot).

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