On 12/01/2011 02:57 PM, Carsten Otte wrote:
> This patch introduces two ioctls for virtual cpus, that are only
> valid for kernel virtual machines that are controlled by userspace.
> Each virtual cpu has its individual address space in this mode of
> operation, and each address space is backed by the gmap
> implementation just like the address space for regular KVM guests.
> KVM_S390_UCAS_MAP allows to map a part of the user's virtual address
> space to the vcpu. Starting offset and length in both the user and
> the vcpu address space need to be aligned to 1M.
> KVM_S390_UCAS_UNMAP can be used to unmap a range of memory from a
> virtual cpu in a similar way.
> }
> --- a/include/linux/kvm.h
> +++ b/include/linux/kvm.h
> @@ -655,7 +655,14 @@ struct kvm_clock_data {
> #define KVM_SET_TSS_ADDR _IO(KVMIO, 0x47)
> #define KVM_SET_IDENTITY_MAP_ADDR _IOW(KVMIO, 0x48, __u64)
> /* enable ucontrol for s390 */
> +struct kvm_s390_ucas_mapping {
> + unsigned long user_addr;
> + unsigned long vcpu_addr;
> + unsigned long length;
> +};
Do you have 32/64 issues on s390? This struct changes size with host
userspace bitness.
> #define KVM_S390_ENABLE_UCONTROL _IO(KVMIO, 0x49)
> +#define KVM_S390_UCAS_MAP _IOW(KVMIO, 0x50, struct
> kvm_s390_ucas_mapping)
> +#define KVM_S390_UCAS_UNMAP _IOW(KVMIO, 0x51, struct
> kvm_s390_ucas_mapping)
>
>
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
