public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [sean-jc:x86/fastpath_pi_nv 2/2] arch/x86/kvm/svm/svm.c:4147:39: error: expected ';' after expression
Date: Tue, 30 Jul 2024 16:52:06 +0800	[thread overview]
Message-ID: <202407301650.BHl33FuL-lkp@intel.com> (raw)

tree:   https://github.com/sean-jc/linux x86/fastpath_pi_nv
head:   b2746b169a9de85ccd1760906aadedd71e30497d
commit: b2746b169a9de85ccd1760906aadedd71e30497d [2/2] KVM: x86: Add a fastpath HLT handler
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240730/202407301650.BHl33FuL-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240730/202407301650.BHl33FuL-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/202407301650.BHl33FuL-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

>> arch/x86/kvm/svm/svm.c:4147:39: error: expected ';' after expression
    4147 |         to_svm(vcpu)->vmcb->control.exit_code
         |                                              ^
         |                                              ;
>> arch/x86/kvm/svm/svm.c:4151:6: error: use of undeclared identifier 'exit_code'; did you mean 'exit_creds'?
    4151 |         if (exit_code == SVM_EXIT_MSR &&
         |             ^~~~~~~~~
         |             exit_creds
   include/linux/cred.h:150:13: note: 'exit_creds' declared here
     150 | extern void exit_creds(struct task_struct *);
         |             ^
   arch/x86/kvm/svm/svm.c:4155:6: error: use of undeclared identifier 'exit_code'; did you mean 'exit_creds'?
    4155 |         if (exit_code == SVM_EXIT_HLT)
         |             ^~~~~~~~~
         |             exit_creds
   include/linux/cred.h:150:13: note: 'exit_creds' declared here
     150 | extern void exit_creds(struct task_struct *);
         |             ^
>> arch/x86/kvm/svm/svm.c:4147:30: warning: expression result unused [-Wunused-value]
    4147 |         to_svm(vcpu)->vmcb->control.exit_code
         |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~
   1 warning and 3 errors generated.


vim +4147 arch/x86/kvm/svm/svm.c

  4144	
  4145	static fastpath_t svm_exit_handlers_fastpath(struct kvm_vcpu *vcpu)
  4146	{
> 4147		to_svm(vcpu)->vmcb->control.exit_code
  4148		if (is_guest_mode(vcpu))
  4149			return EXIT_FASTPATH_NONE;
  4150	
> 4151		if (exit_code == SVM_EXIT_MSR &&
  4152		    to_svm(vcpu)->vmcb->control.exit_info_1)
  4153			return handle_fastpath_set_msr_irqoff(vcpu);
  4154	
  4155		if (exit_code == SVM_EXIT_HLT)
  4156			return handle_fastpath_hlt(vcpu);
  4157	
  4158		return EXIT_FASTPATH_NONE;
  4159	}
  4160	

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

                 reply	other threads:[~2024-07-30  8:52 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=202407301650.BHl33FuL-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox