public inbox for kvmarm@lists.cs.columbia.edu
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
	Christoffer Dall <christoffer.dall@arm.com>
Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] kvm: arm/arm64: Fix emulated physical timer IRQ injection
Date: Wed, 25 Jul 2018 10:21:26 +0100	[thread overview]
Message-ID: <20180725092128.11534-1-andre.przywara@arm.com> (raw)

Hi,

those two patches fix the (physical EL1) arch timer emulation in KVM,
which missed to inject the timer IRQ if the vCPU was asleep when the
timer expired. This can be checked by a new kvm-unit-tests test [1].

I am now taking Christoffer's approach, which keeps phys_timer_emulate()
mostly as it is, and adds the explicit IRQ injection check in the caller.
This turned out to fit better into the upcoming arch timer rework.

Cheers,
Andre.

[1] https://lists.cs.columbia.edu/pipermail/kvmarm/2018-July/032220.html

Christoffer Dall (2):
  KVM: arm/arm64: Fix potential loss of ptimer interrupts
  KVM: arm/arm64: Fix lost IRQs from emulated physcial timer when
    blocked

 virt/kvm/arm/arch_timer.c | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

-- 
2.14.4

             reply	other threads:[~2018-07-25  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  9:21 Andre Przywara [this message]
2018-07-25  9:21 ` [PATCH v3 1/2] KVM: arm/arm64: Fix potential loss of ptimer interrupts Andre Przywara
2018-07-25  9:21 ` [PATCH v3 2/2] KVM: arm/arm64: Fix lost IRQs from emulated physcial timer when blocked Andre Przywara
  -- strict thread matches above, loose matches on Subject: below --
2018-07-25  9:19 [PATCH v3 0/2] kvm: arm/arm64: Fix emulated physical timer IRQ injection Andre Przywara

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=20180725092128.11534-1-andre.przywara@arm.com \
    --to=andre.przywara@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox