From: kernel test robot <lkp@intel.com>
To: Tianyu Lan <tiala@microsoft.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Wei Liu <wei.liu@kernel.org>,
Michael Kelley <mikelley@microsoft.com>
Subject: [hyperv:hyperv-next 8/8] arch/x86/kernel/cpu/mshyperv.c:583:26: error: no member named 'r8' in 'struct pt_regs'
Date: Sat, 5 Aug 2023 16:56:32 +0800 [thread overview]
Message-ID: <202308051623.AsakMFiD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git hyperv-next
head: 3a5274c555c28bd6906103b0d9bbfd6e9e9df1ff
commit: 3a5274c555c28bd6906103b0d9bbfd6e9e9df1ff [8/8] x86/hyperv: Add hyperv-specific handling for VMMCALL under SEV-ES
config: i386-randconfig-r015-20230731 (https://download.01.org/0day-ci/archive/20230805/202308051623.AsakMFiD-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230805/202308051623.AsakMFiD-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/202308051623.AsakMFiD-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/kernel/cpu/mshyperv.c:583:26: error: no member named 'r8' in 'struct pt_regs'
ghcb_set_r8(ghcb, regs->r8);
~~~~ ^
1 error generated.
vim +583 arch/x86/kernel/cpu/mshyperv.c
577
578 static void hv_sev_es_hcall_prepare(struct ghcb *ghcb, struct pt_regs *regs)
579 {
580 /* RAX and CPL are already in the GHCB */
581 ghcb_set_rcx(ghcb, regs->cx);
582 ghcb_set_rdx(ghcb, regs->dx);
> 583 ghcb_set_r8(ghcb, regs->r8);
584 }
585
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-08-05 8:57 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=202308051623.AsakMFiD-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=mikelley@microsoft.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tiala@microsoft.com \
--cc=wei.liu@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