All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC] virtio-mem: support Confidential Computing (CoCo) environments
Date: Wed, 15 Apr 2026 20:37:06 +0800	[thread overview]
Message-ID: <202604152042.Ddpp3f0z-lkp@intel.com> (raw)
In-Reply-To: <20260401-coco-v1-1-b9c3072e2d9c@redhat.com>

Hi Marc-André,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on c369299895a591d96745d6492d4888259b004a9e]

url:    https://github.com/intel-lab-lkp/linux/commits/Marc-Andr-Lureau/virtio-mem-support-Confidential-Computing-CoCo-environments/20260414-201359
base:   c369299895a591d96745d6492d4888259b004a9e
patch link:    https://lore.kernel.org/r/20260401-coco-v1-1-b9c3072e2d9c%40redhat.com
patch subject: [PATCH RFC] virtio-mem: support Confidential Computing (CoCo) environments
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20260415/202604152042.Ddpp3f0z-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260415/202604152042.Ddpp3f0z-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/202604152042.Ddpp3f0z-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/virtio/virtio_mem.c:876:9: error: call to undeclared function 'set_memory_encrypted'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     876 |         return set_memory_encrypted((unsigned long)__va(addr), PFN_DOWN(size));
         |                ^
>> drivers/virtio/virtio_mem.c:881:9: error: call to undeclared function 'set_memory_decrypted'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     881 |         return set_memory_decrypted((unsigned long)__va(addr), PFN_DOWN(size));
         |                ^
   2 errors generated.


vim +/set_memory_encrypted +876 drivers/virtio/virtio_mem.c

   868	
   869	/*
   870	 * In CoCo (TDX, SEV-SNP) environments, hotplugged memory must be explicitly
   871	 * accepted before use (private/encrypted), and converted to shared/decrypted
   872	 * before returning to the hypervisor on unplug.
   873	 */
   874	static int virtio_mem_coco_set_encrypted(uint64_t addr, uint64_t size)
   875	{
 > 876		return set_memory_encrypted((unsigned long)__va(addr), PFN_DOWN(size));
   877	}
   878	
   879	static int virtio_mem_coco_set_decrypted(uint64_t addr, uint64_t size)
   880	{
 > 881		return set_memory_decrypted((unsigned long)__va(addr), PFN_DOWN(size));
   882	}
   883	

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

  parent reply	other threads:[~2026-04-15 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 11:12 [PATCH RFC] virtio-mem: support Confidential Computing (CoCo) environments Marc-André Lureau
2026-04-01 19:29 ` David Hildenbrand (Arm)
2026-04-15 12:37 ` kernel test robot [this message]
2026-04-15 16:56 ` 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=202604152042.Ddpp3f0z-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=marcandre.lureau@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.