From: Marc Zyngier <maz@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Barry Song <21cnbao@gmail.com>,
bhelgaas@google.com, tglx@linutronix.de,
Jonathan.Cameron@huawei.com, bilbao@vt.edu, corbet@lwn.net,
gregkh@linuxfoundation.org, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linuxarm@huawei.com, luzmaximilian@gmail.com,
mchehab+huawei@kernel.org, schnelle@linux.ibm.com,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org,
Barry Song <song.bao.hua@hisilicon.com>
Subject: Re: [PATCH v3 0/3] PCI/MSI: Clarify the IRQ sysfs ABI for PCI devices
Date: Tue, 19 Oct 2021 08:39:51 +0100 [thread overview]
Message-ID: <87wnm9o43c.wl-maz@kernel.org> (raw)
In-Reply-To: <20211018215047.GA2265015@bhelgaas>
On Mon, 18 Oct 2021 22:50:47 +0100,
Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> On Wed, Aug 25, 2021 at 06:26:33PM +0800, Barry Song wrote:
> > From: Barry Song <song.bao.hua@hisilicon.com>
> >
> >
> > /sys/bus/pci/devices/.../irq has been there for many years but it has never
> > been documented. This patchset is trying to clarify it.
> >
> > -v3:
> > - Don't attempt to modify the current behaviour of IRQ ABI for MSI-X
> > - Make MSI IRQ ABI more explicit(return 1st IRQ of the IRQ vector)
> > - Add Marc's patch of removing default_irq from the previous comment to
> > the series.
> > Note patch 3/3 indirectly changed the code of pci_restore_msi_state(),
> > drivers/net/ethernet/intel/ice/ice_virtchnl_pf.c is the only driver
> > calling this API. I would appreciate testing done from this driver's
> > maintainers.
> >
> > -v2:
> > - split into two patches according to Bjorn's comments;
> > - Add Greg's Acked-by, thanks for reviewing!
> > https://lore.kernel.org/lkml/20210820223744.8439-1-21cnbao@gmail.com/
> >
> > -v1:
> > https://lore.kernel.org/lkml/20210813122650.25764-1-21cnbao@gmail.com/#t
> >
> > Barry Song (2):
> > Documentation: ABI: sysfs-bus-pci: Add description for IRQ entry
> > PCI/sysfs: Don't depend on pci_dev.irq for IRQ entry
>
> I applied the first two (above) to pci/msi for v5.16, thanks!
>
> As far as I can tell from the discussion so far, they should be safe
> and should preserve all existing behavior. The second patch should
> remove the sysfs dependency on the PCI core to swap the INTx and first
> MSI IRQ values in dev->irq.
>
> Marc's patch below is certainly desirable but my understanding is that
> it requires some driver updates first.
Indeed. It means that there will be an uphill battle to remove the
INTx/MSI confusion in a lot of drivers (Barry says about 700 of them,
and I can't say I'm surprised).
We can probably tackle that as a background task for the next few
releases (I need to relearn Coccinelle for the 27th time...).
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-10-19 7:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 10:26 [PATCH v3 0/3] PCI/MSI: Clarify the IRQ sysfs ABI for PCI devices Barry Song
2021-08-25 10:26 ` [PATCH v3 1/3] Documentation: ABI: sysfs-bus-pci: Add description for IRQ entry Barry Song
2021-08-25 10:26 ` [PATCH v3 2/3] PCI/sysfs: Don't depend on pci_dev.irq " Barry Song
2021-08-25 13:30 ` Marc Zyngier
2021-08-25 10:26 ` [PATCH v3 3/3] PCI/MSI: remove msi_attrib.default_irq in msi_desc Barry Song
2021-08-25 13:38 ` Marc Zyngier
[not found] ` <20210829145552.GA11556@xsang-OptiPlex-9020>
2021-08-31 1:21 ` [PCI/MSI] a4fc4cf388: dmesg.genirq:Flags_mismatch_irq##(mei_me)vs.#(xhci_hcd) Barry Song
2021-08-31 1:36 ` Barry Song
2021-09-02 19:34 ` Winkler, Tomas
2021-10-03 8:32 ` Barry Song
[not found] ` <20211015144528.GA21175@linux.intel.com>
2021-10-16 0:08 ` [LKP] " Barry Song
2021-08-31 8:08 ` Marc Zyngier
2021-08-31 21:36 ` Barry Song
2021-09-01 13:09 ` Marc Zyngier
2021-10-16 10:11 ` [PATCH v3 0/3] PCI/MSI: Clarify the IRQ sysfs ABI for PCI devices Barry Song
2021-10-18 21:50 ` Bjorn Helgaas
2021-10-19 7:39 ` Marc Zyngier [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=87wnm9o43c.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=21cnbao@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bhelgaas@google.com \
--cc=bilbao@vt.edu \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=luzmaximilian@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=schnelle@linux.ibm.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tglx@linutronix.de \
/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).