From: Niklas Cassel <cassel@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: bhelgaas@google.com, kw@linux.com, linux-pci@vger.kernel.org,
Damien Le Moal <dlemoal@kernel.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Subject: Re: [PATCH 7/7] misc: pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO
Date: Tue, 18 Mar 2025 11:38:11 +0100 [thread overview]
Message-ID: <Z9lNE68x1CIIUlaM@ryzen> (raw)
In-Reply-To: <Z9lArl5AUA7vbKVA@ryzen>
On Tue, Mar 18, 2025 at 10:45:18AM +0100, Niklas Cassel wrote:
> On Tue, Mar 18, 2025 at 02:26:56PM +0530, Manivannan Sadhasivam wrote:
> > >
> > > I guess one option would be to remove the
> > > "pci_ep_ioctl(PCITEST_SET_IRQTYPE, 1);" calls from the test cases that you
> > > added, and then let the test cases themselves set the proper irq_type in
> > > the BAR register. But, wouldn't that be an API change? READ/WRITE/COPY
> > > test ioctls have always respected the (a successful) PCITEST_SET_IRQTYPE,
> > > now all of a sudden, they shouldn't?
> > >
> >
> > This makes no difference IMO. The previous behavior which you explained above,
> > ignored the result of 'pcitest -i 1'. And it was not user configurable. I think
> > the original intention was to use MSI for tests if available, else use whatever
> > the platform supports.
> >
> > If you want to restore the original behavior, you should remove the ASSERT_EQ()
> > from READ/WRITE/COPY tests first. Then to ensure that the tests make use of the
> > supported IRQ type, you can have the logic in the READ/WRITE/COPY tests itself.
> > If test->irq_type != PCITEST_IRQ_TYPE_UNDEFINED, then just use whatever the
> > test->irq_type is. Otherwise, use whatever the platform supports.
>
> I can submit a patch series that modifies PCITEST_{READ,WRITE,COPY} to always
> figure out the IRQ type to use by themselves.
>
> But you can't have the cake and eat it too.
>
> Either PCITEST_{READ,WRITE,COPY} always ignores PCITEST_SET_IRQTYPE or
> they don't always ignore PCITEST_SET_IRQTYPE.
>
> Only ignoring it "if test->irq_type != PCITEST_IRQ_TYPE_UNDEFINED"
> makes no sense IMO.
Please have a look at:
https://lore.kernel.org/linux-pci/20250318103330.1840678-6-cassel@kernel.org/T/#t
I hope that it addresses your concerns.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-03-18 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 11:10 [PATCH 0/7] pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO Niklas Cassel
2025-03-10 11:10 ` [PATCH 1/7] PCI: endpoint: pcitest: Add IRQ_TYPE_* defines to UAPI header Niklas Cassel
2025-03-10 11:10 ` [PATCH 2/7] misc: pci_endpoint_test: Use IRQ_TYPE_* defines from " Niklas Cassel
2025-03-10 11:10 ` [PATCH 3/7] selftests: pci_endpoint: " Niklas Cassel
2025-03-10 11:10 ` [PATCH 4/7] PCI: endpoint: Add intx_capable to epc_features Niklas Cassel
2025-03-21 21:50 ` Bjorn Helgaas
2025-03-21 21:55 ` Niklas Cassel
2025-03-21 22:42 ` Bjorn Helgaas
2025-03-26 6:25 ` Krzysztof Wilczyński
2025-03-10 11:10 ` [PATCH 5/7] PCI: dw-rockchip: EP mode cannot raise INTx interrupts Niklas Cassel
2025-03-10 11:10 ` [PATCH 6/7] PCI: endpoint: pci-epf-test: Expose supported IRQ types in CAPS register Niklas Cassel
2025-03-10 11:10 ` [PATCH 7/7] misc: pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO Niklas Cassel
2025-03-14 12:45 ` Manivannan Sadhasivam
2025-03-14 17:25 ` Niklas Cassel
2025-03-18 8:56 ` Manivannan Sadhasivam
2025-03-18 9:45 ` Niklas Cassel
2025-03-18 10:38 ` Niklas Cassel [this message]
2025-03-10 13:47 ` [PATCH 0/7] " Krzysztof Wilczyński
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=Z9lNE68x1CIIUlaM@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=dlemoal@kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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.