From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Rick Wertenbroek <rick.wertenbroek@gmail.com>
Cc: "Damien Le Moal" <dlemoal@kernel.org>,
rick.wertenbroek@heig-vd.ch, alberto.dassatti@heig-vd.ch,
"Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Niklas Cassel" <cassel@kernel.org>,
"Frank Li" <Frank.Li@nxp.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] PCI: endpoint: pci-epf-test: Call pci_epf_test_raise_irq() on failed DMA check
Date: Tue, 20 Aug 2024 14:53:59 +0530 [thread overview]
Message-ID: <20240820092359.tfvmjadm6tfxyqvm@thinkpad> (raw)
In-Reply-To: <CAAEEuhpt_WnxOZeYsMxjwTGZm-FJKoj3at-qPgyAH6D76P9wOA@mail.gmail.com>
On Tue, Aug 20, 2024 at 10:43:56AM +0200, Rick Wertenbroek wrote:
> On Tue, Aug 20, 2024 at 10:18 AM Damien Le Moal <dlemoal@kernel.org> wrote:
> >
> > On 8/20/24 16:10, Rick Wertenbroek wrote:
> > > The pci-epf-test PCI endpoint function /drivers/pci/endpoint/function/pci-epf_test.c
> > > is meant to be used in a PCI endpoint device connected to a host computer
> > > with the host side driver: /drivers/misc/pci_endpoint_test.c.
> > >
> > > The host side driver can request read/write/copy transactions from the
> > > endpoint function and expects an IRQ from the endpoint function once
> > > the read/write/copy transaction is finished. These can be issued with or
> > > without DMA enabled. If the host side driver requests a read/write/copy
> > > transaction with DMA enabled and the endpoint function does not support
> > > DMA, the endpoint would only print an error message and wait for further
> > > commands without sending an IRQ because pci_epf_test_raise_irq() is
> > > skipped in pci_epf_test_cmd_handler(). This results in the host side
> > > driver hanging indefinitely waiting for the IRQ.
> > >
> > > Call pci_epf_test_raise_irq() when a transfer with DMA is requested but
> > > DMA is unsupported. The host side driver will no longer hang but report
> > > an error on transfer (printing "NOT OKAY") thanks to the checksum because
> > > no data was moved.
> > >
> > > Clarify the error message in the endpoint function as "Cannot ..." is
> > > vague and does not state the reason why it cannot be done.
> > >
> > > Signed-off-by: Rick Wertenbroek <rick.wertenbroek@gmail.com>
> > > ---
> > > drivers/pci/endpoint/functions/pci-epf-test.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/pci/endpoint/functions/pci-epf-test.c b/drivers/pci/endpoint/functions/pci-epf-test.c
> > > index 7c2ed6eae53a..b02193cef06e 100644
> > > --- a/drivers/pci/endpoint/functions/pci-epf-test.c
> > > +++ b/drivers/pci/endpoint/functions/pci-epf-test.c
> > > @@ -649,7 +649,8 @@ static void pci_epf_test_cmd_handler(struct work_struct *work)
> > >
> > > if ((READ_ONCE(reg->flags) & FLAG_USE_DMA) &&
> > > !epf_test->dma_supported) {
> > > - dev_err(dev, "Cannot transfer data using DMA\n");
> > > + dev_err(dev, "DMA transfer not supported\n");
> >
> > Should we set the FAIL status flag here ?
> > E.g.:
> > reg->status |= STATUS_READ_FAIL;
> >
> > Note: I have no idea why the status flags are different for the different
> > operations. We should really have a single SUCCESS/FAIL flag common to all
> > operations. So I think we could just do:
> >
> > reg->status |= STATUS_READ_FAIL | STATUS_WRITE_FAIL |
> > STATUS_COPY_FAIL;
> >
> > here, or go back to your v1 and handle the failure in each operation function to
> > set the correct flag.
> >
>
> Good catch, indeed with the check outside of the functions, the status
> FAIL bits are not set. I think setting the status as a combined fail
> flag makes sense, however, it conveys the idea that read/write/copy
> failed whereas only one of them actually failed.
>
> I agree that a single status SUCCESS/FAIL flag would be simpler. But
> changing this would require changes on both sides (EP & RC) and will
> reduce compatibility between EP and RC side driver versions, so I
> would refrain from changing this.
>
I think it is OK to change the status flags and do the right thing. If someone
reports a test failure, then we can ask them to upgrade their kernel. Given that
this this just a test application, I don't think it is a big deal.
- Mani
> I think I still prefer the v1/v2 code because even as it has a little
> bit of duplication it is clear and sets the correct FAIL bit without
> extra logic whereas here we either set all FAIL bits or have to add
> extra logic.
>
> Thank you for spotting this.
>
> > > + pci_epf_test_raise_irq(epf_test, reg);
> > > goto reset_handler;
> > > }
> > >
> >
> > --
> > Damien Le Moal
> > Western Digital Research
> >
>
> Best regards,
> Rick
--
மணிவண்ணன் சதாசிவம்
prev parent reply other threads:[~2024-08-20 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 7:10 [PATCH v3 0/1] PCI: endpoint: pci-epf-test: Call Rick Wertenbroek
2024-08-20 7:10 ` [PATCH v3 1/1] PCI: endpoint: pci-epf-test: Call pci_epf_test_raise_irq() on failed DMA check Rick Wertenbroek
2024-08-20 8:18 ` Damien Le Moal
2024-08-20 8:43 ` Rick Wertenbroek
2024-08-20 8:46 ` Damien Le Moal
2024-08-20 9:23 ` Manivannan Sadhasivam [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=20240820092359.tfvmjadm6tfxyqvm@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=Frank.Li@nxp.com \
--cc=alberto.dassatti@heig-vd.ch \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rick.wertenbroek@gmail.com \
--cc=rick.wertenbroek@heig-vd.ch \
/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
all inboxes | Powered by JetHome®