arm/arm64: KVM: MMIO support for BE guest
Subsystems (3)
PATCH v2 1/1 arm/arm64: KVM: MMIO support for BE guest
Do the necessary byteswap when host and guest have different views of the universe. Actually, the only case we need to take care of is when the guest is BE. All the other cases are naturally handled.
Also be careful about endianness when the data is being memcopy-ed from/to the run buffer.
---
Quoted 1 line
From v1:
- Moved data insertion/extraction into specific functions
- Bit of tidying up making the patch more readable
arch/arm/include/asm/kvm_emulate.h | 41 +++++++++++++++++ arch/arm/kvm/mmio.c | 87 +++++++++++++++++++++++++++++++----- arch/arm64/include/asm/kvm_emulate.h | 48 ++++++++++++++++++++ 3 files changed, 165 insertions(+), 11 deletions(-)
arch/arm/include/asm/kvm_emulate.h +41 -0
@@ -157,4 +157,45 @@ static inline u32 kvm_vcpu_hvc_get_imm(struct kvm_vcpu *vcpu)return kvm_vcpu_get_hsr (vcpu) &HSR_HVC_IMM_MASK ; } +static inline bool kvm_vcpu_is_be (struct kvm_vcpu *vcpu) +{ +return !!(*vcpu_cpsr (vcpu) &PSR_E_BIT ); +} + +static inline unsigned long vcpu_data_guest_to_host (struct kvm_vcpu *vcpu, +unsigned long data, +unsigned int len) +{ +if (kvm_vcpu_is_be (vcpu)) { +switch (len) { +case 1 : +return data &0xff ; +case 2 : +return be16_to_cpu (data &0xffff ); +default : +return be32_to_cpu (data); + } + } + +return data;/* Leave LE untouched */ +} + +static inline unsigned long vcpu_data_host_to_guest (struct kvm_vcpu *vcpu, +unsigned long data, +unsigned int len) +{ +if (kvm_vcpu_is_be (vcpu)) { +switch (len) { +case 1 : +return data &0xff ; +case 2 : +return cpu_to_be16 (data &0xffff ); +default : +return cpu_to_be32 (data); + } + } + +return data;/* Leave LE untouched */ +} +#endif /* __ARM_KVM_EMULATE_H__ */
arch/arm/kvm/mmio.c +76 -11
129 lines not on this page · raw message
arch/arm64/include/asm/kvm_emulate.h +48 -0
52 lines not on this page · raw message
Signature · 1 line
1.8.2.3
PATCH v2 1/1 arm/arm64: KVM: MMIO support for BE guest
Quoted 4 lines · Marc Zyngier
Do the necessary byteswap when host and guest have different views of the universe. Actually, the only case we need to take care of is when the guest is BE. All the other cases are naturally handled.
You might want to handle the case where we have LE guest on BE host because for ARM64 kernel we might have lot of people interested in running host kernel in BE mode with KVM enabled.
--
Anup
Quoted 269 lines
Also be careful about endianness when the data is being memcopy-ed from/to the run buffer.
Cc Christoffer Dall <[email protected]>Signed-off-by Marc Zyngier <[email protected]>---
Quoted 1 line
From v1:
- Moved data insertion/extraction into specific functions
- Bit of tidying up making the patch more readablearch/arm/include/asm/kvm_emulate.h | 41 +++++++++++++++++ arch/arm/kvm/mmio.c | 87 +++++++++++++++++++++++++++++++----- arch/arm64/include/asm/kvm_emulate.h | 48 ++++++++++++++++++++ 3 files changed, 165 insertions(+), 11 deletions(-)arch/arm/include/asm/kvm_emulate.h +41
-0@@ -157,4 +157,45 @@ static inline u32 kvm_vcpu_hvc_get_imm(struct kvm_vcpu *vcpu)return kvm_vcpu_get_hsr (vcpu) &HSR_HVC_IMM_MASK ; } +static inline bool kvm_vcpu_is_be (struct kvm_vcpu *vcpu) +{ +return !!(*vcpu_cpsr (vcpu) &PSR_E_BIT ); +} + +static inline unsigned long vcpu_data_guest_to_host (struct kvm_vcpu *vcpu, +unsigned long data, +unsigned int len) +{ +if (kvm_vcpu_is_be (vcpu)) { +switch (len) { +case 1 : +return data &0xff ; +case 2 : +return be16_to_cpu (data &0xffff ); +default : +return be32_to_cpu (data); + } + } + +return data;/* Leave LE untouched */ +} + +static inline unsigned long vcpu_data_host_to_guest (struct kvm_vcpu *vcpu, +unsigned long data, +unsigned int len) +{ +if (kvm_vcpu_is_be (vcpu)) { +switch (len) { +case 1 : +return data &0xff ; +case 2 : +return cpu_to_be16 (data &0xffff ); +default : +return cpu_to_be32 (data); + } + } + +return data;/* Leave LE untouched */ +} +#endif /* __ARM_KVM_EMULATE_H__ */ arch/arm/kvm/mmio.c +76
-11@@ -23,6 +23,69 @@#include "trace.h" +static void mmio_write_data (struct kvm_exit_mmio *mmio,unsigned long data) +{ +void *datap =NULL ; +union { +u8 byte; +u16 hword; +u32 word; +u64 dword; + } tmp; + +switch (mmio->len) { +case 1 : + tmp.byte = data; + datap = &tmp.byte; +break ; +case 2 : + tmp.hword = data; + datap = &tmp.hword; +break ; +case 4 : + tmp.word = data; + datap = &tmp.word; +break ; +case 8 : + tmp.dword = data; + datap = &tmp.dword; +break ; + } + +memcpy (mmio->data, datap, mmio->len); +} + +static unsigned long mmio_read_data (struct kvm_run *run) +{ +unsigned long data =0 ; +unsigned int len = run->mmio.len; +union { +u16 hword; +u32 word; +u64 dword; + } tmp; + +switch (len) { +case 1 : + data = run->mmio.data[0 ]; +break ; +case 2 : +memcpy (&tmp.hword, run->mmio.data, len); + data = tmp.hword; +break ; +case 4 : +memcpy (&tmp.word, run->mmio.data, len); + data = tmp.word; +break ; +case 8 : +memcpy (&tmp.dword, run->mmio.data, len); + data = tmp.dword; +break ; + } + +return data; +} +/** * kvm_handle_mmio_return -- Handle MMIO loads after user space emulation * @vcpu: The VCPU pointer @@ -33,28 +96,27 @@*/ int kvm_handle_mmio_return (struct kvm_vcpu *vcpu,struct kvm_run *run) { -unsigned long *dest; +unsigned long data;unsigned int len;int mask;if (!run->mmio.is_write) { - dest =vcpu_reg (vcpu, vcpu->arch.mmio_decode.rt); - *dest =0 ; - len = run->mmio.len;if (len >sizeof (unsigned long ))return -EINVAL ; -memcpy (dest, run->mmio.data, len); - -trace_kvm_mmio (KVM_TRACE_MMIO_READ , len, run->mmio.phys_addr, - *((u64 *)run->mmio.data)); + data =mmio_read_data (run);if (vcpu->arch.mmio_decode.sign_extend && len <sizeof (unsigned long )) { mask =1U << ((len *8 ) -1 ); - *dest = (*dest ^ mask) - mask; + data = (data ^ mask) - mask; } + +trace_kvm_mmio (KVM_TRACE_MMIO_READ , len, run->mmio.phys_addr, + data); + data =vcpu_data_host_to_guest (vcpu, data, len); + *vcpu_reg (vcpu, vcpu->arch.mmio_decode.rt) = data; }return 0 ;@@ -105,6 +167,7 @@ int io_mem_abort(struct kvm_vcpu *vcpu, struct kvm_run *run, phys_addr_t fault_ipa) {struct kvm_exit_mmio mmio; +unsigned long data;unsigned long rt;int ret;@@ -125,13 +188,15 @@ int io_mem_abort(struct kvm_vcpu *vcpu, struct kvm_run *run, } rt = vcpu->arch.mmio_decode.rt; + data =vcpu_data_guest_to_host (vcpu, *vcpu_reg (vcpu, rt), mmio.len); +trace_kvm_mmio ((mmio.is_write) ?KVM_TRACE_MMIO_WRITE :KVM_TRACE_MMIO_READ_UNSATISFIED , mmio.len, fault_ipa, - (mmio.is_write) ? *vcpu_reg (vcpu, rt) :0 ); + (mmio.is_write) ? data :0 );if (mmio.is_write) -memcpy (mmio.data,vcpu_reg (vcpu, rt), mmio.len); +mmio_write_data (&mmio, data);if (vgic_handle_mmio (vcpu, run, &mmio))return 1 ;arch/arm64/include/asm/kvm_emulate.h +48
-1@@ -177,4 +177,52 @@ static inline u8 kvm_vcpu_trap_get_fault(const struct kvm_vcpu *vcpu)return kvm_vcpu_get_hsr (vcpu) &ESR_EL2_FSC_TYPE ; } +static inline bool kvm_vcpu_is_be (struct kvm_vcpu *vcpu) +{ +if (vcpu_mode_is_32bit (vcpu)) +return !!(*vcpu_cpsr (vcpu) &COMPAT_PSR_E_BIT ); + +return !!(vcpu_sys_reg (vcpu,SCTLR_EL1 ) & (1 <<25 )); +} + +static inline unsigned long vcpu_data_guest_to_host (struct kvm_vcpu *vcpu, +unsigned long data, +unsigned int len) +{ +if (kvm_vcpu_is_be (vcpu)) { +switch (len) { +case 1 : +return data &0xff ; +case 2 : +return be16_to_cpu (data &0xffff ); +case 4 : +return be32_to_cpu (data & ((1UL <<32 ) -1 )); +default : +return be64_to_cpu (data); + } + } + +return data;/* Leave LE untouched */ +} + +static inline unsigned long vcpu_data_host_to_guest (struct kvm_vcpu *vcpu, +unsigned long data, +unsigned int len) +{ +if (kvm_vcpu_is_be (vcpu)) { +switch (len) { +case 1 : +return data &0xff ; +case 2 : +return cpu_to_be16 (data &0xffff ); +case 4 : +return cpu_to_be32 (data & ((1UL <<32 ) -1 )); +default : +return cpu_to_be64 (data); + } + } + +return data;/* Leave LE untouched */ +} +#endif /* __ARM64_KVM_EMULATE_H__ */ --1.8.2.3
_______________________________________________
kvmarm mailing list
kvmarm at lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
PATCH v2 1/1 arm/arm64: KVM: MMIO support for BE guest
Quoted 10 lines · Anup Patel
Quoted 4 lines · Marc Zyngier
Do the necessary byteswap when host and guest have different views of the universe. Actually, the only case we need to take care of is when the guest is BE. All the other cases are naturally handled.
You might want to handle the case where we have LE guest on BE host because for ARM64 kernel we might have lot of people interested in running host kernel in BE mode with KVM enabled.
What makes you think it is not handled already?
M.
Signature · 1 line
Fast, cheap, reliable. Pick two.
PATCH v2 1/1 arm/arm64: KVM: MMIO support for BE guest
Quoted 11 lines · Marc Zyngier
Quoted 10 lines · Anup Patel
Quoted 5 lines · Marc Zyngier
Do the necessary byteswap when host and guest have different views of the universe. Actually, the only case we need to take care of is when the guest is BE. All the other cases are naturally handled.
Quoted 6 lines
Quoted 3 lines
You might want to handle the case where we have LE guest on BE host because for ARM64 kernel we might have lot of people interested in running host kernel in BE mode with KVM enabled.
What makes you think it is not handled already?
What I understood here is that you are trying to ensure that MMIO data passed to/from user space (i.e. QEMU or KVMTOOL) is host endian using vcpu_data_guest_to_host() and vcpu_data_host_to_guest(). This makes lot of sense for having all combinations of host and guest endianness.
If the above is correct then I see an issue in vcpu_data_guest_to_host() and vcpu_data_host_to_guest() for LE guest on BE host because this patch does endianness conversion for BE VCPUs only in vcpu_data_guest_to_host() and vcpu_data_host_to_guest(). If we have LE guest on BE host then these functions won't do any endianness conversion.
--
Anup
Quoted 4 lines
M.--
Fast, cheap, reliable. Pick two.
PATCH v2 1/1 arm/arm64: KVM: MMIO support for BE guest
Quoted 24 lines · Anup Patel
Quoted 11 lines · Marc Zyngier
Quoted 10 lines · Anup Patel
Quoted 5 lines · Marc Zyngier
Do the necessary byteswap when host and guest have different views of the universe. Actually, the only case we need to take care of is when the guest is BE. All the other cases are naturally handled.
Quoted 6 lines
Quoted 3 lines
You might want to handle the case where we have LE guest on BE host because for ARM64 kernel we might have lot of people interested in running host kernel in BE mode with KVM enabled.
What makes you think it is not handled already?
What I understood here is that you are trying to ensure that MMIO data passed to/from user space (i.e. QEMU or KVMTOOL) is host endian using
vcpu_data_guest_to_host()andvcpu_data_host_to_guest(). This makes lot of sense for having all combinations of host and guest endianness.
Quoted 5 lines
If the above is correct then I see an issue in
vcpu_data_guest_to_host()andvcpu_data_host_to_guest()for LE guest on BE host because this patch does endianness conversion for BE VCPUs only invcpu_data_guest_to_host()andvcpu_data_host_to_guest(). If we have LE guest on BE host then these functions won't do any endianness conversion.
And no conversion is exactly what we want. MMIO is always LE.
M.
Signature · 1 line
Jazz is not dead. It just smells funny...
PATCH v2 1/1 arm/arm64: KVM: MMIO support for BE guest
Quoted 25 lines · Marc Zyngier
Quoted 24 lines · Anup Patel
Quoted 11 lines · Marc Zyngier
Quoted 10 lines · Anup Patel
Quoted 5 lines · Marc Zyngier
Do the necessary byteswap when host and guest have different views of the universe. Actually, the only case we need to take care of is when the guest is BE. All the other cases are naturally handled.
Quoted 6 lines
Quoted 3 lines
You might want to handle the case where we have LE guest on BE host because for ARM64 kernel we might have lot of people interested in running host kernel in BE mode with KVM enabled.
What makes you think it is not handled already?
What I understood here is that you are trying to ensure that MMIO data passed to/from user space (i.e. QEMU or KVMTOOL) is host endian using
vcpu_data_guest_to_host()andvcpu_data_host_to_guest(). This makes lot of sense for having all combinations of host and guest endianness.
Quoted 7 lines
Quoted 5 lines
If the above is correct then I see an issue in
vcpu_data_guest_to_host()andvcpu_data_host_to_guest()for LE guest on BE host because this patch does endianness conversion for BE VCPUs only invcpu_data_guest_to_host()andvcpu_data_host_to_guest(). If we have LE guest on BE host then these functions won't do any endianness conversion.And no conversion is exactly what we want. MMIO is always LE.
Ok got it.
I think vcpu_data_guest_to_host() and vcpu_data_host_to_guest() have little misleading names. Can we name it vcpu_data_guest_to_le() and vcpu_data_le_to_guest()?
Now if we are always passing LE MMIO data to QEMU (even for BE host) then this will have to be handled properly for BE QEMU which means code flow for LE QEMU and BE QEMU will not be same.
--
Anup
Quoted 5 lines
M.--
Jazz is not dead. It just smells funny...
PATCH v2 1/1 arm/arm64: KVM: MMIO support for BE guest
Quoted 32 lines · Anup Patel
Quoted 31 lines · Marc Zyngier
Quoted 29 lines · Anup Patel
Quoted 11 lines · Marc Zyngier
Quoted 10 lines · Anup Patel
Quoted 5 lines · Marc Zyngier
Do the necessary byteswap when host and guest have different views of the universe. Actually, the only case we need to take care of is when the guest is BE. All the other cases are naturally handled.
Quoted 6 lines
Quoted 3 lines
You might want to handle the case where we have LE guest on BE host because for ARM64 kernel we might have lot of people interested in running host kernel in BE mode with KVM enabled.
What makes you think it is not handled already?
What I understood here is that you are trying to ensure that MMIO data passed to/from user space (i.e. QEMU or KVMTOOL) is host endian using
vcpu_data_guest_to_host()andvcpu_data_host_to_guest(). This makes lot of sense for having all combinations of host and guest endianness.If the above is correct then I see an issue in
vcpu_data_guest_to_host()andvcpu_data_host_to_guest()for LE guest on BE host because this patch does endianness conversion for BE VCPUs only invcpu_data_guest_to_host()andvcpu_data_host_to_guest(). If we have LE guest on BE host then these functions won't do any endianness conversion.
Quoted 7 lines
Quoted 1 line
And no conversion is exactly what we want. MMIO is always LE.
Ok got it.
I think
vcpu_data_guest_to_host()andvcpu_data_host_to_guest()have little misleading names. Can we name itvcpu_data_guest_to_le()andvcpu_data_le_to_guest()?
My view is that encoding the endianness in the name is also confusing. We're actually going from guest-endianness to "no-endianness".
Quoted 3 lines
Now if we are always passing LE MMIO data to QEMU (even for BE host) then this will have to be handled properly for BE QEMU which means code flow for LE QEMU and BE QEMU will not be same.
Why so? As long as MMIO is dealt with using the same endianness, it should behave the exact same, and the code should be the same. At least, it definitely is for kvmtool, and from what I gathered, the PPC guys didn't have much issues running LE guests on BE hosts using QEMU.
M.
Signature · 1 line
Jazz is not dead. It just smells funny...