From: Christoffer Dall <christoffer.dall@linaro.org> To: Dave Martin <Dave.Martin@arm.com> Cc: Marc Zyngier <marc.zyngier@arm.com>, Shih-Wei Li <shihwei@cs.columbia.edu>, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org Subject: Re: [PATCH v3 09/41] KVM: arm64: Defer restoring host VFP state to vcpu_put Date: Thu, 25 Jan 2018 20:46:53 +0100 [thread overview] Message-ID: <20180125194653.GR21802@cbox> (raw) In-Reply-To: <20180122173326.GO22781@e103592.cambridge.arm.com> On Mon, Jan 22, 2018 at 05:33:28PM +0000, Dave Martin wrote: > On Fri, Jan 12, 2018 at 01:07:15PM +0100, Christoffer Dall wrote: > > Avoid saving the guest VFP registers and restoring the host VFP > > registers on every exit from the VM. Only when we're about to run > > userspace or other threads in the kernel do we really have to switch the > > state back to the host state. > > > > We still initially configure the VFP registers to trap when entering the > > VM, but the difference is that we now leave the guest state in the > > hardware registers as long as we're running this VCPU, even if we > > occasionally trap to the host, and we only restore the host state when > > we return to user space or when scheduling another thread. > > > > Reviewed-by: Andrew Jones <drjones@redhat.com> > > Reviewed-by: Marc Zyngier <marc.zyngier@arm.com> > > Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org> > > [...] > > > diff --git a/arch/arm64/kvm/hyp/sysreg-sr.c b/arch/arm64/kvm/hyp/sysreg-sr.c > > index 883a6383cd36..848a46eb33bf 100644 > > --- a/arch/arm64/kvm/hyp/sysreg-sr.c > > +++ b/arch/arm64/kvm/hyp/sysreg-sr.c > > [...] > > > @@ -213,6 +215,19 @@ void kvm_vcpu_load_sysregs(struct kvm_vcpu *vcpu) > > */ > > void kvm_vcpu_put_sysregs(struct kvm_vcpu *vcpu) > > { > > + struct kvm_cpu_context *host_ctxt = vcpu->arch.host_cpu_context; > > + struct kvm_cpu_context *guest_ctxt = &vcpu->arch.ctxt; > > + > > + /* Restore host FP/SIMD state */ > > + if (vcpu->arch.guest_vfp_loaded) { > > + if (vcpu_el1_is_32bit(vcpu)) { > > + kvm_call_hyp(__fpsimd32_save_state, > > + kern_hyp_va(guest_ctxt)); > > + } > > + __fpsimd_save_state(&guest_ctxt->gp_regs.fp_regs); > > + __fpsimd_restore_state(&host_ctxt->gp_regs.fp_regs); > > + vcpu->arch.guest_vfp_loaded = 0; > > Provided we've already marked the host FPSIMD state as dirty on the way > in, we probably don't need to restore it here. > > In v4.15, the kvm_fpsimd_flush_cpu_state() call in > kvm_arch_vcpu_ioctl_run() is supposed to do this marking: currently > it's only done for SVE, since KVM was previously restoring the host > FPSIMD subset of the state anyway, but it could be made unconditional. > > For a returning run ioctl, this would have the effect of deferring the > host FPSIMD reload until we return to userspace, which is probably > no more costly since the kernel must check whether to do this in > ret_to_user anyway; OTOH if the vcpu thread was preempted by some > other thread we save the cost of restoring the host state entirely here > ... I think. Yes, I agree. However, currently the low-level logic in arch/arm64/kvm/hyp/entry.S:__fpsimd_guest_restore which saves the host state into vcpu->arch.host_cpu_context->gp_regs.fp_regs (where host_cpu_context is a KVM-specific per-cpu variable). I think means that simply marking the state as invalid would cause the kernel to restore some potentially stale values when returning to userspace. Am I missing something? It might very well be possible to change the logic so that we store the host logic the same place where task_fpsimd_save() would have, and I think that would make what you suggest possible. I'd like to make that a separate change from this patch though, as we're already changing quite a bit with this series, so I'm trying to make any logical change as contained per patch as possible, so that problems can be spotted by bisecting. > > Ultimately I'd like to go one better and actually treat a vcpu as a > first-class fpsimd context, so that taking an interrupt to the host > and then reentering the guest doesn't cause any reload at all. That should be the case already; kvm_vcpu_put_sysregs() is only called when you run another thread (preemptively or voluntarily), or when you return to user space, but making the vcpu fpsimd context a first-class citizen fpsimd context would mean that you can run another thread (and maybe run userspace if it doesn't use fpsimd?) without having to save/restore anything. Am I getting this right? > But > that feels like too big a step for this series, and there are likely > side-issues I've not thought about yet. > It should definitely be in separate patches, but I would be optn to tagging something on to the end of this series if we can stabilize this series early after -rc1 is out. Thanks, -Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 09/41] KVM: arm64: Defer restoring host VFP state to vcpu_put Date: Thu, 25 Jan 2018 20:46:53 +0100 [thread overview] Message-ID: <20180125194653.GR21802@cbox> (raw) In-Reply-To: <20180122173326.GO22781@e103592.cambridge.arm.com> On Mon, Jan 22, 2018 at 05:33:28PM +0000, Dave Martin wrote: > On Fri, Jan 12, 2018 at 01:07:15PM +0100, Christoffer Dall wrote: > > Avoid saving the guest VFP registers and restoring the host VFP > > registers on every exit from the VM. Only when we're about to run > > userspace or other threads in the kernel do we really have to switch the > > state back to the host state. > > > > We still initially configure the VFP registers to trap when entering the > > VM, but the difference is that we now leave the guest state in the > > hardware registers as long as we're running this VCPU, even if we > > occasionally trap to the host, and we only restore the host state when > > we return to user space or when scheduling another thread. > > > > Reviewed-by: Andrew Jones <drjones@redhat.com> > > Reviewed-by: Marc Zyngier <marc.zyngier@arm.com> > > Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org> > > [...] > > > diff --git a/arch/arm64/kvm/hyp/sysreg-sr.c b/arch/arm64/kvm/hyp/sysreg-sr.c > > index 883a6383cd36..848a46eb33bf 100644 > > --- a/arch/arm64/kvm/hyp/sysreg-sr.c > > +++ b/arch/arm64/kvm/hyp/sysreg-sr.c > > [...] > > > @@ -213,6 +215,19 @@ void kvm_vcpu_load_sysregs(struct kvm_vcpu *vcpu) > > */ > > void kvm_vcpu_put_sysregs(struct kvm_vcpu *vcpu) > > { > > + struct kvm_cpu_context *host_ctxt = vcpu->arch.host_cpu_context; > > + struct kvm_cpu_context *guest_ctxt = &vcpu->arch.ctxt; > > + > > + /* Restore host FP/SIMD state */ > > + if (vcpu->arch.guest_vfp_loaded) { > > + if (vcpu_el1_is_32bit(vcpu)) { > > + kvm_call_hyp(__fpsimd32_save_state, > > + kern_hyp_va(guest_ctxt)); > > + } > > + __fpsimd_save_state(&guest_ctxt->gp_regs.fp_regs); > > + __fpsimd_restore_state(&host_ctxt->gp_regs.fp_regs); > > + vcpu->arch.guest_vfp_loaded = 0; > > Provided we've already marked the host FPSIMD state as dirty on the way > in, we probably don't need to restore it here. > > In v4.15, the kvm_fpsimd_flush_cpu_state() call in > kvm_arch_vcpu_ioctl_run() is supposed to do this marking: currently > it's only done for SVE, since KVM was previously restoring the host > FPSIMD subset of the state anyway, but it could be made unconditional. > > For a returning run ioctl, this would have the effect of deferring the > host FPSIMD reload until we return to userspace, which is probably > no more costly since the kernel must check whether to do this in > ret_to_user anyway; OTOH if the vcpu thread was preempted by some > other thread we save the cost of restoring the host state entirely here > ... I think. Yes, I agree. However, currently the low-level logic in arch/arm64/kvm/hyp/entry.S:__fpsimd_guest_restore which saves the host state into vcpu->arch.host_cpu_context->gp_regs.fp_regs (where host_cpu_context is a KVM-specific per-cpu variable). I think means that simply marking the state as invalid would cause the kernel to restore some potentially stale values when returning to userspace. Am I missing something? It might very well be possible to change the logic so that we store the host logic the same place where task_fpsimd_save() would have, and I think that would make what you suggest possible. I'd like to make that a separate change from this patch though, as we're already changing quite a bit with this series, so I'm trying to make any logical change as contained per patch as possible, so that problems can be spotted by bisecting. > > Ultimately I'd like to go one better and actually treat a vcpu as a > first-class fpsimd context, so that taking an interrupt to the host > and then reentering the guest doesn't cause any reload at all. That should be the case already; kvm_vcpu_put_sysregs() is only called when you run another thread (preemptively or voluntarily), or when you return to user space, but making the vcpu fpsimd context a first-class citizen fpsimd context would mean that you can run another thread (and maybe run userspace if it doesn't use fpsimd?) without having to save/restore anything. Am I getting this right? > But > that feels like too big a step for this series, and there are likely > side-issues I've not thought about yet. > It should definitely be in separate patches, but I would be optn to tagging something on to the end of this series if we can stabilize this series early after -rc1 is out. Thanks, -Christoffer
next prev parent reply other threads:[~2018-01-25 19:46 UTC|newest] Thread overview: 223+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-12 12:07 [PATCH v3 00/41] Optimize KVM/ARM for VHE systems Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 01/41] KVM: arm/arm64: Avoid vcpu_load for other vcpu ioctls than KVM_RUN Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-05 12:32 ` Julien Grall 2018-02-05 12:32 ` Julien Grall 2018-01-12 12:07 ` [PATCH v3 02/41] KVM: arm/arm64: Move vcpu_load call after kvm_vcpu_first_run_init Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-05 14:34 ` Julien Grall 2018-02-05 14:34 ` Julien Grall 2018-01-12 12:07 ` [PATCH v3 03/41] KVM: arm64: Avoid storing the vcpu pointer on the stack Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-05 17:14 ` Julien Grall 2018-02-05 17:14 ` Julien Grall 2018-01-12 12:07 ` [PATCH v3 04/41] KVM: arm64: Rework hyp_panic for VHE and non-VHE Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-05 18:04 ` Julien Grall 2018-02-05 18:04 ` Julien Grall 2018-02-05 18:10 ` Julien Grall 2018-02-05 18:10 ` Julien Grall 2018-02-08 13:24 ` Christoffer Dall 2018-02-08 13:24 ` Christoffer Dall 2018-02-09 10:55 ` Julien Grall 2018-02-09 10:55 ` Julien Grall 2018-01-12 12:07 ` [PATCH v3 05/41] KVM: arm64: Move HCR_INT_OVERRIDE to default HCR_EL2 guest flag Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-09 11:38 ` Julien Grall 2018-02-09 11:38 ` Julien Grall 2018-02-13 21:47 ` Christoffer Dall 2018-02-13 21:47 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 06/41] KVM: arm/arm64: Get rid of vcpu->arch.irq_lines Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 07/41] KVM: arm/arm64: Add kvm_vcpu_load_sysregs and kvm_vcpu_put_sysregs Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 08/41] KVM: arm/arm64: Introduce vcpu_el1_is_32bit Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-17 14:44 ` Julien Thierry 2018-01-17 14:44 ` Julien Thierry 2018-01-18 12:57 ` Christoffer Dall 2018-01-18 12:57 ` Christoffer Dall 2018-02-09 12:31 ` Julien Grall 2018-02-09 12:31 ` Julien Grall 2018-01-12 12:07 ` [PATCH v3 09/41] KVM: arm64: Defer restoring host VFP state to vcpu_put Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-22 17:33 ` Dave Martin 2018-01-22 17:33 ` Dave Martin 2018-01-25 19:46 ` Christoffer Dall [this message] 2018-01-25 19:46 ` Christoffer Dall 2018-02-07 16:49 ` Dave Martin 2018-02-07 16:49 ` Dave Martin 2018-02-07 17:56 ` Christoffer Dall 2018-02-07 17:56 ` Christoffer Dall 2018-02-09 15:59 ` Dave Martin 2018-02-09 15:59 ` Dave Martin 2018-02-13 8:51 ` Christoffer Dall 2018-02-13 8:51 ` Christoffer Dall 2018-02-13 14:08 ` Dave Martin 2018-02-13 14:08 ` Dave Martin 2018-02-14 10:15 ` Christoffer Dall 2018-02-14 10:15 ` Christoffer Dall 2018-02-14 14:43 ` Dave Martin 2018-02-14 14:43 ` Dave Martin 2018-02-14 17:38 ` Christoffer Dall 2018-02-14 17:38 ` Christoffer Dall 2018-02-14 17:43 ` Ard Biesheuvel 2018-02-14 17:43 ` Ard Biesheuvel 2018-02-14 21:08 ` Marc Zyngier 2018-02-14 21:08 ` Marc Zyngier 2018-02-15 9:51 ` Dave Martin 2018-02-15 9:51 ` Dave Martin 2018-02-09 15:26 ` Julien Grall 2018-02-09 15:26 ` Julien Grall 2018-02-13 8:52 ` Christoffer Dall 2018-02-13 8:52 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 10/41] KVM: arm64: Move debug dirty flag calculation out of world switch Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-17 15:11 ` Julien Thierry 2018-01-17 15:11 ` Julien Thierry 2018-01-12 12:07 ` [PATCH v3 11/41] KVM: arm64: Slightly improve debug save/restore functions Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 12/41] KVM: arm64: Improve debug register save/restore flow Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 13/41] KVM: arm64: Factor out fault info population and gic workarounds Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-17 15:35 ` Julien Thierry 2018-01-12 12:07 ` [PATCH v3 14/41] KVM: arm64: Introduce VHE-specific kvm_vcpu_run Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-24 16:13 ` Dave Martin 2018-01-24 16:13 ` Dave Martin 2018-01-25 8:45 ` Christoffer Dall 2018-01-25 8:45 ` Christoffer Dall 2018-02-09 17:34 ` Julien Grall 2018-02-09 17:34 ` Julien Grall 2018-02-13 8:52 ` Christoffer Dall 2018-02-13 8:52 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 15/41] KVM: arm64: Remove kern_hyp_va() use in VHE switch function Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-24 16:24 ` Dave Martin 2018-01-24 16:24 ` Dave Martin 2018-01-25 19:48 ` Christoffer Dall 2018-01-25 19:48 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 16/41] KVM: arm64: Don't deactivate VM on VHE systems Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 17/41] KVM: arm64: Remove noop calls to timer save/restore from VHE switch Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-09 17:53 ` Julien Grall 2018-02-09 17:53 ` Julien Grall 2018-02-13 8:53 ` Christoffer Dall 2018-02-13 8:53 ` Christoffer Dall 2018-02-13 22:31 ` Christoffer Dall 2018-02-13 22:31 ` Christoffer Dall 2018-02-19 16:30 ` Julien Grall 2018-02-19 16:30 ` Julien Grall 2018-01-12 12:07 ` [PATCH v3 18/41] KVM: arm64: Move userspace system registers into separate function Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-09 18:50 ` Julien Grall 2018-02-09 18:50 ` Julien Grall 2018-02-14 11:22 ` Christoffer Dall 2018-02-14 11:22 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 19/41] KVM: arm64: Rewrite sysreg alternatives to static keys Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 20/41] KVM: arm64: Introduce separate VHE/non-VHE sysreg save/restore functions Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 21/41] KVM: arm/arm64: Remove leftover comment from kvm_vcpu_run_vhe Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 22/41] KVM: arm64: Unify non-VHE host/guest sysreg save and restore functions Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 23/41] KVM: arm64: Don't save the host ELR_EL2 and SPSR_EL2 on VHE systems Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 24/41] KVM: arm64: Change 32-bit handling of VM system registers Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 25/41] KVM: arm64: Rewrite system register accessors to read/write functions Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 26/41] KVM: arm64: Introduce framework for accessing deferred sysregs Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-17 17:52 ` Julien Thierry 2018-01-17 17:52 ` Julien Thierry 2018-01-18 13:08 ` Christoffer Dall 2018-01-18 13:08 ` Christoffer Dall 2018-01-18 13:39 ` Julien Thierry 2018-01-18 13:39 ` Julien Thierry 2018-01-23 16:04 ` Dave Martin 2018-01-23 16:04 ` Dave Martin 2018-01-25 19:54 ` Christoffer Dall 2018-01-25 19:54 ` Christoffer Dall 2018-02-09 16:17 ` Dave Martin 2018-02-09 16:17 ` Dave Martin 2018-02-13 8:55 ` Christoffer Dall 2018-02-13 8:55 ` Christoffer Dall 2018-02-13 14:27 ` Dave Martin 2018-02-13 14:27 ` Dave Martin 2018-01-12 12:07 ` [PATCH v3 27/41] KVM: arm/arm64: Prepare to handle deferred save/restore of SPSR_EL1 Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 28/41] KVM: arm64: Prepare to handle deferred save/restore of ELR_EL1 Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 29/41] KVM: arm64: Defer saving/restoring 64-bit sysregs to vcpu load/put on VHE Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 30/41] KVM: arm64: Prepare to handle deferred save/restore of 32-bit registers Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-17 18:22 ` Julien Thierry 2018-01-17 18:22 ` Julien Thierry 2018-01-18 13:12 ` Christoffer Dall 2018-01-18 13:12 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 31/41] KVM: arm64: Defer saving/restoring 32-bit sysregs to vcpu load/put Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 32/41] KVM: arm64: Move common VHE/non-VHE trap config in separate functions Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 33/41] KVM: arm64: Configure FPSIMD traps on vcpu load/put Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-18 9:31 ` Julien Thierry 2018-01-18 9:31 ` Julien Thierry 2018-01-31 12:17 ` Tomasz Nowicki 2018-01-31 12:17 ` Tomasz Nowicki 2018-02-05 10:06 ` Christoffer Dall 2018-02-05 10:06 ` Christoffer Dall 2018-01-31 12:24 ` Tomasz Nowicki 2018-01-31 12:24 ` Tomasz Nowicki 2018-01-12 12:07 ` [PATCH v3 34/41] KVM: arm64: Configure c15, PMU, and debug register traps on cpu load/put for VHE Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 35/41] KVM: arm64: Separate activate_traps and deactive_traps for VHE and non-VHE Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 36/41] KVM: arm/arm64: Get rid of vgic_elrsr Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 37/41] KVM: arm/arm64: Handle VGICv2 save/restore from the main VGIC code Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 38/41] KVM: arm/arm64: Move arm64-only vgic-v2-sr.c file to arm64 Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 39/41] KVM: arm/arm64: Handle VGICv3 save/restore from the main VGIC code on VHE Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 40/41] KVM: arm/arm64: Move VGIC APR save/restore to vgic put/load Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-01-12 12:07 ` [PATCH v3 41/41] KVM: arm/arm64: Avoid VGICv3 save/restore on VHE with no IRQs Christoffer Dall 2018-01-12 12:07 ` Christoffer Dall 2018-02-05 13:29 ` Tomasz Nowicki 2018-02-05 13:29 ` Tomasz Nowicki 2018-02-08 15:48 ` Christoffer Dall 2018-02-08 15:48 ` Christoffer Dall 2018-01-15 14:14 ` [PATCH v3 00/41] Optimize KVM/ARM for VHE systems Yury Norov 2018-01-15 14:14 ` Yury Norov 2018-01-15 15:50 ` Christoffer Dall 2018-01-15 15:50 ` Christoffer Dall 2018-01-17 8:34 ` Yury Norov 2018-01-17 8:34 ` Yury Norov 2018-01-17 10:48 ` Christoffer Dall 2018-01-17 10:48 ` Christoffer Dall 2018-01-18 11:16 ` Christoffer Dall 2018-01-18 11:16 ` Christoffer Dall 2018-01-18 12:18 ` Yury Norov 2018-01-18 12:18 ` Yury Norov 2018-01-18 13:32 ` Christoffer Dall 2018-01-18 13:32 ` Christoffer Dall 2018-01-22 13:40 ` Tomasz Nowicki 2018-01-22 13:40 ` Tomasz Nowicki 2018-02-01 13:57 ` Tomasz Nowicki 2018-02-01 13:57 ` Tomasz Nowicki 2018-02-01 16:15 ` Yury Norov 2018-02-01 16:15 ` Yury Norov 2018-02-02 10:05 ` Tomasz Nowicki 2018-02-02 10:05 ` Tomasz Nowicki 2018-02-02 10:07 ` Tomasz Nowicki 2018-02-02 10:07 ` Tomasz Nowicki 2018-02-08 15:47 ` Christoffer Dall 2018-02-08 15:47 ` Christoffer Dall
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20180125194653.GR21802@cbox \ --to=christoffer.dall@linaro.org \ --cc=Dave.Martin@arm.com \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=marc.zyngier@arm.com \ --cc=shihwei@cs.columbia.edu \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.