Re: [GIT PULL 1/2] KVM: s390: allow user space to handle instr 0x0000

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Marc, Christoffer,
FYI/FYA
the CAP number will conflict with your kvmarm changes.
I assume Paolo/Radim will resolve this when merging.

Seems that you have no hit in api.txt, correct?



> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
> index c4d2fb0..299306d 100644
> --- a/Documentation/virtual/kvm/api.txt
> +++ b/Documentation/virtual/kvm/api.txt
[...]
> +7.8 KVM_CAP_S390_USER_INSTR0
> +
> +Architectures: s390
[...]

> --- a/include/uapi/linux/kvm.h
> +++ b/include/uapi/linux/kvm.h
> @@ -867,6 +867,7 @@ struct kvm_ppc_smmu_info {
>  #define KVM_CAP_VCPU_ATTRIBUTES 127
>  #define KVM_CAP_MAX_VCPU_ID 128
>  #define KVM_CAP_X2APIC_API 129
> +#define KVM_CAP_S390_USER_INSTR0 130

--
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



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux