linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Cédric Le Goater <clg@kaod.org>, linuxppc-dev@lists.ozlabs.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] powerpc/xive: Discard disabled interrupts in get_irqchip_state()
Date: Sun, 17 Oct 2021 23:28:03 +1100	[thread overview]
Message-ID: <163447368300.1156783.15492137091707859947.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20211011070203.99726-1-clg@kaod.org>

On Mon, 11 Oct 2021 09:02:03 +0200, Cédric Le Goater wrote:
> When an interrupt is passed through, the KVM XIVE device calls the
> set_vcpu_affinity() handler which raises the P bit to mask the
> interrupt and to catch any in-flight interrupts while routing the
> interrupt to the guest.
> 
> On the guest side, drivers (like some Intels) can request at probe
> time some MSIs and call synchronize_irq() to check that there are no
> in flight interrupts. This will call the XIVE get_irqchip_state()
> handler which will always return true as the interrupt P bit has been
> set on the host side and lock the CPU in an infinite loop.
> 
> [...]

Applied to powerpc/fixes.

[1/1] powerpc/xive: Discard disabled interrupts in get_irqchip_state()
      https://git.kernel.org/powerpc/c/6f779e1d359b8d5801f677c1d49dcfa10bf95674

cheers

      parent reply	other threads:[~2021-10-17 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11  7:02 [PATCH] powerpc/xive: Discard disabled interrupts in get_irqchip_state() Cédric Le Goater
2021-10-11  9:47 ` seeteena
2021-10-11  9:50 ` seeteena
2021-10-17 12:28 ` Michael Ellerman [this message]

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=163447368300.1156783.15492137091707859947.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=clg@kaod.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).