All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Jintack Lim <jintack@cs.columbia.edu>
Cc: kvm@vger.kernel.org, catalin.marinas@arm.com,
	will.deacon@arm.com, linux@armlinux.org.uk,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, andre.przywara@arm.com,
	pbonzini@redhat.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level
Date: Sun, 29 Jan 2017 15:21:06 +0000	[thread overview]
Message-ID: <86sho199jx.fsf@arm.com> (raw)
In-Reply-To: <1485479100-4966-7-git-send-email-jintack@cs.columbia.edu> (Jintack Lim's message of "Thu, 26 Jan 2017 20:04:56 -0500")

On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim <jintack@cs.columbia.edu> wrote:
> Now that we maintain the EL1 physical timer register states of VMs,
> update the physical timer interrupt level along with the virtual one.
>
> Note that the emulated EL1 physical timer is not mapped to any hardware
> timer, so we call a proper vgic function.
>
> Signed-off-by: Jintack Lim <jintack@cs.columbia.edu>
> ---
>  virt/kvm/arm/arch_timer.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index 0f6e935..3b6bd50 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -180,6 +180,21 @@ static void kvm_timer_update_mapped_irq(struct kvm_vcpu *vcpu, bool new_level,
>  	WARN_ON(ret);
>  }
>  
> +static void kvm_timer_update_irq(struct kvm_vcpu *vcpu, bool new_level,
> +				 struct arch_timer_context *timer)
> +{
> +	int ret;
> +
> +	BUG_ON(!vgic_initialized(vcpu->kvm));

Although I've added my fair share of BUG_ON() in the code base, I've
since reconsidered my position. If we get in a situation where the vgic
is not initialized, maybe it would be better to just WARN_ON and return
early rather than killing the whole box. Thoughts?

> +
> +	timer->irq.level = new_level;
> +	trace_kvm_timer_update_irq(vcpu->vcpu_id, timer->irq.irq,
> +				   timer->irq.level);
> +	ret = kvm_vgic_inject_irq(vcpu->kvm, vcpu->vcpu_id, timer->irq.irq,
> +				  timer->irq.level);
> +	WARN_ON(ret);
> +}
> +
>  /*
>   * Check if there was a change in the timer state (should we raise or lower
>   * the line level to the GIC).
> @@ -188,6 +203,7 @@ static int kvm_timer_update_state(struct kvm_vcpu *vcpu)
>  {
>  	struct arch_timer_cpu *timer = &vcpu->arch.timer_cpu;
>  	struct arch_timer_context *vtimer = vcpu_vtimer(vcpu);
> +	struct arch_timer_context *ptimer = vcpu_ptimer(vcpu);
>  
>  	/*
>  	 * If userspace modified the timer registers via SET_ONE_REG before
> @@ -201,6 +217,10 @@ static int kvm_timer_update_state(struct kvm_vcpu *vcpu)
>  	if (kvm_timer_should_fire(vcpu, vtimer) != vtimer->irq.level)
>  		kvm_timer_update_mapped_irq(vcpu, !vtimer->irq.level, vtimer);
>  
> +	/* The emulated EL1 physical timer irq is not mapped to hardware */

Maybe a slightly better comment would be saying that we're using a
purely virtual interrupt, unrelated to the hardware interrupt.

> +	if (kvm_timer_should_fire(vcpu, ptimer) != ptimer->irq.level)
> +		kvm_timer_update_irq(vcpu, !ptimer->irq.level, ptimer);
> +
>  	return 0;
>  }

Otherwise looks good.

          M.
-- 
Jazz is not dead. It just smells funny.

WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level
Date: Sun, 29 Jan 2017 15:21:06 +0000	[thread overview]
Message-ID: <86sho199jx.fsf@arm.com> (raw)
In-Reply-To: <1485479100-4966-7-git-send-email-jintack@cs.columbia.edu> (Jintack Lim's message of "Thu, 26 Jan 2017 20:04:56 -0500")

On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim <jintack@cs.columbia.edu> wrote:
> Now that we maintain the EL1 physical timer register states of VMs,
> update the physical timer interrupt level along with the virtual one.
>
> Note that the emulated EL1 physical timer is not mapped to any hardware
> timer, so we call a proper vgic function.
>
> Signed-off-by: Jintack Lim <jintack@cs.columbia.edu>
> ---
>  virt/kvm/arm/arch_timer.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index 0f6e935..3b6bd50 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -180,6 +180,21 @@ static void kvm_timer_update_mapped_irq(struct kvm_vcpu *vcpu, bool new_level,
>  	WARN_ON(ret);
>  }
>  
> +static void kvm_timer_update_irq(struct kvm_vcpu *vcpu, bool new_level,
> +				 struct arch_timer_context *timer)
> +{
> +	int ret;
> +
> +	BUG_ON(!vgic_initialized(vcpu->kvm));

Although I've added my fair share of BUG_ON() in the code base, I've
since reconsidered my position. If we get in a situation where the vgic
is not initialized, maybe it would be better to just WARN_ON and return
early rather than killing the whole box. Thoughts?

> +
> +	timer->irq.level = new_level;
> +	trace_kvm_timer_update_irq(vcpu->vcpu_id, timer->irq.irq,
> +				   timer->irq.level);
> +	ret = kvm_vgic_inject_irq(vcpu->kvm, vcpu->vcpu_id, timer->irq.irq,
> +				  timer->irq.level);
> +	WARN_ON(ret);
> +}
> +
>  /*
>   * Check if there was a change in the timer state (should we raise or lower
>   * the line level to the GIC).
> @@ -188,6 +203,7 @@ static int kvm_timer_update_state(struct kvm_vcpu *vcpu)
>  {
>  	struct arch_timer_cpu *timer = &vcpu->arch.timer_cpu;
>  	struct arch_timer_context *vtimer = vcpu_vtimer(vcpu);
> +	struct arch_timer_context *ptimer = vcpu_ptimer(vcpu);
>  
>  	/*
>  	 * If userspace modified the timer registers via SET_ONE_REG before
> @@ -201,6 +217,10 @@ static int kvm_timer_update_state(struct kvm_vcpu *vcpu)
>  	if (kvm_timer_should_fire(vcpu, vtimer) != vtimer->irq.level)
>  		kvm_timer_update_mapped_irq(vcpu, !vtimer->irq.level, vtimer);
>  
> +	/* The emulated EL1 physical timer irq is not mapped to hardware */

Maybe a slightly better comment would be saying that we're using a
purely virtual interrupt, unrelated to the hardware interrupt.

> +	if (kvm_timer_should_fire(vcpu, ptimer) != ptimer->irq.level)
> +		kvm_timer_update_irq(vcpu, !ptimer->irq.level, ptimer);
> +
>  	return 0;
>  }

Otherwise looks good.

          M.
-- 
Jazz is not dead. It just smells funny.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Jintack Lim <jintack@cs.columbia.edu>
Cc: <pbonzini@redhat.com>, <rkrcmar@redhat.com>,
	<christoffer.dall@linaro.org>, <linux@armlinux.org.uk>,
	<catalin.marinas@arm.com>, <will.deacon@arm.com>,
	<andre.przywara@arm.com>, <kvm@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<kvmarm@lists.cs.columbia.edu>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level
Date: Sun, 29 Jan 2017 15:21:06 +0000	[thread overview]
Message-ID: <86sho199jx.fsf@arm.com> (raw)
In-Reply-To: <1485479100-4966-7-git-send-email-jintack@cs.columbia.edu> (Jintack Lim's message of "Thu, 26 Jan 2017 20:04:56 -0500")

On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim <jintack@cs.columbia.edu> wrote:
> Now that we maintain the EL1 physical timer register states of VMs,
> update the physical timer interrupt level along with the virtual one.
>
> Note that the emulated EL1 physical timer is not mapped to any hardware
> timer, so we call a proper vgic function.
>
> Signed-off-by: Jintack Lim <jintack@cs.columbia.edu>
> ---
>  virt/kvm/arm/arch_timer.c | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
>
> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
> index 0f6e935..3b6bd50 100644
> --- a/virt/kvm/arm/arch_timer.c
> +++ b/virt/kvm/arm/arch_timer.c
> @@ -180,6 +180,21 @@ static void kvm_timer_update_mapped_irq(struct kvm_vcpu *vcpu, bool new_level,
>  	WARN_ON(ret);
>  }
>  
> +static void kvm_timer_update_irq(struct kvm_vcpu *vcpu, bool new_level,
> +				 struct arch_timer_context *timer)
> +{
> +	int ret;
> +
> +	BUG_ON(!vgic_initialized(vcpu->kvm));

Although I've added my fair share of BUG_ON() in the code base, I've
since reconsidered my position. If we get in a situation where the vgic
is not initialized, maybe it would be better to just WARN_ON and return
early rather than killing the whole box. Thoughts?

> +
> +	timer->irq.level = new_level;
> +	trace_kvm_timer_update_irq(vcpu->vcpu_id, timer->irq.irq,
> +				   timer->irq.level);
> +	ret = kvm_vgic_inject_irq(vcpu->kvm, vcpu->vcpu_id, timer->irq.irq,
> +				  timer->irq.level);
> +	WARN_ON(ret);
> +}
> +
>  /*
>   * Check if there was a change in the timer state (should we raise or lower
>   * the line level to the GIC).
> @@ -188,6 +203,7 @@ static int kvm_timer_update_state(struct kvm_vcpu *vcpu)
>  {
>  	struct arch_timer_cpu *timer = &vcpu->arch.timer_cpu;
>  	struct arch_timer_context *vtimer = vcpu_vtimer(vcpu);
> +	struct arch_timer_context *ptimer = vcpu_ptimer(vcpu);
>  
>  	/*
>  	 * If userspace modified the timer registers via SET_ONE_REG before
> @@ -201,6 +217,10 @@ static int kvm_timer_update_state(struct kvm_vcpu *vcpu)
>  	if (kvm_timer_should_fire(vcpu, vtimer) != vtimer->irq.level)
>  		kvm_timer_update_mapped_irq(vcpu, !vtimer->irq.level, vtimer);
>  
> +	/* The emulated EL1 physical timer irq is not mapped to hardware */

Maybe a slightly better comment would be saying that we're using a
purely virtual interrupt, unrelated to the hardware interrupt.

> +	if (kvm_timer_should_fire(vcpu, ptimer) != ptimer->irq.level)
> +		kvm_timer_update_irq(vcpu, !ptimer->irq.level, ptimer);
> +
>  	return 0;
>  }

Otherwise looks good.

          M.
-- 
Jazz is not dead. It just smells funny.

  reply	other threads:[~2017-01-29 15:21 UTC|newest]

Thread overview: 127+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27  1:04 [RFC v2 00/10] Provide the EL1 physical timer to the VM Jintack Lim
2017-01-27  1:04 ` Jintack Lim
2017-01-27  1:04 ` [RFC v2 01/10] KVM: arm/arm64: Abstract virtual timer context into separate structure Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-29 11:44   ` Marc Zyngier
2017-01-29 11:44     ` Marc Zyngier
2017-01-29 11:44     ` Marc Zyngier
2017-01-27  1:04 ` [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-29 11:54   ` Marc Zyngier
2017-01-29 11:54     ` Marc Zyngier
2017-01-29 11:54     ` Marc Zyngier
2017-01-30 14:45     ` Christoffer Dall
2017-01-30 14:45       ` Christoffer Dall
2017-01-30 14:45       ` Christoffer Dall
2017-01-30 14:51       ` Marc Zyngier
2017-01-30 14:51         ` Marc Zyngier
2017-01-30 14:51         ` Marc Zyngier
2017-01-30 17:40         ` Jintack Lim
2017-01-30 17:40           ` Jintack Lim
2017-01-30 17:40           ` Jintack Lim
2017-01-30 17:58     ` Jintack Lim
2017-01-30 17:58       ` Jintack Lim
2017-01-30 17:58       ` Jintack Lim
2017-01-30 18:05       ` Marc Zyngier
2017-01-30 18:05         ` Marc Zyngier
2017-01-30 18:05         ` Marc Zyngier
2017-01-30 18:45         ` Jintack Lim
2017-01-30 18:45           ` Jintack Lim
2017-01-27  1:04 ` [RFC v2 03/10] KVM: arm/arm64: Decouple kvm timer functions from virtual timer Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-29 12:01   ` Marc Zyngier
2017-01-29 12:01     ` Marc Zyngier
2017-01-29 12:01     ` Marc Zyngier
2017-01-30 17:17     ` Jintack Lim
2017-01-30 17:17       ` Jintack Lim
2017-01-30 14:49   ` Christoffer Dall
2017-01-30 14:49     ` Christoffer Dall
2017-01-30 14:49     ` Christoffer Dall
2017-01-30 17:18     ` Jintack Lim
2017-01-30 17:18       ` Jintack Lim
2017-01-30 17:18       ` Jintack Lim
2017-01-27  1:04 ` [RFC v2 04/10] KVM: arm/arm64: Add the EL1 physical timer context Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-27  1:04 ` [RFC v2 05/10] KVM: arm/arm64: Initialize the emulated EL1 physical timer Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-29 12:07   ` Marc Zyngier
2017-01-29 12:07     ` Marc Zyngier
2017-01-29 12:07     ` Marc Zyngier
2017-01-30 14:58     ` Christoffer Dall
2017-01-30 14:58       ` Christoffer Dall
2017-01-30 14:58       ` Christoffer Dall
2017-01-30 17:44       ` Marc Zyngier
2017-01-30 17:44         ` Marc Zyngier
2017-01-30 19:04         ` Christoffer Dall
2017-01-30 19:04           ` Christoffer Dall
2017-01-30 19:04           ` Christoffer Dall
2017-02-01 10:08           ` Marc Zyngier
2017-02-01 10:08             ` Marc Zyngier
2017-02-01 10:08             ` Marc Zyngier
2017-01-27  1:04 ` [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-29 15:21   ` Marc Zyngier [this message]
2017-01-29 15:21     ` Marc Zyngier
2017-01-29 15:21     ` Marc Zyngier
2017-01-30 15:02     ` Christoffer Dall
2017-01-30 15:02       ` Christoffer Dall
2017-01-30 17:50       ` Marc Zyngier
2017-01-30 17:50         ` Marc Zyngier
2017-01-30 17:50         ` Marc Zyngier
2017-01-30 18:41         ` Christoffer Dall
2017-01-30 18:41           ` Christoffer Dall
2017-01-30 18:48           ` Marc Zyngier
2017-01-30 18:48             ` Marc Zyngier
2017-01-30 18:48             ` Marc Zyngier
2017-01-30 19:06             ` Christoffer Dall
2017-01-30 19:06               ` Christoffer Dall
2017-01-30 19:06               ` Christoffer Dall
2017-01-31 17:00               ` Marc Zyngier
2017-01-31 17:00                 ` Marc Zyngier
2017-01-31 17:00                 ` Marc Zyngier
2017-02-01  8:02                 ` Christoffer Dall
2017-02-01  8:02                   ` Christoffer Dall
2017-02-01  8:02                   ` Christoffer Dall
2017-02-01  8:04     ` Christoffer Dall
2017-02-01  8:04       ` Christoffer Dall
2017-02-01  8:04       ` Christoffer Dall
2017-02-01  8:40       ` Jintack Lim
2017-02-01  8:40         ` Jintack Lim
2017-02-01  8:40         ` Jintack Lim
2017-02-01 10:07         ` Christoffer Dall
2017-02-01 10:07           ` Christoffer Dall
2017-02-01 10:07           ` Christoffer Dall
2017-02-01 10:17           ` Marc Zyngier
2017-02-01 10:17             ` Marc Zyngier
2017-02-01 10:17             ` Marc Zyngier
2017-02-01 10:01       ` Marc Zyngier
2017-02-01 10:01         ` Marc Zyngier
2017-01-27  1:04 ` [RFC v2 07/10] KVM: arm/arm64: Set a background timer to the earliest timer expiration Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-27  1:04 ` [RFC v2 08/10] KVM: arm/arm64: Set up a background timer for the physical timer emulation Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-27  1:04 ` [RFC v2 09/10] KVM: arm64: Add the EL1 physical timer access handler Jintack Lim
2017-01-27  1:04   ` Jintack Lim
2017-01-27  1:05 ` [RFC v2 10/10] KVM: arm/arm64: Emulate the EL1 phys timer register access Jintack Lim
2017-01-27  1:05   ` Jintack Lim
2017-01-29 15:44   ` Marc Zyngier
2017-01-29 15:44     ` Marc Zyngier
2017-01-29 15:44     ` Marc Zyngier
2017-01-30 17:08     ` Jintack Lim
2017-01-30 17:08       ` Jintack Lim
2017-01-30 17:08       ` Jintack Lim
2017-01-30 17:26       ` Peter Maydell
2017-01-30 17:26         ` Peter Maydell
2017-01-30 17:26         ` Peter Maydell
2017-01-30 17:35         ` Marc Zyngier
2017-01-30 17:35           ` Marc Zyngier
2017-01-30 17:35           ` Marc Zyngier
2017-01-30 17:38         ` Jintack Lim
2017-01-30 17:38           ` Jintack Lim
2017-01-30 17:38           ` Jintack Lim
2017-01-29 15:55 ` [RFC v2 00/10] Provide the EL1 physical timer to the VM Marc Zyngier
2017-01-29 15:55   ` Marc Zyngier
2017-01-29 15:55   ` Marc Zyngier
2017-01-30 19:02   ` Jintack Lim
2017-01-30 19:02     ` Jintack Lim
2017-01-30 19:02     ` 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=86sho199jx.fsf@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=jintack@cs.columbia.edu \
    --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=pbonzini@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.