All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Pau Monne <roger.pau@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>
Subject: [PATCH v3 1/6] x86/vioapic: top word redir entry writes don't trigger interrupts
Date: Tue, 26 Jan 2021 14:45:16 +0100	[thread overview]
Message-ID: <20210126134521.25784-2-roger.pau@citrix.com> (raw)
In-Reply-To: <20210126134521.25784-1-roger.pau@citrix.com>

Top word writes just update the destination of the interrupt, but
since there's no change on the masking or the triggering mode no
guest interrupt injection can result of such write. Add an assert to
that effect.

Requested-by: Jan Beulich <jbeulich@suse.com>
Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
---
Changes since v2:
 - New in this version.
---
 xen/arch/x86/hvm/vioapic.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/xen/arch/x86/hvm/vioapic.c b/xen/arch/x86/hvm/vioapic.c
index 804bc77279..e3ee747b7d 100644
--- a/xen/arch/x86/hvm/vioapic.c
+++ b/xen/arch/x86/hvm/vioapic.c
@@ -262,6 +262,8 @@ static void vioapic_write_redirent(
               !ent.fields.remote_irr &&
               hvm_irq->gsi_assert_count[gsi] )
     {
+        /* A top word write should never trigger an interrupt injection. */
+        ASSERT(!top_word);
         pent->fields.remote_irr = 1;
         vioapic_deliver(vioapic, idx);
     }
-- 
2.29.2



  reply	other threads:[~2021-01-26 13:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 13:45 [PATCH v3 0/6] x86/intr: HVM guest interrupt handling fixes/cleanup Roger Pau Monne
2021-01-26 13:45 ` Roger Pau Monne [this message]
2021-01-26 15:24   ` [PATCH v3 1/6] x86/vioapic: top word redir entry writes don't trigger interrupts Jan Beulich
2021-01-26 13:45 ` [PATCH v3 2/6] x86/vioapic: issue EOI to dpci when switching pin to edge trigger mode Roger Pau Monne
2021-01-26 15:25   ` Jan Beulich
2021-01-26 13:45 ` [PATCH v3 3/6] x86/vpic: force int output to low when in init mode Roger Pau Monne
2021-01-26 16:50   ` Jan Beulich
2021-01-26 13:45 ` [PATCH v3 4/6] x86/vpic: don't trigger unmask event until end of init Roger Pau Monne
2021-01-26 16:53   ` Jan Beulich
2021-01-26 13:45 ` [PATCH v3 5/6] x86/vpic: issue dpci EOI for cleared pins at ICW1 Roger Pau Monne
2021-01-26 16:57   ` Jan Beulich
2021-01-27  9:15     ` Roger Pau Monné
2021-01-27  9:30       ` Jan Beulich
2021-04-20  9:32     ` Jan Beulich
2021-01-26 13:45 ` [PATCH v3 6/6] x86/dpci: remove the dpci EOI timer Roger Pau Monne
2021-01-26 17:07 ` [PATCH v3 0/6] x86/intr: HVM guest interrupt handling fixes/cleanup Jan Beulich
2021-01-27  9:21   ` Roger Pau Monné

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=20210126134521.25784-2-roger.pau@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.org \
    /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.