[Devel,RHEL7,COMMIT] ms/KVM: i8254: change PIT discard tick policy

Submitted by Konstantin Khorenko on Dec. 9, 2016, 1:23 p.m.


Message ID 201612091323.uB9DNMkQ023782@finist_cl7.x64_64.work.ct
State New
Series "KVM-PIT discard mode fixes"
Headers show

Commit Message

Konstantin Khorenko Dec. 9, 2016, 1:23 p.m.
The commit is pushed to "branch-rh7-3.10.0-327.36.1.vz7.20.x-ovz" and will appear at https://src.openvz.org/scm/ovz/vzkernel.git
after rh7-3.10.0-327.36.1.vz7.20.14
commit bb75ae85ffe5b4998ac6fc1effb7f680dc3ceb93
Author: Radim Krčmář <rkrcmar@redhat.com>
Date:   Fri Dec 9 17:23:22 2016 +0400

    ms/KVM: i8254: change PIT discard tick policy
    Discard policy uses ack_notifiers to prevent injection of PIT interrupts
    before EOI from the last one.
    This patch changes the policy to always try to deliver the interrupt,
    which makes a difference when its vector is in ISR.
    Old implementation would drop the interrupt, but proposed one injects to
    IRR, like real hardware would.
    The old policy breaks legacy NMI watchdogs, where PIT is used through
    virtual wire (LVT0): PIT never sends an interrupt before receiving EOI,
    thus a guest deadlock with disabled interrupts will stop NMIs.
    Note that NMI doesn't do EOI, so PIT also had to send a normal interrupt
    through IOAPIC.  (KVM's PIT is deeply rotten and luckily not used much
    in modern systems.)
    Even though there is a chance of regressions, I think we can fix the
    LVT0 NMI bug without introducing a new tick policy.
    Cc: <stable@vger.kernel.org>
    Reported-by: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>
    Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
    Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
    ms commit 7dd0fdff145c5be7146d0ac06732ae3613412ac1
    ("KVM: i8254: change PIT discard tick policy")
    Fixes https://jira.sw.ru/browse/PSBM-56972
    Signed-off-by: Evgeny Yakovlev <eyakovlev@virtuozzo.com>
    Patchset description:
    KVM-PIT discard mode fixes
    This is a backport of upstream kvm-pit lost tick policy 'discard' fixes
    Radim Krčmář (4):
      KVM: i8254: change PIT discard tick policy
      KVM: i8254: simplify atomics in kvm_pit_ack_irq
      KVM: i8254: add kvm_pit_reset_reinject
      KVM: i8254: use atomic_t instead of pit.inject_lock
 arch/x86/kvm/i8254.c | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

Patch hide | download patch | download mbox

diff --git a/arch/x86/kvm/i8254.c b/arch/x86/kvm/i8254.c
index 1406ffd..b0a706d 100644
--- a/arch/x86/kvm/i8254.c
+++ b/arch/x86/kvm/i8254.c
@@ -244,7 +244,7 @@  static void kvm_pit_ack_irq(struct kvm_irq_ack_notifier *kian)
 		 * PIC is being reset.  Handle it gracefully here
-	else if (value > 0)
+	else if (value > 0 && ps->reinject)
 		/* in this case, we had multiple outstanding pit interrupts
 		 * that we needed to inject.  Reinject
@@ -287,7 +287,9 @@  static void pit_do_work(struct kthread_work *work)
 	 * last one has been acked.
-	if (ps->irq_ack) {
+	if (!ps->reinject)
+		inject = 1;
+	else if (ps->irq_ack) {
 		ps->irq_ack = 0;
 		inject = 1;
@@ -316,10 +318,10 @@  static enum hrtimer_restart pit_timer_fn(struct hrtimer *data)
 	struct kvm_kpit_state *ps = container_of(data, struct kvm_kpit_state, timer);
 	struct kvm_pit *pt = ps->kvm->arch.vpit;
-	if (ps->reinject || !atomic_read(&ps->pending)) {
+	if (ps->reinject)
-		queue_kthread_work(&pt->worker, &pt->expired);
-	}
+	queue_kthread_work(&pt->worker, &pt->expired);
 	if (ps->is_periodic) {
 		hrtimer_add_expires_ns(&ps->timer, ps->period);