From: kernel test robot <lkp@intel.com>
To: Kai Huang <kai.huang@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Zhu Lingshan <lingshan.zhu@intel.com>,
Isaku Yamahata <isaku.yamahata@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Yuan Yao <yuan.yao@intel.com>
Subject: [ls-zhu:test 49/294] arch/x86/virt/vmx/tdx/tdx.c:663:27: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sun, 31 Dec 2023 19:08:10 +0800 [thread overview]
Message-ID: <202312311924.tGjsBIQD-lkp@intel.com> (raw)
tree: https://github.com/ls-zhu/linux test
head: 62a15ffb17f55ec915aedff138ef7dd490f44532
commit: d111994fe80fd5a91e4677d6e7e624b10de7b66e [49/294] x86/virt/tdx: Configure global KeyID on all packages
config: x86_64-randconfig-123-20231229 (https://download.01.org/0day-ci/archive/20231231/202312311924.tGjsBIQD-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231231/202312311924.tGjsBIQD-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/202312311924.tGjsBIQD-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/virt/vmx/tdx/tdx.c:663:27: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] __iomem *dst @@ got void * @@
arch/x86/virt/vmx/tdx/tdx.c:663:27: sparse: expected void [noderef] __iomem *dst
arch/x86/virt/vmx/tdx/tdx.c:663:27: sparse: got void *
arch/x86/virt/vmx/tdx/tdx.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/xarray.h, ...):
include/linux/page-flags.h:242:46: sparse: sparse: self-comparison always evaluates to false
arch/x86/virt/vmx/tdx/tdx.c: note: in included file (through include/linux/rculist.h, include/linux/pid.h, include/linux/sched.h, ...):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
vim +663 arch/x86/virt/vmx/tdx/tdx.c
650
651 /*
652 * Convert TDX private pages back to normal by using MOVDIR64B to
653 * clear these pages. Note this function doesn't flush cache of
654 * these TDX private pages. The caller should make sure of that.
655 */
656 static void reset_tdx_pages(unsigned long base, unsigned long size)
657 {
658 const void *zero_page = (const void *)page_address(ZERO_PAGE(0));
659 unsigned long phys, end;
660
661 end = base + size;
662 for (phys = base; phys < end; phys += 64)
> 663 movdir64b(__va(phys), zero_page);
664
665 /*
666 * MOVDIR64B uses WC protocol. Use memory barrier to
667 * make sure any later user of these pages sees the
668 * updated data.
669 */
670 mb();
671 }
672
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-12-31 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 11:08 kernel test robot [this message]
2024-01-04 5:20 [ls-zhu:test 49/294] arch/x86/virt/vmx/tdx/tdx.c:663:27: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
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=202312311924.tGjsBIQD-lkp@intel.com \
--to=lkp@intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=lingshan.zhu@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yuan.yao@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;
as well as URLs for NNTP newsgroup(s).