On 15.01.2013, at 14:32, Gleb Natapov wrote: > On Mon, Jan 14, 2013 at 05:17:31PM -0500, Christoffer Dall wrote: >> On Mon, Jan 14, 2013 at 1:49 PM, Gleb Natapov <gleb@xxxxxxxxxx> wrote: >>> A couple of general question about ABI. If they were already answered >>> just refer me to the previous discussion. >>> >>> On Tue, Jan 08, 2013 at 01:38:55PM -0500, Christoffer Dall wrote: >>>> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt >>>> index a4df553..4237c27 100644 >>>> --- a/Documentation/virtual/kvm/api.txt >>>> +++ b/Documentation/virtual/kvm/api.txt >>>> @@ -293,7 +293,7 @@ kvm_run' (see below). >>>> 4.11 KVM_GET_REGS >>>> >>>> Capability: basic >>>> -Architectures: all >>>> +Architectures: all except ARM >>>> Type: vcpu ioctl >>>> Parameters: struct kvm_regs (out) >>>> Returns: 0 on success, -1 on error >>>> @@ -314,7 +314,7 @@ struct kvm_regs { >>>> 4.12 KVM_SET_REGS >>>> >>>> Capability: basic >>>> -Architectures: all >>>> +Architectures: all except ARM >>>> Type: vcpu ioctl >>>> Parameters: struct kvm_regs (in) >>>> Returns: 0 on success, -1 on error >>>> @@ -600,7 +600,7 @@ struct kvm_fpu { >>>> 4.24 KVM_CREATE_IRQCHIP >>> Why KVM_GET_REGS/KVM_SET_REGS are not usable for arm? >>> >> >> We use the ONE_REG API instead and we don't want to support two >> separate APIs to user space. >> > I suppose fetching all registers is not anywhere on a fast path in > userspace :) If it's ever going to be in a fast path, we will add MULTI_REG which will feature an array of ONE_REG structs to fetch multiple registers at once. 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