From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Greg Kurz <groug@kaod.org>, Michael Ellerman <mpe@ellerman.id.au>
Cc: lvivier@redhat.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Cédric Le Goater <clg@kaod.org>
Subject: Re: [PATCH v2] powerpc/pseries: Don't enforce MSI affinity with kdump
Date: Sun, 14 Mar 2021 21:01:23 +1100 (AEDT) [thread overview]
Message-ID: <161571587010.138988.17393630047865691595.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210215094506.1196119-1-groug@kaod.org>
On Mon, 15 Feb 2021 10:45:06 +0100, Greg Kurz wrote:
> Depending on the number of online CPUs in the original kernel, it is
> likely for CPU #0 to be offline in a kdump kernel. The associated IRQs
> in the affinity mappings provided by irq_create_affinity_masks() are
> thus not started by irq_startup(), as per-design with managed IRQs.
>
> This can be a problem with multi-queue block devices driven by blk-mq :
> such a non-started IRQ is very likely paired with the single queue
> enforced by blk-mq during kdump (see blk_mq_alloc_tag_set()). This
> causes the device to remain silent and likely hangs the guest at
> some point.
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc/pseries: Don't enforce MSI affinity with kdump
https://git.kernel.org/powerpc/c/f9619d5e5174867536b7e558683bc4408eab833f
cheers
prev parent reply other threads:[~2021-03-14 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 9:45 [PATCH v2] powerpc/pseries: Don't enforce MSI affinity with kdump Greg Kurz
2021-02-15 9:45 ` Greg Kurz
2021-03-14 10:01 ` 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=161571587010.138988.17393630047865691595.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@redhat.com \
--cc=mpe@ellerman.id.au \
--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 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.