On 24.11.2009, at 16:02, Avi Kivity wrote:
> On 11/24/2009 09:50 AM, Alexander Graf wrote:
>> Currently userspace has no chance to find out which virtual address space we're
>> in and resolve addresses. While that is a big problem for migration, it's also
>> unpleasent when debugging, as gdb and the monitor don't work on virtual
>> addresses.
>>
>
>> index 92045a9..1240fcb 100644
>> --- a/include/linux/kvm.h
>> +++ b/include/linux/kvm.h
>> @@ -492,6 +492,7 @@ struct kvm_ioeventfd {
>> #ifdef __KVM_HAVE_VCPU_EVENTS
>> #define KVM_CAP_VCPU_EVENTS 41
>> #endif
>> +#define KVM_CAP_PPC_SEGSTATE 42
>>
>>
>
> 42 is already taken (s390 psw and D. Adams), please use 43.
Aww. Any reason I didn't get the s390 patch in a git pull yet? (damn that Carsten - he got the cool number)
Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
