From: kernel test robot <lkp@intel.com>
To: Peter Gonda <pgonda@google.com>, kvm@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Peter Gonda <pgonda@google.com>,
Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4.1] KVM, SEV: Add KVM_EXIT_SHUTDOWN metadata for SEV-ES
Date: Fri, 8 Apr 2022 13:15:14 +0800 [thread overview]
Message-ID: <202204081314.dqs8Tnxd-lkp@intel.com> (raw)
In-Reply-To: <20220407210233.782250-1-pgonda@google.com>
Hi Peter,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on kvm/master]
[also build test ERROR on v5.18-rc1 next-20220407]
[cannot apply to v4.1]
[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]
url: https://github.com/intel-lab-lkp/linux/commits/Peter-Gonda/KVM-SEV-Add-KVM_EXIT_SHUTDOWN-metadata-for-SEV-ES/20220408-050628
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git master
config: riscv-randconfig-c006-20220408 (https://download.01.org/0day-ci/archive/20220408/202204081314.dqs8Tnxd-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project c29a51b3a257908aebc01cd7c4655665db317d66)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://github.com/intel-lab-lkp/linux/commit/3b310e5891d172b59042783c128f6efcf5bf6198
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Peter-Gonda/KVM-SEV-Add-KVM_EXIT_SHUTDOWN-metadata-for-SEV-ES/20220408-050628
git checkout 3b310e5891d172b59042783c128f6efcf5bf6198
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=riscv 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/riscv/kvm/vcpu_sbi.c:97:20: error: no member named 'flags' in 'struct kvm_run::(unnamed at include/uapi/linux/kvm.h:443:3)'
run->system_event.flags = flags;
~~~~~~~~~~~~~~~~~ ^
1 error generated.
vim +97 arch/riscv/kvm/vcpu_sbi.c
dea8ee31a03927 Atish Patra 2021-09-27 83
4b11d86571c447 Anup Patel 2022-01-31 84 void kvm_riscv_vcpu_sbi_system_reset(struct kvm_vcpu *vcpu,
4b11d86571c447 Anup Patel 2022-01-31 85 struct kvm_run *run,
4b11d86571c447 Anup Patel 2022-01-31 86 u32 type, u64 flags)
4b11d86571c447 Anup Patel 2022-01-31 87 {
4b11d86571c447 Anup Patel 2022-01-31 88 unsigned long i;
4b11d86571c447 Anup Patel 2022-01-31 89 struct kvm_vcpu *tmp;
4b11d86571c447 Anup Patel 2022-01-31 90
4b11d86571c447 Anup Patel 2022-01-31 91 kvm_for_each_vcpu(i, tmp, vcpu->kvm)
4b11d86571c447 Anup Patel 2022-01-31 92 tmp->arch.power_off = true;
4b11d86571c447 Anup Patel 2022-01-31 93 kvm_make_all_cpus_request(vcpu->kvm, KVM_REQ_SLEEP);
4b11d86571c447 Anup Patel 2022-01-31 94
4b11d86571c447 Anup Patel 2022-01-31 95 memset(&run->system_event, 0, sizeof(run->system_event));
4b11d86571c447 Anup Patel 2022-01-31 96 run->system_event.type = type;
4b11d86571c447 Anup Patel 2022-01-31 @97 run->system_event.flags = flags;
4b11d86571c447 Anup Patel 2022-01-31 98 run->exit_reason = KVM_EXIT_SYSTEM_EVENT;
4b11d86571c447 Anup Patel 2022-01-31 99 }
4b11d86571c447 Anup Patel 2022-01-31 100
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-04-08 5:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 21:02 [PATCH v4.1] KVM, SEV: Add KVM_EXIT_SHUTDOWN metadata for SEV-ES Peter Gonda
2022-04-08 2:55 ` Sean Christopherson
2022-04-08 15:18 ` Peter Gonda
2022-04-08 17:01 ` Sean Christopherson
2022-04-11 9:12 ` Will Deacon
2022-04-11 14:00 ` Alexandru Elisei
2022-04-11 15:06 ` Sean Christopherson
2022-04-14 23:21 ` Sean Christopherson
2022-04-08 4:34 ` kernel test robot
2022-04-08 5:15 ` kernel test robot [this message]
2022-04-08 16:56 ` Paolo Bonzini
2022-04-11 9:45 ` Marc Zyngier
2022-04-11 14:25 ` Sean Christopherson
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=202204081314.dqs8Tnxd-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=seanjc@google.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 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.