From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ankit Agrawal <ankita@nvidia.com>
Cc: linux-cxl@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, dave@stgolabs.net,
jic23@kernel.org, dave.jiang@intel.com,
alison.schofield@intel.com, vishal.l.verma@intel.com,
jgg@nvidia.com, aneesh.kumar@kernel.org, aik@amd.com,
yilun.xu@linux.intel.com, iweiny@kernel.org,
ming.li@zohomail.com, icheng@nvidia.com, bhelgaas@google.com,
smadhavan@nvidia.com, ilpo.jarvinen@linux.intel.com,
Smita.KoralahalliChannabasappa@amd.com,
linux-coco@lists.linux.dev
Subject: Re: [RFC PATCH 3/4] PCI/TSM: Derive the coherent-range IPA from CXL
Date: Mon, 12 Oct 2026 22:21:41 +0300 [thread overview]
Message-ID: <as0zRXh5f5kjULVI@ashevche-desk.local> (raw)
In-Reply-To: <20261005070252.84810-4-ankita@nvidia.com>
On Mon, Oct 05, 2026 at 09:02:51AM +0200, Ankit Agrawal wrote:
> The DevIf report range with range ID 0xffff describes the device's
> coherent (CXL) memory window and unlike every other reported range
> carries no BAR number. Recognize
> PCI_TSM_DEVIF_REPORT_MMIO_RANGE_ID_COHERENT and recover that window's
> address from the CXL side of the device instead of treating it as a
> BAR-relative offset.
>
> pci_tsm_coherent_range() resolves the window from pdev->coh_resource[],
> snapshotted once with the committed CXL HDM decoders range. The
> range to IPA conversion is applied onto range_base/range_len using
> pdev->coh_resource[]. The ascending BAR order checks stay on the BAR
> path only. The coherent range is required to be the last report entry
> and is not part of the BAR sequence.
>
> An HDM decoded window lives in the CXL Fixed Memory Window and is not
> part of a BAR. So by construction, no pci_dev resource contains it. So
> the function pci_tsm_coh_resource_contains() validates the range against
> pdev->coh_resource[] instead; the same known-good snapshot
> pci_tsm_coherent_range() already trusts.
> Assisted-by: Claude:sonnet-5
Assisted-by: LLM
...
> +static bool pci_tsm_coh_resource_contains(struct pci_dev *pdev,
> + const struct resource *res)
> +{
> + int i;
> +
> + for (i = 0; i < PCI_CXL_MAX_COHERENT_RANGES; i++) {
for (int i = 0...)
> + struct resource *coh_res = &pdev->coh_resource[i];
pci_resource_n()
> + if ((coh_res->flags & IORESOURCE_MEM) &&
> + resource_contains(coh_res, res))
> + return true;
> + }
> +
> + return false;
> +}
...
> + for (j = 0; j < PCI_NUM_RESOURCES; j++)
> + if (resource_contains(pci_resource_n(pdev, j), res))
> + break;
pci_dev_for_each_resource()
...
> +static int pci_tsm_coherent_range(struct pci_dev *pdev, u64 *out_base,
> + u64 *out_size)
Instead of the last two you can use struct range.
> +{
> + for (int i = 0; i < PCI_CXL_MAX_COHERENT_RANGES; i++) {
> + struct resource *res = &pdev->coh_resource[i];
pci_resource_n()
> + if (!(res->flags & IORESOURCE_MEM))
> + continue;
resource_type()
> + *out_base = res->start;
> + *out_size = resource_size(res);
> + return 0;
> + }
> +
> + return -ENODEV;
> +}
...
> + if (pci_tsm_coherent_range(pdev, &range_base,
> + &range_len)) {
I would leave it on a single line.
> + pci_dbg(pdev, "No CXL region or committed HDM decoder for coherent reporting range\n");
> + return NULL;
> + }
...
> + range_off = coherent ? tsm_offset :
> + tsm_offset - reporting_bar_base;
Indentation is broken. I think it's better to read when it's a single line.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-12 19:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 7:02 [RFC PATCH 0/4] PCI/TSM: Resolve TDISP coherent (CXL) ranges from precommitted HDM decoders Ankit Agrawal
2026-10-05 7:02 ` [RFC PATCH 1/4] PCI/TSM: Create MMIO descriptors via TDISP Report Ankit Agrawal
2026-10-05 11:17 ` Bradley Morgan
2026-10-14 14:01 ` Nikolay Borisov
2026-10-16 11:57 ` Xu Yilun
2026-10-16 12:35 ` Nikolay Borisov
2026-10-16 12:37 ` Xu Yilun
2026-10-20 8:19 ` Ankit Agrawal
2026-10-16 12:30 ` Xu Yilun
2026-10-05 7:02 ` [RFC PATCH 2/4] PCI/CXL: Populate and insert/remove pdev->coh_resource[] Ankit Agrawal
2026-10-07 19:27 ` Bowman, Terry
2026-10-20 8:41 ` Ankit Agrawal
2026-10-22 20:26 ` Bowman, Terry
2026-10-20 9:24 ` Richard Cheng
2026-10-20 9:37 ` Richard Cheng
2026-10-22 11:12 ` Ankit Agrawal
2026-10-05 7:02 ` [RFC PATCH 3/4] PCI/TSM: Derive the coherent-range IPA from CXL Ankit Agrawal
2026-10-06 16:13 ` Dave Jiang
2026-10-20 9:06 ` Ankit Agrawal
2026-10-12 19:21 ` Andy Shevchenko [this message]
2026-10-20 9:14 ` Ankit Agrawal
2026-10-20 9:30 ` Andy Shevchenko
2026-10-20 9:35 ` Ankit Agrawal
2026-10-05 7:02 ` [RFC PATCH 4/4] PCI/TSM: Support multiple coherent ranges via coh_idx Ankit Agrawal
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=as0zRXh5f5kjULVI@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=aik@amd.com \
--cc=alison.schofield@intel.com \
--cc=aneesh.kumar@kernel.org \
--cc=ankita@nvidia.com \
--cc=bhelgaas@google.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=icheng@nvidia.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=iweiny@kernel.org \
--cc=jgg@nvidia.com \
--cc=jic23@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=smadhavan@nvidia.com \
--cc=vishal.l.verma@intel.com \
--cc=yilun.xu@linux.intel.com \
/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