From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: kernel test robot <lkp@intel.com>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Jason Gunthorpe <jgg@nvidia.com>,
"Kevin Tian" <kevin.tian@intel.com>
Subject: RE: [linux-next:master 9539/12880] drivers/iommu/io-pgtable-arm.c:772:50: error: 'IOMMU_DIRTY_NO_CLEAR' undeclared
Date: Fri, 12 Jul 2024 10:22:49 +0000 [thread overview]
Message-ID: <84de5d98f80f4890943eada39b795fec@huawei.com> (raw)
In-Reply-To: <202407121602.HL9ih1it-lkp@intel.com>
> -----Original Message-----
> From: kernel test robot <lkp@intel.com>
> Sent: Friday, July 12, 2024 9:21 AM
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> Cc: oe-kbuild-all@lists.linux.dev; Linux Memory Management List <linux-
> mm@kvack.org>; Will Deacon <will@kernel.org>; Ryan Roberts
> <ryan.roberts@arm.com>; Jason Gunthorpe <jgg@nvidia.com>; Kevin Tian
> <kevin.tian@intel.com>
> Subject: [linux-next:master 9539/12880] drivers/iommu/io-pgtable-
> arm.c:772:50: error: 'IOMMU_DIRTY_NO_CLEAR' undeclared
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> head: 3fe121b622825ff8cc995a1e6b026181c48188db
> commit: 4fe88fd8b4aecb7f9680bf898811db76b94095a9 [9539/12880]
> iommu/io-pgtable-arm: Add read_and_clear_dirty() support
> config: arm-buildonly-randconfig-r005-20220402
> (https://download.01.org/0day-ci/archive/20240712/202407121602.HL9ih1it-
> lkp@intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 13.3.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-
> ci/archive/20240712/202407121602.HL9ih1it-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/202407121602.HL9ih1it-
> lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> drivers/iommu/io-pgtable-arm.c: In function 'io_pgtable_visit_dirty':
> >> drivers/iommu/io-pgtable-arm.c:772:50: error:
> 'IOMMU_DIRTY_NO_CLEAR' undeclared (first use in this function)
> 772 | if (!(walk_data->flags & IOMMU_DIRTY_NO_CLEAR))
Looks like we need to move the IOMMU_DIRTY_NO_CLEAR define in iommu.h
to cover !CONFIG_IOMMU_API case.
---x---
diff --git a/include/linux/iommu.h b/include/linux/iommu.h
index 7bc8dff7cf6d..104ce84647d4 100644
--- a/include/linux/iommu.h
+++ b/include/linux/iommu.h
@@ -317,6 +317,9 @@ enum iommu_dev_features {
#define IOMMU_PASID_INVALID (-1U)
typedef unsigned int ioasid_t;
+/* Read but do not clear any dirty bits */
+#define IOMMU_DIRTY_NO_CLEAR (1 << 0)
+
#ifdef CONFIG_IOMMU_API
/**
@@ -353,9 +356,6 @@ struct iommu_dirty_bitmap {
struct iommu_iotlb_gather *gather;
};
-/* Read but do not clear any dirty bits */
-#define IOMMU_DIRTY_NO_CLEAR (1 << 0)
-
/**
* struct iommu_dirty_ops - domain specific dirty tracking operations
* @set_dirty_tracking: Enable or Disable dirty tracking on the iommu domain
I will sent out a patch.
Thanks,
Shameer
prev parent reply other threads:[~2024-07-12 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 8:20 kernel test robot
2024-07-12 10:22 ` Shameerali Kolothum Thodi [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=84de5d98f80f4890943eada39b795fec@huawei.com \
--to=shameerali.kolothum.thodi@huawei.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ryan.roberts@arm.com \
--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