All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <cdall@linaro.org>
To: Jintack Lim <jintack@cs.columbia.edu>
Cc: christoffer.dall@linaro.org, marc.zyngier@arm.com,
	pbonzini@redhat.com, rkrcmar@redhat.com, linux@armlinux.org.uk,
	catalin.marinas@arm.com, will.deacon@arm.com,
	vladimir.murzin@arm.com, suzuki.poulose@arm.com,
	mark.rutland@arm.com, james.morse@arm.com,
	lorenzo.pieralisi@arm.com, kevin.brodsky@arm.com,
	wcohen@redhat.com, shankerd@codeaurora.org, geoff@infradead.org,
	andre.przywara@arm.com, eric.auger@redhat.com,
	anna-maria@linutronix.de, shihwei@cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC 31/55] KVM: arm/arm64: Inject maintenance interrupts to the guest hypervisor
Date: Wed, 22 Feb 2017 14:19:49 +0100	[thread overview]
Message-ID: <20170222131949.GR26976@cbox> (raw)
In-Reply-To: <1483943091-1364-32-git-send-email-jintack@cs.columbia.edu>

On Mon, Jan 09, 2017 at 01:24:27AM -0500, Jintack Lim wrote:
> From: Christoffer Dall <christoffer.dall@linaro.org>
> 
> If we exit a nested VM with a pending maintenance interrupt from the
> GIC, then we need to forward this to the guest hypervisor so that it can
> re-sync the appropriate LRs and sample level triggered interrupts again.
> 
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> Signed-off-by: Jintack Lim <jintack@cs.columbia.edu>
> ---
>  arch/arm64/kvm/context.c           |  3 +++
>  include/kvm/arm_vgic.h             |  2 ++
>  virt/kvm/arm/vgic/vgic-v2-nested.c | 16 ++++++++++++++++
>  3 files changed, 21 insertions(+)
> 
> diff --git a/arch/arm64/kvm/context.c b/arch/arm64/kvm/context.c
> index 7a94c9d..a93ffe4 100644
> --- a/arch/arm64/kvm/context.c
> +++ b/arch/arm64/kvm/context.c
> @@ -140,6 +140,9 @@ static void sync_shadow_el1_state(struct kvm_vcpu *vcpu, bool setup)
>  void kvm_arm_setup_shadow_state(struct kvm_vcpu *vcpu)
>  {
>  	struct kvm_cpu_context *ctxt = &vcpu->arch.ctxt;
> +
> +	vgic_handle_nested_maint_irq(vcpu);
> +

It feels like I stuck this in some random place where it would work, but
now it looks weird to call a vgic function from the shadow_el1_state
function.  Can we find a more appropriate place to put it?

>  	if (unlikely(vcpu_mode_el2(vcpu))) {
>  		ctxt->hw_pstate = *vcpu_cpsr(vcpu) & ~PSR_MODE_MASK;
>  
> diff --git a/include/kvm/arm_vgic.h b/include/kvm/arm_vgic.h
> index 484f6b1..fc882d6 100644
> --- a/include/kvm/arm_vgic.h
> +++ b/include/kvm/arm_vgic.h
> @@ -315,9 +315,11 @@ int kvm_vgic_inject_mapped_irq(struct kvm *kvm, int cpuid, unsigned int intid,
>  #ifdef CONFIG_KVM_ARM_NESTED_HYP
>  void vgic_v2_setup_shadow_state(struct kvm_vcpu *vcpu);
>  void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu);
> +void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu);
>  #else
>  static inline void vgic_v2_setup_shadow_state(struct kvm_vcpu *vcpu) { }
>  static inline void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu) { }
> +static inline void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu) { }
>  #endif
>  
>  #define irqchip_in_kernel(k)	(!!((k)->arch.vgic.in_kernel))
> diff --git a/virt/kvm/arm/vgic/vgic-v2-nested.c b/virt/kvm/arm/vgic/vgic-v2-nested.c
> index a992da5..85f646b 100644
> --- a/virt/kvm/arm/vgic/vgic-v2-nested.c
> +++ b/virt/kvm/arm/vgic/vgic-v2-nested.c
> @@ -300,6 +300,22 @@ void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu)
>  	vgic_cpu->nested_vgic_v2 = vgic_cpu->shadow_vgic_v2;
>  }
>  
> +void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu)
> +{
> +	struct vgic_v2_cpu_if *cpu_if = vcpu_nested_if(vcpu);
> +
> +	/*
> +	 * If we exit a nested VM with a pending maintenance interrupt from the
> +	 * GIC, then we need to forward this to the guest hypervisor so that it
> +	 * can re-sync the appropriate LRs and sample level triggered interrupts
> +	 * again.
> +	 */
> +	if (vcpu_el2_imo_is_set(vcpu) && !vcpu_mode_el2(vcpu) &&

I think I made the same mistake here, that we shouldn't check if we're
in EL2 or not, because I don't think the GIC cares.  I think we should
check if EL2 can accept interrupts (i.e. PSTATE.I is clear if it is in
EL2 or IMO is set if not).

> +	    (cpu_if->vgic_hcr & GICH_HCR_EN) &&
> +	    vgic_mmio_read_v2_misr(vcpu, 0, 0))

what are the zeroes?  They look dodgy.

> +		kvm_inject_nested_irq(vcpu);
> +}
> +
>  void vgic_init_nested(struct kvm_vcpu *vcpu)
>  {
>  	vgic_v2_setup_shadow_state(vcpu);
> -- 
> 1.9.1
> 
> 

Thanks,
-Christoffer

WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <cdall@linaro.org>
To: Jintack Lim <jintack@cs.columbia.edu>
Cc: kvm@vger.kernel.org, catalin.marinas@arm.com,
	will.deacon@arm.com, kvmarm@lists.cs.columbia.edu,
	shihwei@cs.columbia.edu, lorenzo.pieralisi@arm.com,
	linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
	marc.zyngier@arm.com, andre.przywara@arm.com,
	kevin.brodsky@arm.com, wcohen@redhat.com,
	anna-maria@linutronix.de, geoff@infradead.org,
	linux-kernel@vger.kernel.org, pbonzini@redhat.com
Subject: Re: [RFC 31/55] KVM: arm/arm64: Inject maintenance interrupts to the guest hypervisor
Date: Wed, 22 Feb 2017 14:19:49 +0100	[thread overview]
Message-ID: <20170222131949.GR26976@cbox> (raw)
In-Reply-To: <1483943091-1364-32-git-send-email-jintack@cs.columbia.edu>

On Mon, Jan 09, 2017 at 01:24:27AM -0500, Jintack Lim wrote:
> From: Christoffer Dall <christoffer.dall@linaro.org>
> 
> If we exit a nested VM with a pending maintenance interrupt from the
> GIC, then we need to forward this to the guest hypervisor so that it can
> re-sync the appropriate LRs and sample level triggered interrupts again.
> 
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> Signed-off-by: Jintack Lim <jintack@cs.columbia.edu>
> ---
>  arch/arm64/kvm/context.c           |  3 +++
>  include/kvm/arm_vgic.h             |  2 ++
>  virt/kvm/arm/vgic/vgic-v2-nested.c | 16 ++++++++++++++++
>  3 files changed, 21 insertions(+)
> 
> diff --git a/arch/arm64/kvm/context.c b/arch/arm64/kvm/context.c
> index 7a94c9d..a93ffe4 100644
> --- a/arch/arm64/kvm/context.c
> +++ b/arch/arm64/kvm/context.c
> @@ -140,6 +140,9 @@ static void sync_shadow_el1_state(struct kvm_vcpu *vcpu, bool setup)
>  void kvm_arm_setup_shadow_state(struct kvm_vcpu *vcpu)
>  {
>  	struct kvm_cpu_context *ctxt = &vcpu->arch.ctxt;
> +
> +	vgic_handle_nested_maint_irq(vcpu);
> +

It feels like I stuck this in some random place where it would work, but
now it looks weird to call a vgic function from the shadow_el1_state
function.  Can we find a more appropriate place to put it?

>  	if (unlikely(vcpu_mode_el2(vcpu))) {
>  		ctxt->hw_pstate = *vcpu_cpsr(vcpu) & ~PSR_MODE_MASK;
>  
> diff --git a/include/kvm/arm_vgic.h b/include/kvm/arm_vgic.h
> index 484f6b1..fc882d6 100644
> --- a/include/kvm/arm_vgic.h
> +++ b/include/kvm/arm_vgic.h
> @@ -315,9 +315,11 @@ int kvm_vgic_inject_mapped_irq(struct kvm *kvm, int cpuid, unsigned int intid,
>  #ifdef CONFIG_KVM_ARM_NESTED_HYP
>  void vgic_v2_setup_shadow_state(struct kvm_vcpu *vcpu);
>  void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu);
> +void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu);
>  #else
>  static inline void vgic_v2_setup_shadow_state(struct kvm_vcpu *vcpu) { }
>  static inline void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu) { }
> +static inline void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu) { }
>  #endif
>  
>  #define irqchip_in_kernel(k)	(!!((k)->arch.vgic.in_kernel))
> diff --git a/virt/kvm/arm/vgic/vgic-v2-nested.c b/virt/kvm/arm/vgic/vgic-v2-nested.c
> index a992da5..85f646b 100644
> --- a/virt/kvm/arm/vgic/vgic-v2-nested.c
> +++ b/virt/kvm/arm/vgic/vgic-v2-nested.c
> @@ -300,6 +300,22 @@ void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu)
>  	vgic_cpu->nested_vgic_v2 = vgic_cpu->shadow_vgic_v2;
>  }
>  
> +void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu)
> +{
> +	struct vgic_v2_cpu_if *cpu_if = vcpu_nested_if(vcpu);
> +
> +	/*
> +	 * If we exit a nested VM with a pending maintenance interrupt from the
> +	 * GIC, then we need to forward this to the guest hypervisor so that it
> +	 * can re-sync the appropriate LRs and sample level triggered interrupts
> +	 * again.
> +	 */
> +	if (vcpu_el2_imo_is_set(vcpu) && !vcpu_mode_el2(vcpu) &&

I think I made the same mistake here, that we shouldn't check if we're
in EL2 or not, because I don't think the GIC cares.  I think we should
check if EL2 can accept interrupts (i.e. PSTATE.I is clear if it is in
EL2 or IMO is set if not).

> +	    (cpu_if->vgic_hcr & GICH_HCR_EN) &&
> +	    vgic_mmio_read_v2_misr(vcpu, 0, 0))

what are the zeroes?  They look dodgy.

> +		kvm_inject_nested_irq(vcpu);
> +}
> +
>  void vgic_init_nested(struct kvm_vcpu *vcpu)
>  {
>  	vgic_v2_setup_shadow_state(vcpu);
> -- 
> 1.9.1
> 
> 

Thanks,
-Christoffer

WARNING: multiple messages have this Message-ID (diff)
From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 31/55] KVM: arm/arm64: Inject maintenance interrupts to the guest hypervisor
Date: Wed, 22 Feb 2017 14:19:49 +0100	[thread overview]
Message-ID: <20170222131949.GR26976@cbox> (raw)
In-Reply-To: <1483943091-1364-32-git-send-email-jintack@cs.columbia.edu>

On Mon, Jan 09, 2017 at 01:24:27AM -0500, Jintack Lim wrote:
> From: Christoffer Dall <christoffer.dall@linaro.org>
> 
> If we exit a nested VM with a pending maintenance interrupt from the
> GIC, then we need to forward this to the guest hypervisor so that it can
> re-sync the appropriate LRs and sample level triggered interrupts again.
> 
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> Signed-off-by: Jintack Lim <jintack@cs.columbia.edu>
> ---
>  arch/arm64/kvm/context.c           |  3 +++
>  include/kvm/arm_vgic.h             |  2 ++
>  virt/kvm/arm/vgic/vgic-v2-nested.c | 16 ++++++++++++++++
>  3 files changed, 21 insertions(+)
> 
> diff --git a/arch/arm64/kvm/context.c b/arch/arm64/kvm/context.c
> index 7a94c9d..a93ffe4 100644
> --- a/arch/arm64/kvm/context.c
> +++ b/arch/arm64/kvm/context.c
> @@ -140,6 +140,9 @@ static void sync_shadow_el1_state(struct kvm_vcpu *vcpu, bool setup)
>  void kvm_arm_setup_shadow_state(struct kvm_vcpu *vcpu)
>  {
>  	struct kvm_cpu_context *ctxt = &vcpu->arch.ctxt;
> +
> +	vgic_handle_nested_maint_irq(vcpu);
> +

It feels like I stuck this in some random place where it would work, but
now it looks weird to call a vgic function from the shadow_el1_state
function.  Can we find a more appropriate place to put it?

>  	if (unlikely(vcpu_mode_el2(vcpu))) {
>  		ctxt->hw_pstate = *vcpu_cpsr(vcpu) & ~PSR_MODE_MASK;
>  
> diff --git a/include/kvm/arm_vgic.h b/include/kvm/arm_vgic.h
> index 484f6b1..fc882d6 100644
> --- a/include/kvm/arm_vgic.h
> +++ b/include/kvm/arm_vgic.h
> @@ -315,9 +315,11 @@ int kvm_vgic_inject_mapped_irq(struct kvm *kvm, int cpuid, unsigned int intid,
>  #ifdef CONFIG_KVM_ARM_NESTED_HYP
>  void vgic_v2_setup_shadow_state(struct kvm_vcpu *vcpu);
>  void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu);
> +void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu);
>  #else
>  static inline void vgic_v2_setup_shadow_state(struct kvm_vcpu *vcpu) { }
>  static inline void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu) { }
> +static inline void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu) { }
>  #endif
>  
>  #define irqchip_in_kernel(k)	(!!((k)->arch.vgic.in_kernel))
> diff --git a/virt/kvm/arm/vgic/vgic-v2-nested.c b/virt/kvm/arm/vgic/vgic-v2-nested.c
> index a992da5..85f646b 100644
> --- a/virt/kvm/arm/vgic/vgic-v2-nested.c
> +++ b/virt/kvm/arm/vgic/vgic-v2-nested.c
> @@ -300,6 +300,22 @@ void vgic_v2_restore_shadow_state(struct kvm_vcpu *vcpu)
>  	vgic_cpu->nested_vgic_v2 = vgic_cpu->shadow_vgic_v2;
>  }
>  
> +void vgic_handle_nested_maint_irq(struct kvm_vcpu *vcpu)
> +{
> +	struct vgic_v2_cpu_if *cpu_if = vcpu_nested_if(vcpu);
> +
> +	/*
> +	 * If we exit a nested VM with a pending maintenance interrupt from the
> +	 * GIC, then we need to forward this to the guest hypervisor so that it
> +	 * can re-sync the appropriate LRs and sample level triggered interrupts
> +	 * again.
> +	 */
> +	if (vcpu_el2_imo_is_set(vcpu) && !vcpu_mode_el2(vcpu) &&

I think I made the same mistake here, that we shouldn't check if we're
in EL2 or not, because I don't think the GIC cares.  I think we should
check if EL2 can accept interrupts (i.e. PSTATE.I is clear if it is in
EL2 or IMO is set if not).

> +	    (cpu_if->vgic_hcr & GICH_HCR_EN) &&
> +	    vgic_mmio_read_v2_misr(vcpu, 0, 0))

what are the zeroes?  They look dodgy.

> +		kvm_inject_nested_irq(vcpu);
> +}
> +
>  void vgic_init_nested(struct kvm_vcpu *vcpu)
>  {
>  	vgic_v2_setup_shadow_state(vcpu);
> -- 
> 1.9.1
> 
> 

Thanks,
-Christoffer

  reply	other threads:[~2017-02-22 13:20 UTC|newest]

Thread overview: 322+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-09  6:23 [RFC 00/55] Nested Virtualization on KVM/ARM Jintack Lim
2017-01-09  6:23 ` Jintack Lim
2017-01-09  6:23 ` Jintack Lim
2017-01-09  6:23 ` [RFC 01/55] arm64: Add missing TCR hw defines Jintack Lim
2017-01-09  6:23   ` Jintack Lim
2017-01-09  6:23   ` Jintack Lim
2017-01-09  6:23 ` [RFC 02/55] KVM: arm64: Add nesting config option Jintack Lim
2017-01-09  6:23   ` Jintack Lim
2017-01-09  6:23   ` Jintack Lim
2017-01-09  6:23 ` [RFC 03/55] KVM: arm64: Add KVM nesting feature Jintack Lim
2017-01-09  6:23   ` Jintack Lim
2017-01-09  6:23   ` Jintack Lim
2017-01-09  6:24 ` [RFC 04/55] KVM: arm64: Allow userspace to set PSR_MODE_EL2x Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 05/55] KVM: arm64: Add vcpu_mode_el2 primitive to support nesting Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 06/55] KVM: arm64: Add EL2 execution context for nesting Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:10   ` Christoffer Dall
2017-02-22 11:10     ` Christoffer Dall
2017-02-22 11:10     ` Christoffer Dall
2017-06-26 14:33     ` Jintack Lim
2017-06-26 14:33       ` Jintack Lim
2017-06-26 14:33       ` Jintack Lim
2017-07-03  9:03       ` Christoffer Dall
2017-07-03  9:03         ` Christoffer Dall
2017-07-03  9:03         ` Christoffer Dall
2017-07-03  9:32         ` Marc Zyngier
2017-07-03  9:32           ` Marc Zyngier
2017-07-03  9:32           ` Marc Zyngier
2017-07-03  9:54           ` Christoffer Dall
2017-07-03  9:54             ` Christoffer Dall
2017-07-03  9:54             ` Christoffer Dall
2017-07-03 14:44             ` Jintack Lim
2017-07-03 14:44               ` Jintack Lim
2017-07-03 14:44               ` Jintack Lim
2017-07-03 15:30               ` Christoffer Dall
2017-07-03 15:30                 ` Christoffer Dall
2017-07-03 15:30                 ` Christoffer Dall
2017-01-09  6:24 ` [RFC 07/55] KVM: arm/arm64: Add virtual EL2 state emulation framework Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:12   ` Christoffer Dall
2017-02-22 11:12     ` Christoffer Dall
2017-02-22 11:12     ` Christoffer Dall
2017-06-01 20:05   ` Bandan Das
2017-06-01 20:05     ` Bandan Das
2017-06-02 11:51     ` Christoffer Dall
2017-06-02 11:51       ` Christoffer Dall
2017-06-02 11:51       ` Christoffer Dall
2017-06-02 17:36       ` Bandan Das
2017-06-02 17:36         ` Bandan Das
2017-06-02 17:36         ` Bandan Das
2017-06-02 19:06         ` Christoffer Dall
2017-06-02 19:06           ` Christoffer Dall
2017-06-02 19:06           ` Christoffer Dall
2017-06-02 19:25           ` Bandan Das
2017-06-02 19:25             ` Bandan Das
2017-06-02 19:25             ` Bandan Das
     [not found]             ` <20170602194353.GG397@cbox>
2017-06-02 20:18               ` Bandan Das
2017-06-02 21:15                 ` Christoffer Dall
2017-06-02 23:49                   ` Bandan Das
2017-01-09  6:24 ` [RFC 08/55] KVM: arm64: Set virtual EL2 context depending on the guest exception level Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:14   ` Christoffer Dall
2017-02-22 11:14     ` Christoffer Dall
2017-02-22 11:14     ` Christoffer Dall
2017-06-01 20:22   ` Bandan Das
2017-06-01 20:22     ` Bandan Das
2017-06-02  8:48     ` Marc Zyngier
2017-06-02  8:48       ` Marc Zyngier
2017-06-02  8:48       ` Marc Zyngier
2017-01-09  6:24 ` [RFC 09/55] KVM: arm64: Set shadow EL1 registers for virtual EL2 execution Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:19   ` Christoffer Dall
2017-02-22 11:19     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 10/55] KVM: arm64: Synchronize EL1 system registers on virtual EL2 entry and exit Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-06-06 20:16   ` Bandan Das
2017-06-06 20:16     ` Bandan Das
2017-06-06 20:16     ` Bandan Das
2017-06-07  4:26     ` Jintack Lim
2017-06-07  4:26       ` Jintack Lim
2017-01-09  6:24 ` [RFC 11/55] KVM: arm64: Emulate taking an exception to the guest hypervisor Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:28   ` Christoffer Dall
2017-02-22 11:28     ` Christoffer Dall
2017-02-22 11:28     ` Christoffer Dall
2017-06-06 20:21   ` Bandan Das
2017-06-06 20:21     ` Bandan Das
2017-06-06 20:21     ` Bandan Das
2017-06-06 20:38     ` Jintack Lim
2017-06-06 20:38       ` Jintack Lim
2017-06-06 22:07       ` Bandan Das
2017-06-06 22:07         ` Bandan Das
2017-06-06 23:16         ` Jintack Lim
2017-06-06 23:16           ` Jintack Lim
2017-06-06 23:16           ` Jintack Lim
2017-06-07 17:21           ` Bandan Das
2017-06-07 17:21             ` Bandan Das
2017-01-09  6:24 ` [RFC 12/55] KVM: arm64: Handle EL2 register access traps Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:30   ` Christoffer Dall
2017-02-22 11:30     ` Christoffer Dall
2017-02-22 11:31   ` Christoffer Dall
2017-02-22 11:31     ` Christoffer Dall
2017-02-22 11:31     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 13/55] KVM: arm64: Handle eret instruction traps Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 14/55] KVM: arm64: Take account of system " Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:34   ` Christoffer Dall
2017-02-22 11:34     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 15/55] KVM: arm64: Trap EL1 VM register accesses in virtual EL2 Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 16/55] KVM: arm64: Forward VM reg traps to the guest hypervisor Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:39   ` Christoffer Dall
2017-02-22 11:39     ` Christoffer Dall
2017-02-22 11:39     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 17/55] KVM: arm64: Trap SPSR_EL1, ELR_EL1 and VBAR_EL1 in virtual EL2 Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:40   ` Christoffer Dall
2017-02-22 11:40     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 18/55] KVM: arm64: Forward traps due to HCR_EL2.NV1 bit to the guest hypervisor Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:41   ` Christoffer Dall
2017-02-22 11:41     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 19/55] KVM: arm64: Trap CPACR_EL1 access in virtual EL2 Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 20/55] KVM: arm64: Forward CPACR_EL1 traps to the guest hypervisor Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 21/55] KVM: arm64: Forward HVC instruction " Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 11:47   ` Christoffer Dall
2017-02-22 11:47     ` Christoffer Dall
2017-02-22 11:47     ` Christoffer Dall
2017-06-26 15:21     ` Jintack Lim
2017-06-26 15:21       ` Jintack Lim
2017-06-26 15:21       ` Jintack Lim
2017-07-03  9:08       ` Christoffer Dall
2017-07-03  9:08         ` Christoffer Dall
2017-07-03  9:08         ` Christoffer Dall
2017-07-03  9:31         ` Andrew Jones
2017-07-03  9:31           ` Andrew Jones
2017-07-03  9:31           ` Andrew Jones
2017-07-03  9:51           ` Christoffer Dall
2017-07-03  9:51             ` Christoffer Dall
2017-07-03  9:51             ` Christoffer Dall
2017-07-03 12:03             ` Will Deacon
2017-07-03 12:03               ` Will Deacon
2017-07-03 12:03               ` Will Deacon
2017-07-03 12:35               ` Marc Zyngier
2017-07-03 12:35                 ` Marc Zyngier
2017-07-03 12:35                 ` Marc Zyngier
2017-07-03 13:29         ` Jintack Lim
2017-07-03 13:29           ` Jintack Lim
2017-07-03 13:29           ` Jintack Lim
2017-01-09  6:24 ` [RFC 22/55] KVM: arm64: Handle PSCI call from the guest Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 23/55] KVM: arm64: Forward WFX to the guest hypervisor Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 24/55] KVM: arm64: Forward FP exceptions " Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 25/55] KVM: arm/arm64: Let vcpu thread modify its own active state Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 12:27   ` Christoffer Dall
2017-02-22 12:27     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 26/55] KVM: arm/arm64: Add VGIC data structures for the nesting Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 27/55] KVM: arm/arm64: Emulate GICH interface on GICv2 Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 13:06   ` Christoffer Dall
2017-02-22 13:06     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 28/55] KVM: arm/arm64: Prepare vgic state for the nested VM Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 13:12   ` Christoffer Dall
2017-02-22 13:12     ` Christoffer Dall
2017-02-22 13:12     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 29/55] KVM: arm/arm64: Set up the prepared vgic state Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 30/55] KVM: arm/arm64: Inject irqs to the guest hypervisor Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 13:16   ` Christoffer Dall
2017-02-22 13:16     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 31/55] KVM: arm/arm64: Inject maintenance interrupts " Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 13:19   ` Christoffer Dall [this message]
2017-02-22 13:19     ` Christoffer Dall
2017-02-22 13:19     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 32/55] KVM: arm/arm64: register GICH iodev for " Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 13:21   ` Christoffer Dall
2017-02-22 13:21     ` Christoffer Dall
2017-02-22 13:21     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 33/55] KVM: arm/arm64: Remove unused params in mmu functions Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 34/55] KVM: arm/arm64: Abstract stage-2 MMU state into a separate structure Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 35/55] KVM: arm/arm64: Support mmu for the virtual EL2 execution Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 13:38   ` Christoffer Dall
2017-02-22 13:38     ` Christoffer Dall
2017-02-22 13:38     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 36/55] KVM: arm64: Invalidate virtual EL2 TLB entries when needed Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 37/55] KVM: arm64: Setup vttbr_el2 on each VM entry Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 38/55] KVM: arm/arm64: Make mmu functions non-static Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 39/55] KVM: arm/arm64: Add mmu context for the nesting Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 13:34   ` Christoffer Dall
2017-02-22 13:34     ` Christoffer Dall
2017-02-22 13:34     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 40/55] KVM: arm/arm64: Handle vttbr_el2 write operation from the guest hypervisor Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 17:59   ` Christoffer Dall
2017-02-22 17:59     ` Christoffer Dall
2017-02-22 17:59     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 41/55] KVM: arm/arm64: Unmap/flush shadow stage 2 page tables Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 18:09   ` Christoffer Dall
2017-02-22 18:09     ` Christoffer Dall
2017-02-22 18:09     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 42/55] KVM: arm64: Implement nested Stage-2 page table walk logic Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 43/55] KVM: arm/arm64: Handle shadow stage 2 page faults Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 44/55] KVM: arm/arm64: Move kvm_is_write_fault to header file Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 45/55] KVM: arm64: KVM: Inject stage-2 page faults Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 46/55] KVM: arm64: Add more info to the S2 translation result Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 47/55] KVM: arm/arm64: Forward the guest hypervisor's stage 2 permission faults Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 18:15   ` Christoffer Dall
2017-02-22 18:15     ` Christoffer Dall
2017-02-22 18:15     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 48/55] KVM: arm64: Emulate TLBI instruction Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 49/55] KVM: arm64: Fixes to toggle_cache for nesting Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 50/55] KVM: arm/arm64: Abstract kvm_phys_addr_ioremap() function Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 51/55] KVM: arm64: Expose physical address of vcpu interface Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 52/55] KVM: arm/arm64: Create a vcpu mapping for the nested VM Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 53/55] KVM: arm64: Reflect shadow VMPIDR_EL2 value to MPIDR_EL1 Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24 ` [RFC 54/55] KVM: arm/arm64: Adjust virtual offset considering nesting Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-02-22 19:28   ` Christoffer Dall
2017-02-22 19:28     ` Christoffer Dall
2017-02-22 19:28     ` Christoffer Dall
2017-01-09  6:24 ` [RFC 55/55] KVM: arm64: Enable nested virtualization Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09  6:24   ` Jintack Lim
2017-01-09 15:05 ` [RFC 00/55] Nested Virtualization on KVM/ARM David Hildenbrand
2017-01-09 15:05   ` David Hildenbrand
2017-01-10 16:18   ` Jintack Lim
2017-01-10 16:18     ` Jintack Lim
2017-01-10 16:18     ` Jintack Lim
2017-02-22 18:23 ` Christoffer Dall
2017-02-22 18:23   ` Christoffer Dall
2017-02-22 18:23   ` Christoffer Dall
2017-02-24 10:08   ` Jintack Lim
2017-02-24 10:28   ` Jintack Lim
2017-02-24 10:28     ` Jintack Lim
2017-02-24 10:28     ` Jintack Lim

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=20170222131949.GR26976@cbox \
    --to=cdall@linaro.org \
    --cc=andre.przywara@arm.com \
    --cc=anna-maria@linutronix.de \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=eric.auger@redhat.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=jintack@cs.columbia.edu \
    --cc=kevin.brodsky@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=shankerd@codeaurora.org \
    --cc=shihwei@cs.columbia.edu \
    --cc=suzuki.poulose@arm.com \
    --cc=vladimir.murzin@arm.com \
    --cc=wcohen@redhat.com \
    --cc=will.deacon@arm.com \
    /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: link
Be 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.