From: kernel test robot <lkp@intel.com>
To: "brookxu.cn" <brookxu.cn@gmail.com>,
robin.murphy@arm.com, joro@8bytes.org, will@kernel.org
Cc: kbuild-all@lists.01.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/iova: using separate rcache for SAC and DAC
Date: Sat, 17 Sep 2022 11:44:42 +0800 [thread overview]
Message-ID: <202209171115.TzR7T0b4-lkp@intel.com> (raw)
In-Reply-To: <20220916154613.104965-1-brookxu.cn@gmail.com>
Hi brookxu.cn",
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v6.0-rc5]
[also build test ERROR on linus/master next-20220916]
[cannot apply to joro-iommu/next]
[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/brookxu-cn/iommu-iova-using-separate-rcache-for-SAC-and-DAC/20220916-234845
base: 80e78fcce86de0288793a0ef0f6acf37656ee4cf
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20220917/202209171115.TzR7T0b4-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/fa50a31c6b74157cac20cd44b3717c19b934ff76
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review brookxu-cn/iommu-iova-using-separate-rcache-for-SAC-and-DAC/20220916-234845
git checkout fa50a31c6b74157cac20cd44b3717c19b934ff76
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/iommu/iova.c: In function 'iova_rcache_get':
>> drivers/iommu/iova.c:902:24: error: expected ';' before '}' token
902 | return iova_pfn
| ^
| ;
903 | }
| ~
vim +902 drivers/iommu/iova.c
878
879 /*
880 * Try to satisfy IOVA allocation range from rcache. Fail if requested
881 * size is too big or the DMA limit we are given isn't satisfied by the
882 * top element in the magazine.
883 */
884 static unsigned long iova_rcache_get(struct iova_domain *iovad,
885 unsigned long size,
886 unsigned long limit_pfn)
887 {
888 unsigned int log_size = order_base_2(size);
889 unsigned long iova_pfn;
890 unsigned int index;
891
892 if (log_size >= IOVA_RANGE_CACHE_MAX_SIZE || !iovad->rcaches)
893 return 0;
894
895 iova_pfn = __iova_rcache_get(&iovad->rcaches[log_size], limit_pfn - size);
896
897 if (!iova_pfn && limit_pfn > DMA_BIT_MASK(32)) {
898 index = log_size + IOVA_RANGE_CACHE_MAX_SIZE;
899 iova_pfn = __iova_rcache_get(&iovad->rcaches[index], limit_pfn - size);
900 }
901
> 902 return iova_pfn
903 }
904
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-09-17 3:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 15:46 [PATCH] iommu/iova: using separate rcache for SAC and DAC brookxu.cn
2022-09-16 17:03 ` Robin Murphy
2022-09-19 3:02 ` brookxu.cn
2022-09-23 12:27 ` Robin Murphy
2022-09-17 3:44 ` kernel test robot [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=202209171115.TzR7T0b4-lkp@intel.com \
--to=lkp@intel.com \
--cc=brookxu.cn@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@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