public inbox for kvmarm@lists.cs.columbia.edu
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Christoffer Dall <christoffer.dall@arm.com>,
	Andrew Jones <drjones@redhat.com>
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] KVM: arm/arm64: fix emulated ptimer irq injection
Date: Tue, 28 May 2019 13:25:52 +0100	[thread overview]
Message-ID: <3f9d398b-3be2-5988-d3f9-01b28c4ccb1c@arm.com> (raw)
In-Reply-To: <20190528110152.GA6775@e113682-lin.lund.arm.com>

On 28/05/2019 12:01, Christoffer Dall wrote:
> On Mon, May 27, 2019 at 01:46:19PM +0200, Andrew Jones wrote:
>> The emulated ptimer needs to track the level changes, otherwise the
>> the interrupt will never get deasserted, resulting in the guest getting
>> stuck in an interrupt storm if it enables ptimer interrupts. This was
>> found with kvm-unit-tests; the ptimer tests hung as soon as interrupts
>> were enabled. Typical Linux guests don't have a problem as they prefer
>> using the virtual timer.
>>
>> Fixes: bee038a674875 ("KVM: arm/arm64: Rework the timer code to use a timer_map")
>> Signed-off-by: Andrew Jones <drjones@redhat.com>
>> ---
>>  virt/kvm/arm/arch_timer.c | 7 ++++++-
>>  1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
>> index 7fc272ecae16..9f5d8cc8b5e5 100644
>> --- a/virt/kvm/arm/arch_timer.c
>> +++ b/virt/kvm/arm/arch_timer.c
>> @@ -324,10 +324,15 @@ static void kvm_timer_update_irq(struct kvm_vcpu *vcpu, bool new_level,
>>  static void timer_emulate(struct arch_timer_context *ctx)
>>  {
>>  	bool should_fire = kvm_timer_should_fire(ctx);
>> +	struct timer_map map;
>> +
>> +	get_timer_map(ctx->vcpu, &map);
>>  
>>  	trace_kvm_timer_emulate(ctx, should_fire);
>>  
>> -	if (should_fire) {
>> +	if (ctx == map.emul_ptimer && should_fire != ctx->irq.level) {
>> +		kvm_timer_update_irq(ctx->vcpu, !ctx->irq.level, ctx);
>> +	} else if (should_fire) {
>>  		kvm_timer_update_irq(ctx->vcpu, true, ctx);
>>  		return;
>>  	}
> 
> Hmm, this doesn't feel completely right.
> 
> Lowering the line of an emulated timer should only ever happen when the
> guest (or user space) writes to one of the system registers for that
> timer, which should be trapped and that should cause an update of the
> line.
> 
> Are we missing a call to kvm_timer_update_irq() from
> kvm_arm_timer_set_reg() ?

Which is exactly what we removed in 6bc210003dff, for good reasons.

Looking at kvm_arm_timer_write_sysreg(), we end-up calling kvm_timer_vcpu_load, but not updating the irq status.

How about something like this instead (untested):

diff --git a/virt/kvm/arm/arch_timer.c b/virt/kvm/arm/arch_timer.c
index 7fc272ecae16..6a418dcc5433 100644
--- a/virt/kvm/arm/arch_timer.c
+++ b/virt/kvm/arm/arch_timer.c
@@ -882,10 +882,14 @@ void kvm_arm_timer_write_sysreg(struct kvm_vcpu *vcpu,
 				enum kvm_arch_timer_regs treg,
 				u64 val)
 {
+	struct arch_timer_context *timer;
+
 	preempt_disable();
 	kvm_timer_vcpu_put(vcpu);
 
-	kvm_arm_timer_write(vcpu, vcpu_get_timer(vcpu, tmr), treg, val);
+	timer = vcpu_get_timer(vcpu, tmr);
+	kvm_arm_timer_write(vcpu, timer, treg, val);
+	kvm_timer_update_irq(vcpu, kvm_timer_should_fire(timer), timer);
 
 	kvm_timer_vcpu_load(vcpu);
 	preempt_enable();

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2019-05-28 12:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 11:46 [PATCH] KVM: arm/arm64: fix emulated ptimer irq injection Andrew Jones
2019-05-28 11:01 ` Christoffer Dall
2019-05-28 12:25   ` Marc Zyngier [this message]
2019-05-28 13:12     ` Christoffer Dall
2019-05-28 13:40       ` Andrew Jones
2019-05-28 16:08         ` Marc Zyngier
2019-05-29  5:19           ` Andrew Jones
2019-05-29  9:08           ` Christoffer Dall
2019-05-29  9:13             ` Marc Zyngier
2019-05-29 10:03               ` Christoffer Dall
2019-06-03 12:14                 ` Andrew Jones
2019-06-13 10:01                   ` Marc Zyngier
2019-06-13 15:45                     ` 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=3f9d398b-3be2-5988-d3f9-01b28c4ccb1c@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=drjones@redhat.com \
    --cc=kvmarm@lists.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox