All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Leshenko <nikita.leshchenko@oracle.com>
To: kvm@vger.kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com
Cc: idan.brown@oracle.com,
	Nikita Leshenko <nikita.leshchenko@oracle.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH 4/5] KVM: x86: ioapic: Clear Remote IRR when entry is switched to edge-triggered
Date: Sun,  5 Nov 2017 15:52:32 +0200	[thread overview]
Message-ID: <20171105135233.34572-5-nikita.leshchenko@oracle.com> (raw)
In-Reply-To: <20171105135233.34572-1-nikita.leshchenko@oracle.com>

Some OSes (Linux, Xen) use this behavior to clear the Remote IRR bit for
IOAPICs without an EOI register. They simulate the EOI message manually
by changing the trigger mode to edge and then back to level, with the
entry being masked during this.

QEMU implements this feature in commit ed1263c363c9
("ioapic: clear remote irr bit for edge-triggered interrupts")

As a side effect, this commit removes an incorrect behavior where Remote
IRR was cleared when the redirection table entry was rewritten. This is not
consistent with the manual and also opens an opportunity for a strange
behavior when a redirection table entry is modified from an interrupt
handler that handles the same entry: The modification will clear the
Remote IRR bit even though the interrupt handler is still running.

Signed-off-by: Nikita Leshenko <nikita.leshchenko@oracle.com>
Reviewed-by: Liran Alon <liran.alon@oracle.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
---
 arch/x86/kvm/ioapic.c | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/arch/x86/kvm/ioapic.c b/arch/x86/kvm/ioapic.c
index 6df150eaaa78..163d340ee5f8 100644
--- a/arch/x86/kvm/ioapic.c
+++ b/arch/x86/kvm/ioapic.c
@@ -304,8 +304,17 @@ static void ioapic_write_indirect(struct kvm_ioapic *ioapic, u32 val)
 		} else {
 			e->bits &= ~0xffffffffULL;
 			e->bits |= (u32) val;
-			e->fields.remote_irr = 0;
 		}
+
+		/*
+		 * Some OSes (Linux, Xen) assume that Remote IRR bit will
+		 * be cleared by IOAPIC hardware when the entry is configured
+		 * as edge-triggered. This behavior is used to simulate an
+		 * explicit EOI on IOAPICs that don't have the EOI register.
+		 */
+		if (e->fields.trig_mode == IOAPIC_EDGE_TRIG)
+			e->fields.remote_irr = 0;
+
 		mask_after = e->fields.mask;
 		if (mask_before != mask_after)
 			kvm_fire_mask_notifiers(ioapic->kvm, KVM_IRQCHIP_IOAPIC, index, mask_after);
-- 
2.13.3

  parent reply	other threads:[~2017-11-05 13:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-05 13:52 [PATCH 0/5] KVM: x86: Various IOAPIC improvements Nikita Leshenko
2017-11-05 13:52 ` [PATCH 1/5] KVM: x86: ioapic: Fix level-triggered EOI and IOAPIC reconfigure race Nikita Leshenko
2017-11-06  2:00   ` Wanpeng Li
2017-11-06 13:53     ` Nikita Leshchenko
2017-11-06 14:05       ` Paolo Bonzini
2017-11-07  8:13         ` Nikita Leshchenko
2017-11-07 10:18           ` Paolo Bonzini
2017-11-07 23:09             ` Steve Rutherford
2017-11-05 13:52 ` [PATCH 2/5] KVM: x86: ioapic: Don't fire level irq when Remote IRR set Nikita Leshenko
2017-11-06  2:50   ` Wanpeng Li
2017-11-05 13:52 ` [PATCH 3/5] KVM: x86: ioapic: Remove redundant check for Remote IRR in ioapic_set_irq Nikita Leshenko
2017-11-06  3:16   ` Wanpeng Li
2017-11-05 13:52 ` Nikita Leshenko [this message]
2017-11-06  3:30   ` [PATCH 4/5] KVM: x86: ioapic: Clear Remote IRR when entry is switched to edge-triggered Wanpeng Li
2017-11-08  0:16     ` Steve Rutherford
2017-11-08  9:52       ` Nikita Leshchenko
2017-11-08 21:24         ` Steve Rutherford
2017-11-08 21:25           ` Steve Rutherford
2017-11-05 13:52 ` [PATCH 5/5] KVM: x86: ioapic: Preserve read-only values in the redirection table Nikita Leshenko
2017-11-06  3:20   ` Wanpeng Li
2017-11-08  0:18     ` Steve Rutherford
2017-11-10 21:42 ` [PATCH 0/5] KVM: x86: Various IOAPIC improvements Radim Krčmář

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=20171105135233.34572-5-nikita.leshchenko@oracle.com \
    --to=nikita.leshchenko@oracle.com \
    --cc=idan.brown@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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.