public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Damien Le Moal" <dlemoal@kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] misc: pci_endpoint_test: Add consecutive BAR test
Date: Thu, 12 Dec 2024 09:02:55 +0100	[thread overview]
Message-ID: <Z1qYr7GRgmXfHdt9@ryzen> (raw)
In-Reply-To: <20241124023922.dpdjublabfnfxrd4@thinkpad>

On Sun, Nov 24, 2024 at 08:09:22AM +0530, Manivannan Sadhasivam wrote:
> On Sat, Nov 16, 2024 at 04:20:45AM +0100, Niklas Cassel wrote:
> > Add a more advanced BAR test that writes all BARs in one go, and then reads
> > them back and verifies that the value matches the BAR number bitwise OR:ed
> > with offset, this allows us to verify:
> > -The BAR number was what we intended to read.
> > -The offset was what we intended to read.
> > 
> > This allows us to detect potential address translation issues on the EP.
> > 
> > Reading back the BAR directly after writing will not allow us to detect the
> > case where inbound address translation on the endpoint incorrectly causes
> > multiple BARs to be redirected to the same memory region (within the EP).
> > 
> > Signed-off-by: Niklas Cassel <cassel@kernel.org>
> 
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>

Thanks for the review!

Could this patch please be picked up?


Kind regards,
Niklas

  reply	other threads:[~2024-12-12  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16  3:20 [PATCH] misc: pci_endpoint_test: Add consecutive BAR test Niklas Cassel
2024-11-24  2:39 ` Manivannan Sadhasivam
2024-12-12  8:02   ` Niklas Cassel [this message]
2024-12-22 20:55 ` 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=Z1qYr7GRgmXfHdt9@ryzen \
    --to=cassel@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --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