From: kernel test robot <lkp@intel.com>
To: Shyam Saini <shyamsaini@linux.microsoft.com>,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, virtualization@lists.linux.dev
Cc: oe-kbuild-all@lists.linux.dev, jgg@ziepe.ca, will@kernel.org,
jacob.pan@linux.microsoft.com, eric.auger@redhat.com,
code@tyhicks.com, eahariha@linux.microsoft.com,
vijayb@linux.microsoft.com, bboscaccy@linux.microsoft.com
Subject: Re: [PATCH v3 3/3] arm-smmu: select suitable MSI IOVA
Date: Fri, 8 Aug 2025 01:55:35 +0800 [thread overview]
Message-ID: <202508080104.M1bnmiMo-lkp@intel.com> (raw)
In-Reply-To: <20250806215539.1240561-4-shyamsaini@linux.microsoft.com>
Hi Shyam,
kernel test robot noticed the following build errors:
[auto build test ERROR on soc/for-next]
[also build test ERROR on linus/master v6.16 next-20250807]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Shyam-Saini/arm-smmu-move-MSI_IOVA-macro-definitions/20250807-055741
base: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git for-next
patch link: https://lore.kernel.org/r/20250806215539.1240561-4-shyamsaini%40linux.microsoft.com
patch subject: [PATCH v3 3/3] arm-smmu: select suitable MSI IOVA
config: um-randconfig-r071-20250807 (https://download.01.org/0day-ci/archive/20250808/202508080104.M1bnmiMo-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 7b8dea265e72c3037b6b1e54d5ab51b7e14f328b)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250808/202508080104.M1bnmiMo-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202508080104.M1bnmiMo-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/iommu/arm/arm-smmu/arm-smmu.c:24:
In file included from include/linux/dma-mapping.h:8:
In file included from include/linux/scatterlist.h:9:
In file included from arch/um/include/asm/io.h:24:
include/asm-generic/io.h:1175:55: warning: performing pointer arithmetic on a null pointer has undefined behavior [-Wnull-pointer-arithmetic]
1175 | return (port > MMIO_UPPER_LIMIT) ? NULL : PCI_IOBASE + port;
| ~~~~~~~~~~ ^
drivers/iommu/arm/arm-smmu/arm-smmu.c:1602:35: error: use of undeclared identifier 'MSI_IOVA_BASE'
1602 | static const u64 msi_bases[] = { MSI_IOVA_BASE, MSI_IOVA_BASE2 };
| ^~~~~~~~~~~~~
>> drivers/iommu/arm/arm-smmu/arm-smmu.c:1602:50: error: use of undeclared identifier 'MSI_IOVA_BASE2'
1602 | static const u64 msi_bases[] = { MSI_IOVA_BASE, MSI_IOVA_BASE2 };
| ^~~~~~~~~~~~~~
>> drivers/iommu/arm/arm-smmu/arm-smmu.c:1610:23: error: invalid application of 'sizeof' to an incomplete type 'const u64[]' (aka 'const unsigned long long[]')
1610 | for (int i = 0; i != ARRAY_SIZE(msi_bases); i++) {
| ^~~~~~~~~~~~~~~~~~~~~
include/linux/array_size.h:11:32: note: expanded from macro 'ARRAY_SIZE'
11 | #define ARRAY_SIZE(arr) (sizeof(arr) / sizeof((arr)[0]) + __must_be_array(arr))
| ^~~~~
drivers/iommu/arm/arm-smmu/arm-smmu.c:1613:44: error: use of undeclared identifier 'MSI_IOVA_LENGTH'
1613 | if (resv_region_intersects(msi_bases[i], MSI_IOVA_LENGTH, head))
| ^~~~~~~~~~~~~~~
drivers/iommu/arm/arm-smmu/arm-smmu.c:1616:50: error: use of undeclared identifier 'MSI_IOVA_LENGTH'
1616 | region = iommu_alloc_resv_region(msi_bases[i], MSI_IOVA_LENGTH, prot,
| ^~~~~~~~~~~~~~~
1 warning and 5 errors generated.
vim +/MSI_IOVA_BASE2 +1602 drivers/iommu/arm/arm-smmu/arm-smmu.c
1596
1597 static void arm_smmu_get_resv_regions(struct device *dev,
1598 struct list_head *head)
1599 {
1600 int prot = IOMMU_WRITE | IOMMU_NOEXEC | IOMMU_MMIO;
1601
> 1602 static const u64 msi_bases[] = { MSI_IOVA_BASE, MSI_IOVA_BASE2 };
1603
1604 iommu_dma_get_resv_regions(dev, head);
1605
1606 /*
1607 * Use the first msi_base that does not intersect with a platform
1608 * reserved region. The SW MSI base selection is entirely arbitrary.
1609 */
> 1610 for (int i = 0; i != ARRAY_SIZE(msi_bases); i++) {
1611 struct iommu_resv_region *region;
1612
1613 if (resv_region_intersects(msi_bases[i], MSI_IOVA_LENGTH, head))
1614 continue;
1615
1616 region = iommu_alloc_resv_region(msi_bases[i], MSI_IOVA_LENGTH, prot,
1617 IOMMU_RESV_SW_MSI, GFP_KERNEL);
1618 if (!region)
1619 return;
1620
1621 list_add_tail(®ion->list, head);
1622 return;
1623 }
1624 }
1625
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-07 17:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 21:55 [PATCH v3 0/3] arm-smmu: select suitable MSI IOVA Shyam Saini
2025-08-06 21:55 ` [PATCH v3 1/3] arm-smmu: move MSI_IOVA macro definitions Shyam Saini
2025-08-07 14:32 ` kernel test robot
2025-08-06 21:55 ` [PATCH v3 2/3] iommu/of: fix device tree configuration for PCI devices Shyam Saini
2025-08-08 12:15 ` Jason Gunthorpe
2025-08-14 23:30 ` Shyam Saini
2025-08-15 0:39 ` Jason Gunthorpe
2025-08-15 2:32 ` Shyam Saini
2025-08-18 15:53 ` Jason Gunthorpe
2025-08-26 1:15 ` Shyam Saini
2025-08-26 12:36 ` Jason Gunthorpe
2025-08-26 22:19 ` Shyam Saini
2025-08-06 21:55 ` [PATCH v3 3/3] arm-smmu: select suitable MSI IOVA Shyam Saini
2025-08-06 23:58 ` Jason Gunthorpe
2025-08-07 17:55 ` kernel test robot [this message]
2025-08-11 22:34 ` Jacob Pan
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=202508080104.M1bnmiMo-lkp@intel.com \
--to=lkp@intel.com \
--cc=bboscaccy@linux.microsoft.com \
--cc=code@tyhicks.com \
--cc=devicetree@vger.kernel.org \
--cc=eahariha@linux.microsoft.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jacob.pan@linux.microsoft.com \
--cc=jgg@ziepe.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shyamsaini@linux.microsoft.com \
--cc=vijayb@linux.microsoft.com \
--cc=virtualization@lists.linux.dev \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).