From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: "Niklas Cassel" <cassel@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Damien Le Moal <dlemoal@kernel.org>, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] misc: pci_endpoint_test: Use memcpy_toio()/memcpy_fromio() for BAR tests
Date: Wed, 20 Mar 2024 08:53:12 -0700 [thread overview]
Message-ID: <4cb86057-f252-4f48-8b76-6cb0d8de2ec4@linux.intel.com> (raw)
In-Reply-To: <20240320090106.310955-1-cassel@kernel.org>
Hi,
On 3/20/24 2:01 AM, Niklas Cassel wrote:
> The current code uses writel()/readl(), which has an implicit memory
> barrier for every single readl()/writel().
>
> Additionally, reading 4 bytes at a time over the PCI bus is not really
> optimal, considering that this code is running in an ioctl handler.
>
> Use memcpy_toio()/memcpy_fromio() for BAR tests.
>
> Before patch with a 4MB BAR:
> $ time /usr/bin/pcitest -b 1
> BAR1: OKAY
> real 0m 1.56s
>
> After patch with a 4MB BAR:
> $ time /usr/bin/pcitest -b 1
> BAR1: OKAY
> real 0m 0.54s
>
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> ---
> Changes since v2:
> -Actually free the allocated memory... (thank you Kuppuswamy)
>
> drivers/misc/pci_endpoint_test.c | 68 ++++++++++++++++++++++++++------
> 1 file changed, 55 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
> index 705029ad8eb5..1d361589fb61 100644
> --- a/drivers/misc/pci_endpoint_test.c
> +++ b/drivers/misc/pci_endpoint_test.c
> @@ -272,33 +272,75 @@ static const u32 bar_test_pattern[] = {
> 0xA5A5A5A5,
> };
>
> +static int pci_endpoint_test_bar_memcmp(struct pci_endpoint_test *test,
> + enum pci_barno barno, int offset,
> + void *write_buf, void *read_buf,
> + int size)
> +{
> + memset(write_buf, bar_test_pattern[barno], size);
> + memcpy_toio(test->bar[barno] + offset, write_buf, size);
> +
> + memcpy_fromio(read_buf, test->bar[barno] + offset, size);
> +
> + return memcmp(write_buf, read_buf, size);
> +}
> +
> static bool pci_endpoint_test_bar(struct pci_endpoint_test *test,
> enum pci_barno barno)
> {
> - int j;
> - u32 val;
> - int size;
> + int j, bar_size, buf_size, iters, remain;
> + void *write_buf;
> + void *read_buf;
> struct pci_dev *pdev = test->pdev;
> + bool ret;
>
> if (!test->bar[barno])
> return false;
>
> - size = pci_resource_len(pdev, barno);
> + bar_size = pci_resource_len(pdev, barno);
>
> if (barno == test->test_reg_bar)
> - size = 0x4;
> + bar_size = 0x4;
>
> - for (j = 0; j < size; j += 4)
> - pci_endpoint_test_bar_writel(test, barno, j,
> - bar_test_pattern[barno]);
> + buf_size = min(SZ_1M, bar_size);
Why 1MB limit?
>
> - for (j = 0; j < size; j += 4) {
> - val = pci_endpoint_test_bar_readl(test, barno, j);
> - if (val != bar_test_pattern[barno])
> - return false;
> + write_buf = kmalloc(buf_size, GFP_KERNEL);
> + if (!write_buf)
> + return false;
> +
> + read_buf = kmalloc(buf_size, GFP_KERNEL);
> + if (!read_buf) {
> + ret = false;
> + goto err;
> }
>
> - return true;
> + iters = bar_size / buf_size;
> + for (j = 0; j < iters; j++) {
> + if (pci_endpoint_test_bar_memcmp(test, barno, buf_size * j,
> + write_buf, read_buf,
> + buf_size)) {
> + ret = false;
> + goto err;
> + }
> + }
> +
> + remain = bar_size % buf_size;
> + if (remain) {
> + if (pci_endpoint_test_bar_memcmp(test, barno, buf_size * iters,
> + write_buf, read_buf,
> + remain)) {
> + ret = false;
> + goto err;
> + }
> + }
> +
> + ret = true;
> +
> +err:
> + kfree(write_buf);
> + kfree(read_buf);
> +
> + return ret;
> }
>
> static bool pci_endpoint_test_intx_irq(struct pci_endpoint_test *test)
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2024-03-20 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 9:01 [PATCH v3] misc: pci_endpoint_test: Use memcpy_toio()/memcpy_fromio() for BAR tests Niklas Cassel
2024-03-20 15:53 ` Kuppuswamy Sathyanarayanan [this message]
2024-03-21 8:45 ` Niklas Cassel
2024-03-21 18:16 ` Kuppuswamy Sathyanarayanan
2024-03-22 10:20 ` Manivannan Sadhasivam
2024-03-22 10:29 ` Niklas Cassel
2024-03-22 14:45 ` Manivannan Sadhasivam
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=4cb86057-f252-4f48-8b76-6cb0d8de2ec4@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=arnd@arndb.de \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox