mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Joerg Roedel <jroedel@suse.de>,
	Brijesh Singh <brijesh.singh@amd.com>
Subject: [joro:x86-testing 22/45] arch/x86/kvm/svm/sev.c:562:37: error: 'struct vcpu_svm' has no member named 'vmsa'
Date: Fri, 19 Nov 2021 21:53:58 +0800	[thread overview]
Message-ID: <202111192153.M8XRxRK8-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3361 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git x86-testing
head:   139c88cae82e33dfd6e49ecc4b015a5c7d39c80a
commit: ac655e0ba98a2425eec250e39795acd295e30171 [22/45] KVM: SVM: Create a separate mapping for the SEV-ES save area
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git/commit/?id=ac655e0ba98a2425eec250e39795acd295e30171
        git remote add joro https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git
        git fetch --no-tags joro x86-testing
        git checkout ac655e0ba98a2425eec250e39795acd295e30171
        # save the attached .config to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/x86/kvm/svm/sev.c: In function 'sev_es_sync_vmsa':
>> arch/x86/kvm/svm/sev.c:562:37: error: 'struct vcpu_svm' has no member named 'vmsa'
     562 |  struct sev_es_save_area *save = svm->vmsa;
         |                                     ^~


vim +562 arch/x86/kvm/svm/sev.c

   559	
   560	static int sev_es_sync_vmsa(struct vcpu_svm *svm)
   561	{
 > 562		struct sev_es_save_area *save = svm->vmsa;
   563	
   564		/* Check some debug related fields before encrypting the VMSA */
   565		if (svm->vcpu.guest_debug || (svm->vmcb->save.dr7 & ~DR7_FIXED_1))
   566			return -EINVAL;
   567	
   568		/*
   569		 * SEV-ES will use a VMSA that is pointed to by the VMCB, not
   570		 * the traditional VMSA that is part of the VMCB. Copy the
   571		 * traditional VMSA as it has been built so far (in prep
   572		 * for LAUNCH_UPDATE_VMSA) to be the initial SEV-ES state.
   573		 */
   574		memcpy(save, &svm->vmcb->save, sizeof(svm->vmcb->save));
   575	
   576		/* Sync registgers */
   577		save->rax = svm->vcpu.arch.regs[VCPU_REGS_RAX];
   578		save->rbx = svm->vcpu.arch.regs[VCPU_REGS_RBX];
   579		save->rcx = svm->vcpu.arch.regs[VCPU_REGS_RCX];
   580		save->rdx = svm->vcpu.arch.regs[VCPU_REGS_RDX];
   581		save->rsp = svm->vcpu.arch.regs[VCPU_REGS_RSP];
   582		save->rbp = svm->vcpu.arch.regs[VCPU_REGS_RBP];
   583		save->rsi = svm->vcpu.arch.regs[VCPU_REGS_RSI];
   584		save->rdi = svm->vcpu.arch.regs[VCPU_REGS_RDI];
   585	#ifdef CONFIG_X86_64
   586		save->r8  = svm->vcpu.arch.regs[VCPU_REGS_R8];
   587		save->r9  = svm->vcpu.arch.regs[VCPU_REGS_R9];
   588		save->r10 = svm->vcpu.arch.regs[VCPU_REGS_R10];
   589		save->r11 = svm->vcpu.arch.regs[VCPU_REGS_R11];
   590		save->r12 = svm->vcpu.arch.regs[VCPU_REGS_R12];
   591		save->r13 = svm->vcpu.arch.regs[VCPU_REGS_R13];
   592		save->r14 = svm->vcpu.arch.regs[VCPU_REGS_R14];
   593		save->r15 = svm->vcpu.arch.regs[VCPU_REGS_R15];
   594	#endif
   595		save->rip = svm->vcpu.arch.regs[VCPU_REGS_RIP];
   596	
   597		/* Sync some non-GPR registers before encrypting */
   598		save->xcr0 = svm->vcpu.arch.xcr0;
   599		save->pkru = svm->vcpu.arch.pkru;
   600		save->xss  = svm->vcpu.arch.ia32_xss;
   601		save->dr6  = svm->vcpu.arch.dr6;
   602	
   603		return 0;
   604	}
   605	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66472 bytes --]

                 reply	other threads:[~2021-11-19 13:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202111192153.M8XRxRK8-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brijesh.singh@amd.com \
    --cc=jroedel@suse.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.lendacky@amd.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

Powered by JetHome