Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Frank Li <Frank.li@nxp.com>, Niklas Cassel <cassel@kernel.org>
Cc: "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>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Jon Hunter" <jonathanh@nvidia.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] misc: pci_endpoint_test: Handle BAR sizes larger than INT_MAX
Date: Fri, 14 Feb 2025 14:00:15 +0800	[thread overview]
Message-ID: <0ece2ad3-cd80-4339-a1ee-cf6f11810b20@163.com> (raw)
In-Reply-To: <Z64WkB6uiqbSRpS8@lizhi-Precision-Tower-5810>



On 2025/2/13 23:58, Frank Li wrote:
> On Thu, Feb 13, 2025 at 02:39:14PM +0100, Niklas Cassel wrote:
>> Running 'pcitest -b 0' fails with "TEST FAILED" when the BAR0 size
>> is e.g. 8 GB.
> 
> pcitest is not exist now. Does it need update to pci_endpoint_test?
> 

Hi Frank,

Mani has modified the entire pci_endpoint_test test framework, BAR test 
is still required. So Niklas may need to modify the commit message.

392188bb0f6e ("selftests: pci_endpoint: Migrate to Kselftest framework")
e19bde2269ca ("selftests: Move PCI Endpoint tests from tools/pci to 
Kselftests")

Best regards
Hans


      reply	other threads:[~2025-02-14  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 13:39 [PATCH v3] misc: pci_endpoint_test: Handle BAR sizes larger than INT_MAX Niklas Cassel
2025-02-13 15:58 ` Frank Li
2025-02-14  6:00   ` Hans Zhang [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=0ece2ad3-cd80-4339-a1ee-cf6f11810b20@163.com \
    --to=18255117159@163.com \
    --cc=Frank.li@nxp.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --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