From: Niklas Cassel <cassel@kernel.org>
To: Koichiro Den <den@valinux.co.jp>
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jonathan Corbet" <corbet@lwn.net>,
Frank.Li@nxp.com, dlemoal@kernel.org, linux-pci@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] PCI: endpoint: pci-epf-test: Allow overriding default BAR sizes
Date: Tue, 27 Jan 2026 10:47:52 +0100 [thread overview]
Message-ID: <aXiJyDUSj68MLQaa@fedora> (raw)
In-Reply-To: <23lxq2hvynxqmothnkhjtarpklin3prv7tvjlvy3xjnzpn5kdj@ks2qay2tgzc2>
On Tue, Jan 27, 2026 at 12:44:13PM +0900, Koichiro Den wrote:
> On Fri, Jan 23, 2026 at 07:07:48PM +0100, Niklas Cassel wrote:
> > Add bar{0,1,2,3,4,5}_size attributes in configfs, so that the user is not
> > restricted to run pci-epf-test with the hardcoded BAR size values defined
> > in pci-epf-test.c.
> >
> > This code is shamelessly more or less copy pasted from pci-epf-vntb.c
> >
> > Signed-off-by: Niklas Cassel <cassel@kernel.org>
>
> This is useful, thanks!
> I've used this patch as a dependency for my series [1], and it works fine.
>
> Tested-by: Koichiro Den <den@valinux.co.jp>
>
> [1] https://lore.kernel.org/linux-pci/20260124145012.2794108-1-den@valinux.co.jp/
Thank you for testing!
Just to clarify:
Your series is currently not depending on this patch, and neither do I think
that it should.
There will be a trivial conflict when PCI maintainers will try to merge them.
But the solution is to use your new values:
-static size_t bar_size[] = { 512, 512, 1024, 16384, 131072, 1048576 };
+static size_t bar_size[] = { 131072, 131072, 131072, 131072, 131072, 1048576 };
With my new variable name (default_bar_size):
-static size_t bar_size[] = { 512, 512, 1024, 16384, 131072, 1048576 };
+/* default BAR sizes, can be overridden by the user using configfs */
+static size_t default_bar_size[] = { 512, 512, 1024, 16384, 131072, 1048576 };
So AFAICT, it should a one line conflict resolution.
Since it is so trivial, it would be nice if the PCI maintainers could
handle that when applying, but I guess in worst case, one of us will
need to respin.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-01-27 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 18:07 [PATCH] PCI: endpoint: pci-epf-test: Allow overriding default BAR sizes Niklas Cassel
2026-01-26 18:20 ` Frank Li
2026-01-27 3:44 ` Koichiro Den
2026-01-27 9:47 ` Niklas Cassel [this message]
2026-01-28 5:21 ` Koichiro Den
2026-01-28 8:17 ` Manivannan Sadhasivam
2026-01-28 16:35 ` Niklas Cassel
2026-01-28 18:59 ` Niklas Cassel
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=aXiJyDUSj68MLQaa@fedora \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=den@valinux.co.jp \
--cc=dlemoal@kernel.org \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.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