From: Heiko Carstens <hca@linux.ibm.com>
To: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: Farhan Ali <alifm@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
mjrosato@linux.ibm.com, agordeev@linux.ibm.com,
gor@linux.ibm.com
Subject: Re: [PATCH v1 1/1] s390/pci: Restore IRQ unconditionally for the zPCI device
Date: Thu, 23 Oct 2025 14:00:03 +0200 [thread overview]
Message-ID: <20251023120003.9536Ca9-hca@linux.ibm.com> (raw)
In-Reply-To: <d611c17f342acc0d00b9921686474007a7d29213.camel@linux.ibm.com>
On Thu, Oct 23, 2025 at 01:18:54PM +0200, Niklas Schnelle wrote:
> On Thu, 2025-10-23 at 09:40 +0200, Heiko Carstens wrote:
> > On Wed, Oct 22, 2025 at 09:47:26AM -0700, Farhan Ali wrote:
> > > Commit c1e18c17bda6 ("s390/pci: add zpci_set_irq()/zpci_clear_irq()"),
> > > introduced the zpci_set_irq() and zpci_clear_irq(), to be used while
> > > resetting a zPCI device.
...
> > The above sounds like this fixes a regression. Is there a reason why
> > there are no Fixes and stable tags?
>
> It doesn't have a fixes tag because at the moment the problem is
> theoretical because no driver uses plain pci_restore_state() in
> recovery. Farhan is working on patches where this would be used in
> vfio-pci / PCI pass-through scenarios though.
>
> The existing drivers re-use their shutdown and initialization routines
> to restore state and end up calling arch_teardown_msi_irqs() and
> arch_setup_msi_irqs() so it works out ok there.
>
> That said, I agree this could and probably should carry a fixes tag
> since the logic is kind of broken even if it doesn't break anything at
> the moment.
Can then somebody :) provide a tag, please? I'll add it when applying;
no need for a new version.
next prev parent reply other threads:[~2025-10-23 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 16:47 [PATCH v1 1/1] s390/pci: Restore IRQ unconditionally for the zPCI device Farhan Ali
2025-10-23 7:40 ` Heiko Carstens
2025-10-23 11:18 ` Niklas Schnelle
2025-10-23 12:00 ` Heiko Carstens [this message]
2025-10-23 12:09 ` Niklas Schnelle
2025-10-23 15:19 ` Heiko Carstens
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=20251023120003.9536Ca9-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=schnelle@linux.ibm.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.