mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ashish Kalra <Ashish.Kalra@amd.com>,
	joro@8bytes.org, suravee.suthikulpanit@amd.com,
	thomas.lendacky@amd.com, Sairaj.ArunKodilkar@amd.com,
	Vasant.Hegde@amd.com, herbert@gondor.apana.org.au
Cc: oe-kbuild-all@lists.linux.dev, seanjc@google.com,
	pbonzini@redhat.com, will@kernel.org, robin.murphy@arm.com,
	john.allen@amd.com, davem@davemloft.net, michael.roth@amd.com,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH v4 1/4] iommu/amd: Add support to remap/unmap IOMMU buffers for kdump
Date: Thu, 24 Jul 2025 20:00:01 +0800	[thread overview]
Message-ID: <202507241929.76UExdsw-lkp@intel.com> (raw)
In-Reply-To: <6a48567cd99a0ef915862b3c6590d1415d287870.1753133022.git.ashish.kalra@amd.com>

Hi Ashish,

kernel test robot noticed the following build warnings:

[auto build test WARNING on herbert-cryptodev-2.6/master]
[also build test WARNING on herbert-crypto-2.6/master linus/master v6.16-rc7 next-20250724]
[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/Ashish-Kalra/iommu-amd-Add-support-to-remap-unmap-IOMMU-buffers-for-kdump/20250722-055642
base:   https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master
patch link:    https://lore.kernel.org/r/6a48567cd99a0ef915862b3c6590d1415d287870.1753133022.git.ashish.kalra%40amd.com
patch subject: [PATCH v4 1/4] iommu/amd: Add support to remap/unmap IOMMU buffers for kdump
config: x86_64-randconfig-r133-20250724 (https://download.01.org/0day-ci/archive/20250724/202507241929.76UExdsw-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250724/202507241929.76UExdsw-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/202507241929.76UExdsw-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/iommu/amd/init.c:723:41: sparse: sparse: incorrect type in return expression (different address spaces) @@     expected void * @@     got void [noderef] __iomem * @@
   drivers/iommu/amd/init.c:723:41: sparse:     expected void *
   drivers/iommu/amd/init.c:723:41: sparse:     got void [noderef] __iomem *
>> drivers/iommu/amd/init.c:723:41: sparse: sparse: incorrect type in return expression (different address spaces) @@     expected void * @@     got void [noderef] __iomem * @@
   drivers/iommu/amd/init.c:723:41: sparse:     expected void *
   drivers/iommu/amd/init.c:723:41: sparse:     got void [noderef] __iomem *
>> drivers/iommu/amd/init.c:723:41: sparse: sparse: incorrect type in return expression (different address spaces) @@     expected void * @@     got void [noderef] __iomem * @@
   drivers/iommu/amd/init.c:723:41: sparse:     expected void *
   drivers/iommu/amd/init.c:723:41: sparse:     got void [noderef] __iomem *

vim +723 drivers/iommu/amd/init.c

   707	
   708	static inline void *iommu_memremap(unsigned long paddr, size_t size)
   709	{
   710		phys_addr_t phys;
   711	
   712		if (!paddr)
   713			return NULL;
   714	
   715		/*
   716		 * Obtain true physical address in kdump kernel when SME is enabled.
   717		 * Currently, previous kernel with SME enabled and kdump kernel
   718		 * with SME support disabled is not supported.
   719		 */
   720		phys = __sme_clr(paddr);
   721	
   722		if (cc_platform_has(CC_ATTR_HOST_MEM_ENCRYPT))
 > 723			return ioremap_encrypted(phys, size);
   724		else
   725			return memremap(phys, size, MEMREMAP_WB);
   726	}
   727	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2025-07-24 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 21:52 [PATCH v4 0/4] Add host kdump support for SNP Ashish Kalra
2025-07-21 21:52 ` [PATCH v4 1/4] iommu/amd: Add support to remap/unmap IOMMU buffers for kdump Ashish Kalra
2025-07-24 12:00   ` kernel test robot [this message]
2025-07-25 10:28   ` Sairaj Kodilkar
2025-07-21 21:53 ` [PATCH v4 2/4] iommu/amd: Reuse device table " Ashish Kalra
2025-07-25 10:29   ` Sairaj Kodilkar
2025-07-21 21:53 ` [PATCH v4 3/4] crypto: ccp: Skip SEV and SNP INIT for kdump boot Ashish Kalra
2025-07-25 10:30   ` Sairaj Kodilkar
2025-07-21 21:53 ` [PATCH v4 4/4] iommu/amd: Skip enabling command/event buffers for kdump Ashish Kalra
2025-07-25 10:30   ` Sairaj Kodilkar

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=202507241929.76UExdsw-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Ashish.Kalra@amd.com \
    --cc=Sairaj.ArunKodilkar@amd.com \
    --cc=Vasant.Hegde@amd.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=iommu@lists.linux.dev \
    --cc=john.allen@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=seanjc@google.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=thomas.lendacky@amd.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

Powered by JetHome