KVM: PPC: MOL bringup patches
Subsystems (4)
cover KVM: PPC: MOL bringup patches
Mac-on-Linux has always lacked PPC64 host support. This is going to change now!
This patchset contains minor patches to enable MOL, but is mostly about bug fixes that came out of running Mac OS X. With this set and a pretty small patch to MOL I have 10.4.11 running as a guest on a 970MP host.
I'll send the MOl patches to the respective ML in the next days.
v1 -> v2:
- Add documentation for EXIT_OSI and ENABLE_CAP
- Add flags to enable_cap
- Add build fix for !CONFIG_VSX
- Remove in-paca register check
Alexander Graf (15):
KVM: PPC: Ensure split mode works
KVM: PPC: Allow userspace to unset the IRQ line
KVM: PPC: Make DSISR 32 bits wide
KVM: PPC: Book3S_32 guest MMU fixes
KVM: PPC: Split instruction reading out
KVM: PPC: Don't reload FPU with invalid values
KVM: PPC: Load VCPU for register fetching
KVM: PPC: Implement mfsr emulation
KVM: PPC: Implement BAT reads
KVM: PPC: Make XER load 32 bit
KVM: PPC: Implement emulation for lbzux and lhax
KVM: PPC: Implement alignment interrupt
KVM: Add support for enabling capabilities per-vcpu
KVM: PPC: Add OSI hypercall interface
KVM: PPC: Make build work without CONFIG_VSX/ALTIVEC
Documentation/kvm/api.txt | 28 +++++++ arch/powerpc/include/asm/kvm.h | 3 + arch/powerpc/include/asm/kvm_book3s.h | 18 +++- arch/powerpc/include/asm/kvm_host.h | 4 +- arch/powerpc/include/asm/kvm_ppc.h | 2 + arch/powerpc/kvm/book3s.c | 130 ++++++++++++++++++++++--------- arch/powerpc/kvm/book3s_32_mmu.c | 30 ++++++-- arch/powerpc/kvm/book3s_64_emulate.c | 88 +++++++++++++++++++++ arch/powerpc/kvm/book3s_64_interrupts.S | 2 +- arch/powerpc/kvm/book3s_64_slb.S | 2 +- arch/powerpc/kvm/emulate.c | 20 +++++ arch/powerpc/kvm/powerpc.c | 43 ++++++++++- include/linux/kvm.h | 17 ++++ 13 files changed, 335 insertions(+), 52 deletions(-)
A message that is not in the archive (sent off-list or not yet received): 1268071402-27112-1-git-send-email-agraf-l3A5Bk7waGM@public.gmane.org
PATCH 1/15 KVM: PPC: Ensure split mode works
On PowerPC we can go into MMU Split Mode. That means that either data relocation is on but instruction relocation is off or vice versa.
That mode didn't work properly, as we weren't always flushing entries when going into a new split mode, potentially mapping different code or data that we're supposed to.
--- arch/powerpc/include/asm/kvm_book3s.h | 9 +++--- arch/powerpc/kvm/book3s.c | 46 +++++++++++++++++--------------- 2 files changed, 29 insertions(+), 26 deletions(-)
arch/powerpc/include/asm/kvm_book3s.h +5 -4
@@ -99,10 +99,11 @@ struct kvmppc_vcpu_book3s {#define CONTEXT_GUEST 1#define CONTEXT_GUEST_END 2 -#define VSID_REAL 0xfffffffffff00000 -#define VSID_REAL_DR 0xffffffffffe00000 -#define VSID_REAL_IR 0xffffffffffd00000 -#define VSID_BAT 0xffffffffffc00000 +#define VSID_REAL_DR 0x7ffffffffff00000 +#define VSID_REAL_IR 0x7fffffffffe00000 +#define VSID_SPLIT_MASK 0x7fffffffffe00000 +#define VSID_REAL 0x7fffffffffc00000 +#define VSID_BAT 0x7fffffffffb00000#define VSID_PR 0x8000000000000000extern void kvmppc_mmu_pte_flush (struct kvm_vcpu *vcpu,u64 ea,u64 ea_mask);
arch/powerpc/kvm/book3s.c +24 -22
71 lines not on this page · raw message
Signature · 1 line
1.6.0.2
PATCH 3/15 KVM: PPC: Make DSISR 32 bits wide
In reply to a message not in the archiveDSISR is only defined as 32 bits wide. So let's reflect that in the structs too.
--- arch/powerpc/include/asm/kvm_book3s.h | 2 +- arch/powerpc/include/asm/kvm_host.h | 2 +- arch/powerpc/kvm/book3s_64_interrupts.S | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
arch/powerpc/include/asm/kvm_book3s.h +1 -1
@@ -84,8 +84,8 @@ struct kvmppc_vcpu_book3s {u64 hid[6 ];u64 gqr[8 ];int slb_nr; +u32 dsisr;u64 sdr1; -u64 dsisr;u64 hior;u64 msr_mask;u64 vsid_first;
arch/powerpc/include/asm/kvm_host.h +1 -1
@@ -260,7 +260,7 @@ struct kvm_vcpu_arch {u32 last_inst;#ifdef CONFIG_PPC64 -ulong fault_dsisr; +u32 fault_dsisr;#endif ulong fault_dear;ulong fault_esr;
arch/powerpc/kvm/book3s_64_interrupts.S +1 -1
@@ -171,7 +171,7 @@ kvmppc_handler_highmem: std r3, VCPU_PC(r7) std r4, VCPU_SHADOW_SRR1(r7) std r5, VCPU_FAULT_DEAR(r7) - std r6, VCPU_FAULT_DSISR(r7) + stw r6, VCPU_FAULT_DSISR(r7) ld r5, VCPU_HFLAGS(r7) rldicl. r5, r5, 0, 63 /* CR = ((r5 & 1) == 0) */
Signature · 1 line
1.6.0.2
PATCH 5/15 KVM: PPC: Split instruction reading out
In reply to a message not in the archiveThe current check_ext function reads the instruction and then does the checking. Let's split the reading out so we can reuse it for different functions.
--- arch/powerpc/kvm/book3s.c | 24 ++++++++++++++++-------- 1 files changed, 16 insertions(+), 8 deletions(-)
arch/powerpc/kvm/book3s.c +16 -8
@@ -650,26 +650,34 @@ void kvmppc_giveup_ext(struct kvm_vcpu *vcpu, ulong msr)kvmppc_recalc_shadow_msr (vcpu); } -static int kvmppc_check_ext (struct kvm_vcpu *vcpu,unsigned int exit_nr) +static int kvmppc_read_inst (struct kvm_vcpu *vcpu) {ulong srr0 = vcpu->arch.pc;int ret; -/* Need to do paired single emulation? */ -if (!(vcpu->arch.hflags &BOOK3S_HFLAG_PAIRED_SINGLE )) -return EMULATE_DONE ; - -/* Read out the instruction */ ret =kvmppc_ld (vcpu, &srr0,sizeof (u32), &vcpu->arch.last_inst, false);if (ret == -ENOENT ) { vcpu->arch.msr =kvmppc_set_field (vcpu->arch.msr,33 ,33 ,1 ); vcpu->arch.msr =kvmppc_set_field (vcpu->arch.msr,34 ,36 ,0 ); vcpu->arch.msr =kvmppc_set_field (vcpu->arch.msr,42 ,47 ,0 );kvmppc_book3s_queue_irqprio (vcpu,BOOK3S_INTERRUPT_INST_STORAGE ); - }else if (ret ==EMULATE_DONE ) { +return EMULATE_AGAIN ; + } + +return EMULATE_DONE ; +} + +static int kvmppc_check_ext (struct kvm_vcpu *vcpu,unsigned int exit_nr) +{ + +/* Need to do paired single emulation? */ +if (!(vcpu->arch.hflags &BOOK3S_HFLAG_PAIRED_SINGLE )) +return EMULATE_DONE ; + +/* Read out the instruction */ +if (kvmppc_read_inst (vcpu) ==EMULATE_DONE )/* Need to emulate */ return EMULATE_FAIL ; - }return EMULATE_AGAIN ; }
Signature · 1 line
1.6.0.2
PATCH 7/15 KVM: PPC: Load VCPU for register fetching
In reply to a message not in the archiveWhen trying to read or store vcpu register data, we should also make sure the vcpu is actually loaded, so we're 100% sure we get the correct values.
--- arch/powerpc/kvm/book3s.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
arch/powerpc/kvm/book3s.c +8 -0
@@ -955,6 +955,8 @@ int kvm_arch_vcpu_ioctl_get_regs(struct kvm_vcpu *vcpu, struct kvm_regs *regs) {int i; +vcpu_load (vcpu); + regs->pc = vcpu->arch.pc; regs->cr =kvmppc_get_cr (vcpu); regs->ctr = vcpu->arch.ctr;
@@ -975,6 +977,8 @@ int kvm_arch_vcpu_ioctl_get_regs(struct kvm_vcpu *vcpu, struct kvm_regs *regs)for (i =0 ; i <ARRAY_SIZE (regs->gpr); i++) regs->gpr[i] =kvmppc_get_gpr (vcpu, i); +vcpu_put (vcpu); +return 0 ; }
@@ -982,6 +986,8 @@ int kvm_arch_vcpu_ioctl_set_regs(struct kvm_vcpu *vcpu, struct kvm_regs *regs) {int i; +vcpu_load (vcpu); + vcpu->arch.pc = regs->pc;kvmppc_set_cr (vcpu, regs->cr); vcpu->arch.ctr = regs->ctr;
@@ -1001,6 +1007,8 @@ int kvm_arch_vcpu_ioctl_set_regs(struct kvm_vcpu *vcpu, struct kvm_regs *regs)for (i =0 ; i <ARRAY_SIZE (regs->gpr); i++)kvmppc_set_gpr (vcpu, i, regs->gpr[i]); +vcpu_put (vcpu); +return 0 ; }
Signature · 1 line
1.6.0.2
PATCH 8/15 KVM: PPC: Implement mfsr emulation
In reply to a message not in the archiveWe emulate the mfsrin instruction already, that passes the SR number in a register value. But we lacked support for mfsr that encoded the SR number in the opcode.
So let's implement it.
--- arch/powerpc/kvm/book3s_64_emulate.c | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-)
arch/powerpc/kvm/book3s_64_emulate.c +13 -0
@@ -35,6 +35,7 @@#define OP_31_XOP_SLBMTE 402#define OP_31_XOP_SLBIE 434#define OP_31_XOP_SLBIA 498 +#define OP_31_XOP_MFSR 595#define OP_31_XOP_MFSRIN 659#define OP_31_XOP_SLBMFEV 851#define OP_31_XOP_EIOIO 854
@@ -90,6 +91,18 @@ int kvmppc_core_emulate_op(struct kvm_run *run, struct kvm_vcpu *vcpu,case OP_31_XOP_MTMSR :kvmppc_set_msr (vcpu,kvmppc_get_gpr (vcpu,get_rs (inst)));break ; +case OP_31_XOP_MFSR : + { +int srnum; + + srnum =kvmppc_get_field (inst,12 +32 ,15 +32 ); +if (vcpu->arch.mmu.mfsrin) { +u32 sr; + sr = vcpu->arch.mmu.mfsrin (vcpu, srnum); +kvmppc_set_gpr (vcpu,get_rt (inst), sr); + } +break ; + }case OP_31_XOP_MFSRIN : {int srnum;
Signature · 1 line
1.6.0.2
PATCH 12/15 KVM: PPC: Implement alignment interrupt
In reply to a message not in the archiveMac OS X has some applications - namely the Finder - that require alignment interrupts to work properly. So we need to implement them.
But the spec for 970 and 750 also looks different. While 750 requires the DSISR fields to reflect some instruction bits, the 970 declares this as an optional feature. So we need to reconstruct DSISR manually.
--- arch/powerpc/include/asm/kvm_book3s.h | 1 + arch/powerpc/kvm/book3s.c | 9 +++++++ arch/powerpc/kvm/book3s_64_emulate.c | 40 +++++++++++++++++++++++++++++++++ 3 files changed, 50 insertions(+), 0 deletions(-)
arch/powerpc/include/asm/kvm_book3s.h +1 -0
@@ -131,6 +131,7 @@ extern void kvmppc_rmcall(ulong srr0, ulong srr1);extern void kvmppc_load_up_fpu (void );extern void kvmppc_load_up_altivec (void );extern void kvmppc_load_up_vsx (void ); +extern u32 kvmppc_alignment_dsisr (struct kvm_vcpu *vcpu,unsigned int inst);static inline struct kvmppc_vcpu_book3s *to_book3s (struct kvm_vcpu *vcpu) {
arch/powerpc/kvm/book3s.c +9 -0
@@ -905,6 +905,15 @@ program_interrupt: }break ; } +case BOOK3S_INTERRUPT_ALIGNMENT : + vcpu->arch.dear = vcpu->arch.fault_dear; +if (kvmppc_read_inst (vcpu) ==EMULATE_DONE ) { +to_book3s (vcpu)->dsisr =kvmppc_alignment_dsisr (vcpu, + vcpu->arch.last_inst); +kvmppc_book3s_queue_irqprio (vcpu, exit_nr); + } + r =RESUME_GUEST ; +break ;case BOOK3S_INTERRUPT_MACHINE_CHECK :case BOOK3S_INTERRUPT_TRACE :kvmppc_book3s_queue_irqprio (vcpu, exit_nr);
arch/powerpc/kvm/book3s_64_emulate.c +40 -0
@@ -44,6 +44,8 @@/* DCBZ is actually 1014, but we patch it to 1010 so we get a trap */ #define OP_31_XOP_DCBZ 1010 +#define OP_LFS 48 +#define SPRN_GQR0 912#define SPRN_GQR1 913#define SPRN_GQR2 914
@@ -474,3 +476,41 @@ int kvmppc_core_emulate_mfspr(struct kvm_vcpu *vcpu, int sprn, int rt)return emulated; } +u32 kvmppc_alignment_dsisr (struct kvm_vcpu *vcpu,unsigned int inst) +{ +u32 dsisr =0 ; + +/* +* This is what the spec says about DSISR bits (not mentioned = 0): +* +* 12:13 [DS] Set to bits 30:31 +* 15:16 [X] Set to bits 29:30 +* 17 [X] Set to bit 25 +* [D/DS] Set to bit 5 +* 18:21 [X] Set to bits 21:24 +* [D/DS] Set to bits 1:4 +* 22:26 Set to bits 6:10 (RT/RS/FRT/FRS) +* 27:31 Set to bits 11:15 (RA) +*/ + +switch (get_op (inst)) { +/* D-form */ +case OP_LFS : + dsisr |= (inst >>12 ) &0x4000 ;/* bit 17 */ + dsisr |= (inst >>17 ) &0x3c00 ;/* bits 18:21 */ +break ; +/* X-form */ +case 31 : + dsisr |= (inst <<14 ) &0x18000 ;/* bits 15:16 */ + dsisr |= (inst <<8 ) &0x04000 ;/* bit 17 */ + dsisr |= (inst <<3 ) &0x03c00 ;/* bits 18:21 */ +break ; +default : +printk (KERN_INFO "KVM: Unaligned instruction 0x%x\n" , inst); +break ; + } + + dsisr |= (inst >>16 ) &0x03ff ;/* bits 22:31 */ + +return dsisr; +}
Signature · 1 line
1.6.0.2
PATCH 13/15 KVM: Add support for enabling capabilities per-vcpu
In reply to a message not in the archiveSome times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next patch.
In order to have a generic mechanism in how to enable capabilities individually, this patch introduces a new ioctl that can be used for this purpose. That way features we don't want in all guests or userspace configurations can just not be enabled and we're good.
---
v1 -> v2:
- Add flags to enable_cap
- Update documentation for kvm_enable_cap
--- Documentation/kvm/api.txt | 15 +++++++++++++++ arch/powerpc/kvm/powerpc.c | 26 ++++++++++++++++++++++++++ include/linux/kvm.h | 11 +++++++++++ 3 files changed, 52 insertions(+), 0 deletions(-)
Documentation/kvm/api.txt +15 -0
@@ -749,6 +749,21 @@ Writes debug registers into the vcpu. See KVM_GET_DEBUGREGS for the data structure. The flags field is unused yet and must be cleared on entry. +4.34 KVM_ENABLE_CAP + +Capability: basic +Architectures: all +Type: vcpu ioctl +Parameters: struct kvm_enable_cap (in) +Returns: 0 on success; -1 on error + +Not all extensions are enabled by default. Using this ioctl the application +can enable an extension, making it available to the guest. + +On systems that do not support this ioctl, it always fails. On systems that +do support it, it only works for extensions that are supported for enablement. +As of writing this the only enablement enabled extenion is KVM_CAP_PPC_OSI. + 5. The kvm_run structure
arch/powerpc/kvm/powerpc.c +26 -0
@@ -462,6 +462,23 @@ int kvm_vcpu_ioctl_interrupt(struct kvm_vcpu *vcpu, struct kvm_interrupt *irq)return 0 ; } +static int kvm_vcpu_ioctl_enable_cap (struct kvm_vcpu *vcpu, +struct kvm_enable_cap *cap) +{ +int r; + +if (cap->flags) +return -EINVAL ; + +switch (cap->cap) { +default : + r = -EINVAL ; +break ; + } + +return r; +} +int kvm_arch_vcpu_ioctl_get_mpstate (struct kvm_vcpu *vcpu,struct kvm_mp_state *mp_state) {
@@ -490,6 +507,15 @@ long kvm_arch_vcpu_ioctl(struct file *filp, r =kvm_vcpu_ioctl_interrupt (vcpu, &irq);break ; } +case KVM_ENABLE_CAP : + { +struct kvm_enable_cap cap; + r = -EFAULT ; +if (copy_from_user (&cap, argp,sizeof (cap))) + goto out; + r =kvm_vcpu_ioctl_enable_cap (vcpu, &cap); +break ; + }default : r = -EINVAL ; }
include/linux/kvm.h +11 -0
@@ -400,6 +400,15 @@ struct kvm_ioeventfd {__u8 pad[36 ]; }; +/* for KVM_ENABLE_CAP */ +struct kvm_enable_cap { +/* in */ +__u32 cap; +__u32 flags; +__u64 args[4 ]; +__u8 pad[64 ]; +}; +#define KVMIO 0xAE/*
@@ -696,6 +705,8 @@ struct kvm_clock_data {/* Available with KVM_CAP_DEBUGREGS */ #define KVM_GET_DEBUGREGS _IOR(KVMIO, 0xa1, struct kvm_debugregs)#define KVM_SET_DEBUGREGS _IOW(KVMIO, 0xa2, struct kvm_debugregs) +/* No need for CAP, because then it just always fails */ +#define KVM_ENABLE_CAP _IOW(KVMIO, 0xa3, struct kvm_enable_cap)#define KVM_DEV_ASSIGN_ENABLE_IOMMU (1 << 0)
Signature · 1 line
1.6.0.2
Re: [PATCH 13/15] KVM: Add support for enabling capabilities per-vcpu
Quoted 15 lines · Alexander Graf
Some times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next patch.
In order to have a generic mechanism in how to enable capabilities individually, this patch introduces a new ioctl that can be used for this purpose. That way features we don't want in all guests or userspace configurations can just not be enabled and we're good.
Documentation/kvm/api.txt +0
-0
Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 755
Quoted 7 lines
Documentation/kvm/api.txt +3
-0@@ -749,6 +749,21 @@ Writes debug registers into the vcpu. See KVM_GET_DEBUGREGS for the data structure. The flags field is unused yet and must be cleared on entry. +4.34 KVM_ENABLE_CAP + +Capability: basic
Capability: basic means that the feature was present in 2.6.22. Otherwise you need to specify the KVM_CAP_ that presents this feature.
Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 769
Quoted 3 lines
Documentation/kvm/api.txt +1
-0+Architectures: all
But it's implemented for ppc only (other arches will get ENOTTY).
Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 765
Quoted 7 lines
Documentation/kvm/api.txt +6
-0+Not all extensions are enabled by default. Using this ioctl the application +can enable an extension, making it available to the guest. + +On systems that do not support this ioctl, it always fails. On systems that +do support it, it only works for extensions that are supported for enablement. +As of writing this the only enablement enabled extenion is KVM_CAP_PPC_OSI.
That needs to be documented. It also needs to be discoverable separately - we can have a kernel with KVM_ENABLE_CAP but without KVM_CAP_PPC_OSI.
btw, KVM_CAP_PPC_OSI conflicts with the KVM_CAP_ namespace. Please choose another namespace.
Need to document the structure fields.
Documentation/kvm/api.txt struct kvm_clock_data { · line 710
Quoted 9 lines
Documentation/kvm/api.txt +2
-0/*@@ -696,6 +705,8 @@ struct kvm_clock_data { /* Available with KVM_CAP_DEBUGREGS */ #define KVM_GET_DEBUGREGS _IOR(KVMIO, 0xa1, struct kvm_debugregs) #define KVM_SET_DEBUGREGS _IOW(KVMIO, 0xa2, struct kvm_debugregs) +/* No need for CAP, because then it just always fails */ +#define KVM_ENABLE_CAP _IOW(KVMIO, 0xa3, struct kvm_enable_cap)
The CAPs are needed so you can discover what you have without running guests.
Signature · 1 line
error compiling committee.c: too many arguments to function
Re: [PATCH 13/15] KVM: Add support for enabling capabilities per-vcpu
Quoted 26 lines · Avi Kivity
Quoted 15 lines · Alexander Graf
Some times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next patch.
In order to have a generic mechanism in how to enable capabilities individually, this patch introduces a new ioctl that can be used for this purpose. That way features we don't want in all guests or userspace configurations can just not be enabled and we're good.
Documentation/kvm/api.txt +0
-0Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 755
Quoted 7 lines
Documentation/kvm/api.txt +3
-0@@ -749,6 +749,21 @@ Writes debug registers into the vcpu. See KVM_GET_DEBUGREGS for the data structure. The flags field is unused yet and must be cleared on entry. +4.34 KVM_ENABLE_CAP + +Capability: basicCapability: basic means that the feature was present in 2.6.22. Otherwise you need to specify the
KVM_CAP_that presents this feature.
Quoted 5 lines
Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 769
Quoted 3 lines
Documentation/kvm/api.txt +1
-0+Architectures: allBut it's implemented for ppc only (other arches will get ENOTTY).
That was the whole idea behind it. if it fails it fails. Nothing we can do about it. If it succeeds - great.
Quoted 11 lines
Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 765
Quoted 8 lines
Documentation/kvm/api.txt +6
-0+Not all extensions are enabled by default. Using this ioctl the application +can enable an extension, making it available to the guest. + +On systems that do not support this ioctl, it always fails. On systems that +do support it, it only works for extensions that are supported for enablement. +As of writing this the only enablement enabled extenion is KVM_CAP_PPC_OSI.That needs to be documented. It also needs to be discoverable separately - we can have a kernel with
KVM_ENABLE_CAPbut withoutKVM_CAP_PPC_OSI.
Quoted 1 line
btw,
KVM_CAP_PPC_OSIconflicts with theKVM_CAP_namespace. Please choose another namespace.
Well I figured it'd be slick to have capabilities get enabled or disabled. That's the whole idea behind making it generic. If I wanted a specific interface I'd go in and create an ioctl ENABLE_OSI_INTERFACE.
But this way the detection if a capability exists can be done using the existing CAP detection. It can then be enabled using ENABLE_CAP.
Quoted 12 lines
Need to document the structure fields.
Documentation/kvm/api.txt struct kvm_clock_data { · line 710
Quoted 9 lines
Documentation/kvm/api.txt +2
-0/*@@ -696,6 +705,8 @@ struct kvm_clock_data { /* Available with KVM_CAP_DEBUGREGS */ #define KVM_GET_DEBUGREGS _IOR(KVMIO, 0xa1, struct kvm_debugregs) #define KVM_SET_DEBUGREGS _IOW(KVMIO, 0xa2, struct kvm_debugregs) +/* No need for CAP, because then it just always fails */ +#define KVM_ENABLE_CAP _IOW(KVMIO, 0xa3, struct kvm_enable_cap)The CAPs are needed so you can discover what you have without running guests.
The whole point of this extension was to make CAPs not always enabled, but make them possibly enable on demand.
Alex
Re: [PATCH 13/15] KVM: Add support for enabling capabilities per-vcpu
Quoted 31 lines · Alexander Graf
Quoted 28 lines · Avi Kivity
Quoted 15 lines · Alexander Graf
Some times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next patch.
In order to have a generic mechanism in how to enable capabilities individually, this patch introduces a new ioctl that can be used for this purpose. That way features we don't want in all guests or userspace configurations can just not be enabled and we're good.
Documentation/kvm/api.txt +0
-0Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 756
Quoted 8 lines
Documentation/kvm/api.txt +3
-0@@ -749,6 +749,21 @@ Writes debug registers into the vcpu. See KVM_GET_DEBUGREGS for the data structure. The flags field is unused yet and must be cleared on entry. +4.34 KVM_ENABLE_CAP + +Capability: basicCapability: basic means that the feature was present in 2.6.22. Otherwise you need to specify the
KVM_CAP_that presents this feature.
Quoted 8 lines
Quoted 6 lines
Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 767
Quoted 4 lines
Documentation/kvm/api.txt +1
-0+Architectures: allBut it's implemented for ppc only (other arches will get ENOTTY).
That was the whole idea behind it. if it fails it fails. Nothing we can do about it. If it succeeds - great.
If KVM_CAP_ENABLE_CAP is present, it means the KVM_ENABLE_CAP ioctl will not return ENOTTY (it may return EINVAL if wrong values are present).
ENOTTY means not implemented. 'Architectures: all' means implemented.
Quoted 10 lines
Quoted 10 lines
Documentation/kvm/api.txt Writes debug registers into the vcpu. · line 765
Quoted 8 lines
Documentation/kvm/api.txt +6
-0+Not all extensions are enabled by default. Using this ioctl the application +can enable an extension, making it available to the guest. + +On systems that do not support this ioctl, it always fails. On systems that +do support it, it only works for extensions that are supported for enablement. +As of writing this the only enablement enabled extenion is KVM_CAP_PPC_OSI.That needs to be documented. It also needs to be discoverable separately - we can have a kernel with
KVM_ENABLE_CAPbut withoutKVM_CAP_PPC_OSI.
Quoted 4 lines
Quoted 2 lines
btw,
KVM_CAP_PPC_OSIconflicts with theKVM_CAP_namespace. Please choose another namespace.Well I figured it'd be slick to have capabilities get enabled or disabled. That's the whole idea behind making it generic. If I wanted a specific interface I'd go in and create an ioctl
ENABLE_OSI_INTERFACE.
Ah, I see. Well, that makes sense. Please document it.
Quoted 2 lines
But this way the detection if a capability exists can be done using the existing CAP detection. It can then be enabled using
ENABLE_CAP.
Okay, I agree.
Signature · 1 line
error compiling committee.c: too many arguments to function
PATCH 14/15 KVM: PPC: Add OSI hypercall interface
In reply to a message not in the archiveMOL uses its own hypercall interface to call back into userspace when the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to.
The only user of it so far is MOL.
---
v1 -> v2:
- Add documentation for OSI exit struct
--- Documentation/kvm/api.txt | 13 +++++++++++++ arch/powerpc/include/asm/kvm_book3s.h | 5 +++++ arch/powerpc/include/asm/kvm_host.h | 2 ++ arch/powerpc/kvm/book3s.c | 24 ++++++++++++++++++------ arch/powerpc/kvm/powerpc.c | 12 ++++++++++++ include/linux/kvm.h | 6 ++++++ 6 files changed, 56 insertions(+), 6 deletions(-)
Documentation/kvm/api.txt +13 -0
@@ -932,6 +932,19 @@ s390 specific. powerpc specific. + /* KVM_EXIT_OSI */ + struct { + __u64 gprs[32]; + } osi; + +MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch +hypercalls and exit with this exit struct that contains all the guest gprs. + +If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall. +Userspace can now handle the hypercall and when it's done modify the gprs as +necessary. Upon guest entry all guest GPRs will then be replaced by the values +in this struct. + /* Fix the size of the union. */ char padding[256]; };
arch/powerpc/include/asm/kvm_book3s.h +5 -0
@@ -147,6 +147,11 @@ static inline ulong dsisr(void)extern void kvm_return_point (void ); +/* Magic register values loaded into r3 and r4 before the 'sc' assembly +* instruction for the OSI hypercalls */ +#define OSI_SC_MAGIC_R3 0x113724FA +#define OSI_SC_MAGIC_R4 0x77810F9B +#define INS_DCBZ 0x7c0007ec#endif /* __ASM_KVM_BOOK3S_H__ */
arch/powerpc/include/asm/kvm_host.h +2 -0
@@ -273,6 +273,8 @@ struct kvm_vcpu_arch {u8 mmio_sign_extend;u8 dcr_needed;u8 dcr_is_write; +u8 osi_needed; +u8 osi_enabled;u32 cpr0_cfgaddr;/* holds the last set cpr0_cfgaddr */
arch/powerpc/kvm/book3s.c +18 -6
@@ -871,12 +871,24 @@ program_interrupt:break ; }case BOOK3S_INTERRUPT_SYSCALL : -#ifdef EXIT_DEBUG -printk (KERN_INFO "Syscall Nr %d\n" , (int )kvmppc_get_gpr (vcpu,0 )); -#endif - vcpu->stat.syscall_exits++; -kvmppc_book3s_queue_irqprio (vcpu, exit_nr); - r =RESUME_GUEST ; +// XXX make user settable +if (vcpu->arch.osi_enabled && + (((u32 )kvmppc_get_gpr (vcpu,3 )) ==OSI_SC_MAGIC_R3 ) && + (((u32 )kvmppc_get_gpr (vcpu,4 )) ==OSI_SC_MAGIC_R4 )) { +u64 *gprs = run->osi.gprs; +int i; + + run->exit_reason =KVM_EXIT_OSI ; +for (i =0 ; i <32 ; i++) + gprs[i] =kvmppc_get_gpr (vcpu, i); + vcpu->arch.osi_needed =1 ; + r =RESUME_HOST_NV ; + + }else { + vcpu->stat.syscall_exits++; +kvmppc_book3s_queue_irqprio (vcpu, exit_nr); + r =RESUME_GUEST ; + }break ;case BOOK3S_INTERRUPT_FP_UNAVAIL :case BOOK3S_INTERRUPT_ALTIVEC :
arch/powerpc/kvm/powerpc.c +12 -0
@@ -148,6 +148,7 @@ int kvm_dev_ioctl_check_extension(long ext)switch (ext) {case KVM_CAP_PPC_SEGSTATE :case KVM_CAP_PPC_PAIRED_SINGLES : +case KVM_CAP_PPC_OSI : r =1 ;break ;case KVM_CAP_COALESCED_MMIO :
@@ -429,6 +430,13 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu, struct kvm_run *run)if (!vcpu->arch.dcr_is_write)kvmppc_complete_dcr_load (vcpu, run); vcpu->arch.dcr_needed =0 ; + }else if (vcpu->arch.osi_needed) { +u64 *gprs = run->osi.gprs; +int i; + +for (i =0 ; i <32 ; i++) +kvmppc_set_gpr (vcpu, i, gprs[i]); + vcpu->arch.osi_needed =0 ; }kvmppc_core_deliver_interrupts (vcpu);
@@ -471,6 +479,10 @@ static int kvm_vcpu_ioctl_enable_cap(struct kvm_vcpu *vcpu,return -EINVAL ;switch (cap->cap) { +case KVM_CAP_PPC_OSI : + r =0 ; + vcpu->arch.osi_enabled = true; +break ;default : r = -EINVAL ;break ;
include/linux/kvm.h +6 -0
@@ -160,6 +160,7 @@ struct kvm_pit_config {#define KVM_EXIT_DCR 15#define KVM_EXIT_NMI 16#define KVM_EXIT_INTERNAL_ERROR 17 +#define KVM_EXIT_OSI 18/* For KVM_EXIT_INTERNAL_ERROR */ #define KVM_INTERNAL_ERROR_EMULATION 1
@@ -259,6 +260,10 @@ struct kvm_run {__u32 ndata;__u64 data[16 ]; } internal; +/* KVM_EXIT_OSI */ +struct { +__u64 gprs[32 ]; + } osi;/* Fix the size of the union. */ char padding[256 ]; };
@@ -516,6 +521,7 @@ struct kvm_enable_cap {#define KVM_CAP_DEBUGREGS 50#endif #define KVM_CAP_X86_ROBUST_SINGLESTEP 51 +#define KVM_CAP_PPC_OSI 52#ifdef KVM_CAP_IRQ_ROUTING
Signature · 1 line
1.6.0.2
Re: [PATCH 14/15] KVM: PPC: Add OSI hypercall interface
Quoted 36 lines · Alexander Graf
MOL uses its own hypercall interface to call back into userspace when the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to.
The only user of it so far is MOL.
Signed-off-by Alexander Graf<[email protected]>---
v1 -> v2:
- Add documentation for OSI exit struct
--- Documentation/kvm/api.txt | 13 +++++++++++++ arch/powerpc/include/asm/kvm_book3s.h | 5 +++++ arch/powerpc/include/asm/kvm_host.h | 2 ++ arch/powerpc/kvm/book3s.c | 24 ++++++++++++++++++------ arch/powerpc/kvm/powerpc.c | 12 ++++++++++++ include/linux/kvm.h | 6 ++++++ 6 files changed, 56 insertions(+), 6 deletions(-)Documentation/kvm/api.txt +4
-0@@ -932,6 +932,19 @@ s390 specific. powerpc specific. + /* KVM_EXIT_OSI */ + struct { + __u64 gprs[32]; + } osi;
Documentation/kvm/api.txt s390 specific. · line 948
Quoted 10 lines
Documentation/kvm/api.txt +9
-0+ +MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch +hypercalls and exit with this exit struct that contains all the guest gprs. + +If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall. +Userspace can now handle the hypercall and when it's done modify the gprs as +necessary. Upon guest entry all guest GPRs will then be replaced by the values +in this struct. +
That's migration unsafe. There may not be next guest entry on this host.
Is using KVM_[GS]ET_REGS problematic for some reason?
Signature · 1 line
error compiling committee.c: too many arguments to function
Re: [PATCH 14/15] KVM: PPC: Add OSI hypercall interface
Quoted 33 lines · Avi Kivity
Quoted 32 lines · Alexander Graf
MOL uses its own hypercall interface to call back into userspace when the guest wants to do something.
So let's implement that as an exit reason, specify it with a CAP and only really use it when userspace wants us to.
The only user of it so far is MOL.
Signed-off-by Alexander Graf<[email protected]>---
v1 -> v2:
- Add documentation for OSI exit struct
--- Documentation/kvm/api.txt | 13 +++++++++++++ arch/powerpc/include/asm/kvm_book3s.h | 5 +++++ arch/powerpc/include/asm/kvm_host.h | 2 ++ arch/powerpc/kvm/book3s.c | 24 ++++++++++++++++++------ arch/powerpc/kvm/powerpc.c | 12 ++++++++++++ include/linux/kvm.h | 6 ++++++ 6 files changed, 56 insertions(+), 6 deletions(-)Documentation/kvm/api.txt +0
-0@@ -932,6 +932,19 @@ s390 specific. powerpc specific.
Quoted 16 lines
Quoted 4 lines
Documentation/kvm/api.txt +4
-0+ /* KVM_EXIT_OSI */ + struct { + __u64 gprs[32]; + } osi;Documentation/kvm/api.txt s390 specific.
Quoted 10 lines
Documentation/kvm/api.txt +9
-0+ +MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch +hypercalls and exit with this exit struct that contains all the guest gprs. + +If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall. +Userspace can now handle the hypercall and when it's done modify the gprs as +necessary. Upon guest entry all guest GPRs will then be replaced by the values +in this struct. +That's migration unsafe. There may not be next guest entry on this host.
It's as unsafe as MMIO then.
Quoted 1 line
Is using KVM_[GS]ET_REGS problematic for some reason?
It's two additional ioctls for no good reason. We know the interface, so we can model towards it.
Alex
Re: [PATCH 14/15] KVM: PPC: Add OSI hypercall interface
Quoted 18 lines · Alexander Graf
Quoted 18 lines
Quoted 6 lines
Documentation/kvm/api.txt +3
-0+ /* KVM_EXIT_OSI */ + struct { + __u64 gprs[32];Documentation/kvm/api.txt s390 specific. · line 947
Quoted 10 lines
Documentation/kvm/api.txt +10
-0+ } osi; + +MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch +hypercalls and exit with this exit struct that contains all the guest gprs. + +If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall. +Userspace can now handle the hypercall and when it's done modify the gprs as +necessary. Upon guest entry all guest GPRs will then be replaced by the values +in this struct. +That's migration unsafe. There may not be next guest entry on this host.
Quoted 3 lines
It's as unsafe as MMIO then.
From api.txt:
Quoted 8 lines
NOTE: For
KVM_EXIT_IOandKVM_EXIT_MMIO, the corresponding operations are complete (and guest state is consistent) only after userspace has re-entered the kernel withKVM_RUN. The kernel side will first finish incomplete operations and then check for pending signals. Userspace can re-enter the guest with an unmasked signal pending to complete pending operations.
Quoted 4 lines
Quoted 2 lines
Is using KVM_[GS]ET_REGS problematic for some reason?
It's two additional ioctls for no good reason. We know the interface, so we can model towards it.
But we need to be migration safe. If the interface is not heavily used, let's not add complications.
Signature · 1 line
error compiling committee.c: too many arguments to function
Re: [PATCH 14/15] KVM: PPC: Add OSI hypercall interface
Quoted 19 lines · Avi Kivity
Quoted 18 lines · Alexander Graf
Quoted 18 lines
Quoted 6 lines
Documentation/kvm/api.txt +3
-0+ /* KVM_EXIT_OSI */ + struct { + __u64 gprs[32];Documentation/kvm/api.txt s390 specific. · line 947
Quoted 10 lines
Documentation/kvm/api.txt +10
-0+ } osi; + +MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch +hypercalls and exit with this exit struct that contains all the guest gprs. + +If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall. +Userspace can now handle the hypercall and when it's done modify the gprs as +necessary. Upon guest entry all guest GPRs will then be replaced by the values +in this struct. +That's migration unsafe. There may not be next guest entry on this host.
Quoted 13 lines
Quoted 3 lines
It's as unsafe as MMIO then.
From api.txt:
Quoted 6 lines
NOTE: For
KVM_EXIT_IOandKVM_EXIT_MMIO, the corresponding operations are complete (and guest state is consistent) only after userspace has re-entered the kernel withKVM_RUN. The kernel side will first finish incomplete operations and then check for pending signals. Userspace can re-enter the guest with an unmasked signal pending to complete pending operations.
Alright - so I add KVM_EXIT_OSI there and be good? :)
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
Is using KVM_[GS]ET_REGS problematic for some reason?
It's two additional ioctls for no good reason. We know the interface, so we can model towards it.
But we need to be migration safe. If the interface is not heavily used, let's not add complications.
MOL uses OSI calls instead of MMIO. So yes, it is heavily used.
Alex
A message that is not in the archive (sent off-list or not yet received): 3D0D6963-FEC8-4A53-ACCE-570BEAF3721B-l3A5Bk7waGM@public.gmane.org
Re: [PATCH 14/15] KVM: PPC: Add OSI hypercall interface
Quoted 40 lines · Alexander Graf
Quoted 22 lines · Avi Kivity
Quoted 20 lines · Alexander Graf
Quoted 20 lines
Quoted 7 lines
Documentation/kvm/api.txt +3
-0+ /* KVM_EXIT_OSI */ + struct { + __u64 gprs[32];Documentation/kvm/api.txt s390 specific. · line 947
Quoted 10 lines
Documentation/kvm/api.txt +10
-0+ } osi; + +MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch +hypercalls and exit with this exit struct that contains all the guest gprs. + +If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall. +Userspace can now handle the hypercall and when it's done modify the gprs as +necessary. Upon guest entry all guest GPRs will then be replaced by the values +in this struct. +That's migration unsafe. There may not be next guest entry on this host.
Quoted 15 lines
Quoted 4 lines
It's as unsafe as MMIO then.
From api.txt:
Quoted 7 lines
NOTE: For
KVM_EXIT_IOandKVM_EXIT_MMIO, the corresponding operations are complete (and guest state is consistent) only after userspace has re-entered the kernel withKVM_RUN. The kernel side will first finish incomplete operations and then check for pending signals. Userspace can re-enter the guest with an unmasked signal pending to complete pending operations.
Quoted 2 lines
Alright - so I add
KVM_EXIT_OSIthere and be good? :)
Sure, just verify that the note holds for that case too.
Quoted 5 lines
Quoted 2 lines
But we need to be migration safe. If the interface is not heavily used, let's not add complications.
MOL uses OSI calls instead of MMIO. So yes, it is heavily used.
Ok.
Signature · 1 line
error compiling committee.c: too many arguments to function
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [PATCH 14/15] KVM: PPC: Add OSI hypercall interface
Quoted 41 lines · Avi Kivity
Quoted 40 lines · Alexander Graf
Quoted 37 lines · Avi Kivity
Quoted 20 lines · Alexander Graf
Quoted 10 lines
Quoted 10 lines
(quoted diff) +9
-0+ /* KVM_EXIT_OSI */ + struct { + __u64 gprs[32]; + } osi; + +MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch +hypercalls and exit with this exit struct that contains all the guest gprs. + +If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall.Quoted 10 lines
Review
Quoted 7 lines
(quoted diff) +4
-0+Userspace can now handle the hypercall and when it's done modify the gprs as +necessary. Upon guest entry all guest GPRs will then be replaced by the values +in this struct. +That's migration unsafe. There may not be next guest entry on this host.
Quoted 4 lines
It's as unsafe as MMIO then.
From api.txt:
Quoted 7 lines
NOTE: For
KVM_EXIT_IOandKVM_EXIT_MMIO, the corresponding operations are complete (and guest state is consistent) only after userspace has re-entered the kernel withKVM_RUN. The kernel side will first finish incomplete operations and then check for pending signals. Userspace can re-enter the guest with an unmasked signal pending to complete pending operations.
Quoted 4 lines
Quoted 2 lines
Alright - so I add
KVM_EXIT_OSIthere and be good? :)Sure, just verify that the note holds for that case too.
The handling of the hypercall write-back is in the same region as the mmio one. So whatever applies for MMIO entries applies for OSI entries too.
Alex--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
PATCH 15/15 KVM: PPC: Make build work without CONFIG_VSX/ALTIVEC
In reply to a message not in the archiveThe FPU/Altivec/VSX enablement also brought access to some structure elements that are only defined when the respective config options are enabled.
Unfortuately I forgot to check for the config options at some places, so let's do that now.
Unbreaks the build when CONFIG_VSX is not set.
--- arch/powerpc/kvm/book3s.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
arch/powerpc/kvm/book3s.c +8 -0
@@ -608,7 +608,9 @@ void kvmppc_giveup_ext(struct kvm_vcpu *vcpu, ulong msr) {struct thread_struct *t = ¤t->thread;u64 *vcpu_fpr = vcpu->arch.fpr; +#ifdef CONFIG_VSX u64 *vcpu_vsx = vcpu->arch.vsr; +#endif u64 *thread_fpr = (u64 *)t->fpr;int i;
@@ -688,7 +690,9 @@ static int kvmppc_handle_ext(struct kvm_vcpu *vcpu, unsigned int exit_nr, {struct thread_struct *t = ¤t->thread;u64 *vcpu_fpr = vcpu->arch.fpr; +#ifdef CONFIG_VSX u64 *vcpu_vsx = vcpu->arch.vsr; +#endif u64 *thread_fpr = (u64 *)t->fpr;int i;
@@ -1218,8 +1222,12 @@ int __kvmppc_vcpu_run(struct kvm_run *kvm_run, struct kvm_vcpu *vcpu) {int ret;struct thread_struct ext_bkp; +#ifdef CONFIG_ALTIVEC bool save_vec = current->thread.used_vr; +#endif +#ifdef CONFIG_VSX bool save_vsx = current->thread.used_vsr; +#endif ulong ext_msr;/* No need to go into the guest when all we do is going out */
Signature · 1 line
1.6.0.2
PATCH 2/15 KVM: PPC: Allow userspace to unset the IRQ line
In reply to Alexander GrafUserspace can tell us that it wants to trigger an interrupt. But so far it can't tell us that it wants to stop triggering one.
So let's interpret the parameter to the ioctl that we have anyways to tell us if we want to raise or lower the interrupt line.
--- arch/powerpc/include/asm/kvm.h | 3 +++ arch/powerpc/include/asm/kvm_ppc.h | 2 ++ arch/powerpc/kvm/book3s.c | 6 ++++++ arch/powerpc/kvm/powerpc.c | 5 ++++- 4 files changed, 15 insertions(+), 1 deletions(-)
arch/powerpc/include/asm/kvm.h +3 -0
@@ -84,4 +84,7 @@ struct kvm_guest_debug_arch {#define KVM_REG_QPR 0x0040#define KVM_REG_FQPR 0x0060 +#define KVM_INTERRUPT_SET -1U +#define KVM_INTERRUPT_UNSET -2U +#endif /* __LINUX_KVM_POWERPC_H */
arch/powerpc/include/asm/kvm_ppc.h +2 -0
@@ -92,6 +92,8 @@ extern void kvmppc_core_queue_dec(struct kvm_vcpu *vcpu);extern void kvmppc_core_dequeue_dec (struct kvm_vcpu *vcpu);extern void kvmppc_core_queue_external (struct kvm_vcpu *vcpu,struct kvm_interrupt *irq); +extern void kvmppc_core_dequeue_external (struct kvm_vcpu *vcpu, +struct kvm_interrupt *irq);extern int kvmppc_core_emulate_op (struct kvm_run *run,struct kvm_vcpu *vcpu,unsigned int op,int *advance);
arch/powerpc/kvm/book3s.c +6 -0
@@ -230,6 +230,12 @@ void kvmppc_core_queue_external(struct kvm_vcpu *vcpu,kvmppc_book3s_queue_irqprio (vcpu,BOOK3S_INTERRUPT_EXTERNAL ); } +void kvmppc_core_dequeue_external (struct kvm_vcpu *vcpu, +struct kvm_interrupt *irq) +{ +kvmppc_book3s_dequeue_irqprio (vcpu,BOOK3S_INTERRUPT_EXTERNAL ); +} +int kvmppc_book3s_irqprio_deliver (struct kvm_vcpu *vcpu,unsigned int priority) {int deliver =1 ;
arch/powerpc/kvm/powerpc.c +4 -1
@@ -449,7 +449,10 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu, struct kvm_run *run)int kvm_vcpu_ioctl_interrupt (struct kvm_vcpu *vcpu,struct kvm_interrupt *irq) { -kvmppc_core_queue_external (vcpu, irq); +if (irq->irq =KVM_INTERRUPT_UNSET ) +kvmppc_core_dequeue_external (vcpu, irq); +else +kvmppc_core_queue_external (vcpu, irq);if (waitqueue_active (&vcpu->wq)) {wake_up_interruptible (&vcpu->wq);
Signature · 1 line
1.6.0.2
A message that is not in the archive (sent off-list or not yet received): 1268071402-27112-3-git-send-email-agraf-l3A5Bk7waGM@public.gmane.org
Re: [PATCH 02/15] KVM: PPC: Allow userspace to unset the IRQ line
Quoted 6 lines · Alexander Graf
Userspace can tell us that it wants to trigger an interrupt. But so far it can't tell us that it wants to stop triggering one.
So let's interpret the parameter to the ioctl that we have anyways to tell us if we want to raise or lower the interrupt line.
I asked for a KVM_CAP_ for this. What was the conclusion of that thread?
Signature · 1 line
error compiling committee.c: too many arguments to function
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [PATCH 02/15] KVM: PPC: Allow userspace to unset the IRQ line
Quoted 9 lines · Avi Kivity
Quoted 6 lines · Alexander Graf
Userspace can tell us that it wants to trigger an interrupt. But so far it can't tell us that it wants to stop triggering one.
So let's interpret the parameter to the ioctl that we have anyways to tell us if we want to raise or lower the interrupt line.
I asked for a
KVM_CAP_for this. What was the conclusion of that thread?
Uh - did we come to one?
The last thing you said about it was:
Quoted 3 lines
Having individual capabilities makes backporting a lot easier (otherwise you have to backport the whole thing). If the changes are logically separate, I prefer 500 separate capabilities.
However, for a platform bringup, it's okay to have just one capability, assuming none of the changes are applicable to other platforms.
So I assumed it'd be ok to not have one. If you like I can send an additional patch adding the CAP.
Alex--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 954C5195-A8E4-4CA5-8D5E-AA21E2E21C5B-l3A5Bk7waGM@public.gmane.org
Re: [PATCH 02/15] KVM: PPC: Allow userspace to unset the IRQ line
Quoted 16 lines · Alexander Graf
Quoted 11 lines · Avi Kivity
Quoted 7 lines · Alexander Graf
Userspace can tell us that it wants to trigger an interrupt. But so far it can't tell us that it wants to stop triggering one.
So let's interpret the parameter to the ioctl that we have anyways to tell us if we want to raise or lower the interrupt line.
I asked for a
KVM_CAP_for this. What was the conclusion of that thread?Uh - did we come to one?
Quoted 10 lines
The last thing you said about it was:
Quoted 4 lines
Having individual capabilities makes backporting a lot easier (otherwise you have to backport the whole thing). If the changes are logically separate, I prefer 500 separate capabilities.
However, for a platform bringup, it's okay to have just one capability, assuming none of the changes are applicable to other platforms.
So I assumed it'd be ok to not have one. If you like I can send an additional patch adding the CAP.
Well, what's the capability for this patchset?
Things like "if you have KVM_CAP_OSI you can assume you have KVM_INTERRUPT_LOWER" don't work for me. A platform cap would be called KVM_CAP_MOL and explicitly document everything in there.
And it commits you to not deprecating things individually. Really, individual caps are better.
Signature · 1 line
error compiling committee.c: too many arguments to function
PATCH 4/15 KVM: PPC: Book3S_32 guest MMU fixes
In reply to Alexander GrafThis patch makes the VSID of mapped pages always reflecting all special cases we have, like split mode.
It also changes the tlbie mask to 0x0ffff000 according to the spec. The mask we used before was incorrect.
--- arch/powerpc/include/asm/kvm_book3s.h | 1 + arch/powerpc/kvm/book3s_32_mmu.c | 30 +++++++++++++++++++++++------- 2 files changed, 24 insertions(+), 7 deletions(-)
arch/powerpc/include/asm/kvm_book3s.h +1 -0
@@ -44,6 +44,7 @@ struct kvmppc_sr {bool Ks;bool Kp;bool nx; +bool valid; };struct kvmppc_bat {
arch/powerpc/kvm/book3s_32_mmu.c +23 -7
@@ -57,6 +57,8 @@ static inline bool check_debug_ip(struct kvm_vcpu *vcpu)static int kvmppc_mmu_book3s_32_xlate_bat (struct kvm_vcpu *vcpu,gva_t eaddr,struct kvmppc_pte *pte,bool data); +static int kvmppc_mmu_book3s_32_esid_to_vsid (struct kvm_vcpu *vcpu,u64 esid, +u64 *vsid);static struct kvmppc_sr *find_sr (struct kvmppc_vcpu_book3s *vcpu_book3s,gva_t eaddr) {
@@ -66,13 +68,14 @@ static struct kvmppc_sr *find_sr(struct kvmppc_vcpu_book3s *vcpu_book3s, gva_t estatic u64 kvmppc_mmu_book3s_32_ea_to_vp (struct kvm_vcpu *vcpu,gva_t eaddr,bool data) { -struct kvmppc_sr *sre =find_sr (to_book3s (vcpu), eaddr); +u64 vsid;struct kvmppc_pte pte;if (!kvmppc_mmu_book3s_32_xlate_bat (vcpu, eaddr, &pte, data))return pte.vpage; -return (((u64 )eaddr >>12 ) &0xffff ) | (((u64 )sre->vsid) <<16 ); +kvmppc_mmu_book3s_32_esid_to_vsid (vcpu, eaddr >>SID_SHIFT , &vsid); +return (((u64 )eaddr >>12 ) &0xffff ) | (vsid <<16 ); }static void kvmppc_mmu_book3s_32_reset_msr (struct kvm_vcpu *vcpu)
@@ -142,8 +145,13 @@ static int kvmppc_mmu_book3s_32_xlate_bat(struct kvm_vcpu *vcpu, gva_t eaddr, bat->bepi_mask); }if ((eaddr & bat->bepi_mask) = bat->bepi) { +u64 vsid; +kvmppc_mmu_book3s_32_esid_to_vsid (vcpu, + eaddr >>SID_SHIFT , &vsid); + vsid <<=16 ; + pte->vpage = (((u64 )eaddr >>12 ) &0xffff ) | vsid; + pte->raddr = bat->brpn | (eaddr & ~bat->bepi_mask); - pte->vpage = (eaddr >>12 ) |VSID_BAT ; pte->may_read = bat->pp; pte->may_write = bat->pp >1 ; pte->may_execute = true;
@@ -302,6 +310,7 @@ static void kvmppc_mmu_book3s_32_mtsrin(struct kvm_vcpu *vcpu, u32 srnum,/* And then put in the new SR */ sre->raw = value; sre->vsid = (value &0x0fffffff ); + sre->valid = (value &0x80000000 ) ? false : true; sre->Ks = (value &0x40000000 ) ? true : false; sre->Kp = (value &0x20000000 ) ? true : false; sre->nx = (value &0x10000000 ) ? true : false;
@@ -312,7 +321,7 @@ static void kvmppc_mmu_book3s_32_mtsrin(struct kvm_vcpu *vcpu, u32 srnum,static void kvmppc_mmu_book3s_32_tlbie (struct kvm_vcpu *vcpu,ulong ea,bool large) { -kvmppc_mmu_pte_flush (vcpu, ea, ~0xFFFULL ); +kvmppc_mmu_pte_flush (vcpu, ea,0x0FFFF000 ); } static int kvmppc_mmu_book3s_32_esid_to_vsid(struct kvm_vcpu *vcpu, u64 esid,
@@ -333,15 +342,22 @@ static int kvmppc_mmu_book3s_32_esid_to_vsid(struct kvm_vcpu *vcpu, u64 esid,break ;case MSR_DR |MSR_IR : { -ulong ea; - ea = esid <<SID_SHIFT ; - *vsid =find_sr (to_book3s (vcpu), ea)->vsid; +ulong ea = esid <<SID_SHIFT ; +struct kvmppc_sr *sr =find_sr (to_book3s (vcpu), ea); + +if (!sr->valid) +return -1 ; + + *vsid = sr->vsid;break ; }default :BUG (); } +if (vcpu->arch.msr &MSR_PR ) + *vsid |=VSID_PR ; +return 0 ; }
Signature · 1 line
1.6.0.2
PATCH 6/15 KVM: PPC: Don't reload FPU with invalid values
In reply to Alexander GrafWhen the guest activates the FPU, we load it up. That's fine when it wasn't activated before on the host, but if it was we end up reloading FPU values from last time the FPU was deactivated on the host without writing the proper values back to the vcpu struct.
This patch checks if the FPU is enabled already and if so just doesn't bother activating it, making FPU operations survive guest context switches.
--- arch/powerpc/kvm/book3s.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-)
arch/powerpc/kvm/book3s.c +5 -0
@@ -701,6 +701,11 @@ static int kvmppc_handle_ext(struct kvm_vcpu *vcpu, unsigned int exit_nr,return RESUME_GUEST ; } +/* We already own the ext */ +if (vcpu->arch.guest_owned_ext & msr) { +return RESUME_GUEST ; + } +#ifdef DEBUG_EXT printk (KERN_INFO "Loading up ext 0x%lx\n" , msr);#endif
Signature · 1 line
1.6.0.2
PATCH 9/15 KVM: PPC: Implement BAT reads
In reply to Alexander GrafBATs can't only be written to, you can also read them out! So let's implement emulation for reading BAT values again.
While at it, I also made BAT setting flush the segment cache, so we're absolutely sure there's no MMU state left when writing BATs.
--- arch/powerpc/kvm/book3s_64_emulate.c | 35 ++++++++++++++++++++++++++++++++++ 1 files changed, 35 insertions(+), 0 deletions(-)
arch/powerpc/kvm/book3s_64_emulate.c +35 -0
@@ -239,6 +239,34 @@ void kvmppc_set_bat(struct kvm_vcpu *vcpu, struct kvmppc_bat *bat, bool upper, } } +static u32 kvmppc_read_bat (struct kvm_vcpu *vcpu,int sprn) +{ +struct kvmppc_vcpu_book3s *vcpu_book3s =to_book3s (vcpu); +struct kvmppc_bat *bat; + +switch (sprn) { + case SPRN_IBAT0U ... SPRN_IBAT3L: + bat = &vcpu_book3s->ibat[(sprn -SPRN_IBAT0U ) /2 ]; +break ; + case SPRN_IBAT4U ... SPRN_IBAT7L: + bat = &vcpu_book3s->ibat[4 + ((sprn -SPRN_IBAT4U ) /2 )]; +break ; + case SPRN_DBAT0U ... SPRN_DBAT3L: + bat = &vcpu_book3s->dbat[(sprn -SPRN_DBAT0U ) /2 ]; +break ; + case SPRN_DBAT4U ... SPRN_DBAT7L: + bat = &vcpu_book3s->dbat[4 + ((sprn -SPRN_DBAT4U ) /2 )]; +break ; +default : +BUG (); + } + +if (sprn %2 ) +return bat->raw >>32 ; +else +return bat->raw; +} +static void kvmppc_write_bat (struct kvm_vcpu *vcpu,int sprn,u32 val) {struct kvmppc_vcpu_book3s *vcpu_book3s =to_book3s (vcpu);
@@ -290,6 +318,7 @@ int kvmppc_core_emulate_mtspr(struct kvm_vcpu *vcpu, int sprn, int rs)/* BAT writes happen so rarely that we're ok to flush * everything here */ kvmppc_mmu_pte_flush (vcpu,0 ,0 ); +kvmppc_mmu_flush_segments (vcpu);break ;case SPRN_HID0 :to_book3s (vcpu)->hid[0 ] = spr_val;
@@ -373,6 +402,12 @@ int kvmppc_core_emulate_mfspr(struct kvm_vcpu *vcpu, int sprn, int rt)int emulated =EMULATE_DONE ;switch (sprn) { + case SPRN_IBAT0U ... SPRN_IBAT3L: + case SPRN_IBAT4U ... SPRN_IBAT7L: + case SPRN_DBAT0U ... SPRN_DBAT3L: + case SPRN_DBAT4U ... SPRN_DBAT7L: +kvmppc_set_gpr (vcpu, rt,kvmppc_read_bat (vcpu, sprn)); +break ;case SPRN_SDR1 :kvmppc_set_gpr (vcpu, rt,to_book3s (vcpu)->sdr1);break ;
Signature · 1 line
1.6.0.2
PATCH 10/15 KVM: PPC: Make XER load 32 bit
In reply to Alexander GrafWe have a 32 bit value in the PACA to store XER in. We also do an stw when storing XER in there. But then we load it with ld, completely screwing it up on every entry.
Welcome to the Big Endian world.
--- arch/powerpc/kvm/book3s_64_slb.S | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
arch/powerpc/kvm/book3s_64_slb.S +1 -1
@@ -145,7 +145,7 @@ slb_do_enter: lwz r11, (PACA_KVM_CR)(r13) mtcr r11 - ld r11, (PACA_KVM_XER)(r13) + lwz r11, (PACA_KVM_XER)(r13) mtxer r11 ld r11, (PACA_KVM_R11)(r13)
Signature · 1 line
1.6.0.2
PATCH 11/15 KVM: PPC: Implement emulation for lbzux and lhax
In reply to Alexander GrafWe get MMIOs with the weirdest instructions. But every time we do, we need to improve our emulator to implement them.
So let's do that - this time it's lbzux and lhax's round.
--- arch/powerpc/kvm/emulate.c | 20 ++++++++++++++++++++ 1 files changed, 20 insertions(+), 0 deletions(-)
arch/powerpc/kvm/emulate.c +20 -0
@@ -38,10 +38,12 @@#define OP_31_XOP_LBZX 87#define OP_31_XOP_STWX 151#define OP_31_XOP_STBX 215 +#define OP_31_XOP_LBZUX 119#define OP_31_XOP_STBUX 247#define OP_31_XOP_LHZX 279#define OP_31_XOP_LHZUX 311#define OP_31_XOP_MFSPR 339 +#define OP_31_XOP_LHAX 343#define OP_31_XOP_STHX 407#define OP_31_XOP_STHUX 439#define OP_31_XOP_MTSPR 467
@@ -173,6 +175,19 @@ int kvmppc_emulate_instruction(struct kvm_run *run, struct kvm_vcpu *vcpu) emulated =kvmppc_handle_load (run, vcpu, rt,1 ,1 );break ; +case OP_31_XOP_LBZUX : + rt =get_rt (inst); + ra =get_ra (inst); + rb =get_rb (inst); + + ea =kvmppc_get_gpr (vcpu, rb); +if (ra) + ea +=kvmppc_get_gpr (vcpu, ra); + + emulated =kvmppc_handle_load (run, vcpu, rt,1 ,1 ); +kvmppc_set_gpr (vcpu, ra, ea); +break ; +case OP_31_XOP_STWX : rs =get_rs (inst); emulated = kvmppc_handle_store(run, vcpu,
@@ -202,6 +217,11 @@ int kvmppc_emulate_instruction(struct kvm_run *run, struct kvm_vcpu *vcpu)kvmppc_set_gpr (vcpu, rs, ea);break ; +case OP_31_XOP_LHAX : + rt =get_rt (inst); + emulated =kvmppc_handle_loads (run, vcpu, rt,2 ,1 ); +break ; +case OP_31_XOP_LHZX : rt =get_rt (inst); emulated =kvmppc_handle_load (run, vcpu, rt,2 ,1 );
Signature · 1 line
1.6.0.2
Quoted 9 lines · Alexander Graf
Mac-on-Linux has always lacked PPC64 host support. This is going to change now!
This patchset contains minor patches to enable MOL, but is mostly about bug fixes that came out of running Mac OS X. With this set and a pretty small patch to MOL I have 10.4.11 running as a guest on a 970MP host.
I'll send the MOl patches to the respective ML in the next days.
The patches for MOL are integrated in their SVN already. Forgot to change the description.
Alex