From: Nikolay Borisov <nik.borisov@suse.com>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: Ankit Agrawal <ankita@nvidia.com>,
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,
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,
andriy.shevchenko@linux.intel.com, linux-coco@lists.linux.dev
Subject: Re: [RFC PATCH 1/4] PCI/TSM: Create MMIO descriptors via TDISP Report
Date: Fri, 16 Oct 2026 15:35:28 +0300 [thread overview]
Message-ID: <230ba855-0a7a-4187-aee4-ac551c1cac76@suse.com> (raw)
In-Reply-To: <atIRRUO/t/Fj4VX6@yilunxu-OptiPlex-7050>
On 16.10.26 г. 14:57 ч., Xu Yilun wrote:
>>> +int pci_tsm_mmio_setup(struct pci_dev *pdev, struct pci_tsm_mmio *mmio)
>>> +{
>>> + int i;
>>> +
>>> + device_lock_assert(&pdev->dev);
>>> + if (pdev->dev.driver)
>>> + return -EBUSY;
>>> +
>>> + for (i = 0; i < mmio->nr; i++) {
>>> + struct resource *res = pci_tsm_mmio_resource(mmio, i);
>>> + int j;
>>> +
>>> + if (resource_size(res) == 0 || !(res->flags & IORESOURCE_MEM))
>>> + break;
>>> +
>>> + /* Only require the caller to set the range, init remainder */
>>> + *res = DEFINE_RES_NAMED_DESC(res->start, resource_size(res),
>>> + pci_name(pdev), IORESOURCE_MEM,
>>> + IORES_DESC_ENCRYPTED);
>>> +
>>> + for (j = 0; j < PCI_NUM_RESOURCES; j++)
>>> + if (resource_contains(pci_resource_n(pdev, j), res))
>>> + break;
>>> +
>>> + /* Request is outside of device MMIO */
>>> + if (j >= PCI_NUM_RESOURCES)
>>> + break;
>>> +
>>> + if (insert_resource(&encrypted_iomem_resource, res) != 0)
>>> + break;
>>> + }
>>> +
>>> + if (i >= mmio->nr)
>>> + return 0;
>>
>> Shouldn't this check be if (i == mmio->nr -1 ) i.e all descriptors have been
>> initialized, given the for loop condition i can ever be at most mmio->nr - 1
>> i.e the actual index of a descriptor?
>
> The original if (i >= mmio->nr) check is correct. Valid i is at most mmio->nr -1,
> but you need an invalid i to finish the loop.
Shouldn't the check strictly check for i == mmio->nr the loop
terminating condition, which means "we've initialized ALL mmio
resources" otherwise perform the cleanup, that '>' can never be true.
While not wrong per-se having a strict check would be far clearer, no?
next prev parent reply other threads:[~2026-10-16 12:35 UTC|newest]
Thread overview: 14+ 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 [this message]
2026-10-16 12:37 ` Xu Yilun
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-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-12 19:21 ` Andy Shevchenko
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=230ba855-0a7a-4187-aee4-ac551c1cac76@suse.com \
--to=nik.borisov@suse.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=aik@amd.com \
--cc=alison.schofield@intel.com \
--cc=andriy.shevchenko@linux.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
all inboxes | Powered by JetHome®