From: kernel test robot <lkp@intel.com>
To: "José Pekkarinen" <jose.pekkarinen@foxhound.fi>,
seanjc@google.com, pbonzini@redhat.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
skhan@linuxfoundation.org
Cc: kvm@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
hpa@zytor.com, linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] KVM: x86: cleanup unused variables
Date: Mon, 30 Oct 2023 02:41:48 +0800 [thread overview]
Message-ID: <202310300228.s4py0SQf-lkp@intel.com> (raw)
In-Reply-To: <20231029093859.138442-1-jose.pekkarinen@foxhound.fi>
Hi José,
kernel test robot noticed the following build errors:
[auto build test ERROR on kvm/queue]
[also build test ERROR on linus/master v6.6-rc7 next-20231027]
[cannot apply to kvm/linux-next]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jos-Pekkarinen/KVM-x86-cleanup-unused-variables/20231029-174855
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
patch link: https://lore.kernel.org/r/20231029093859.138442-1-jose.pekkarinen%40foxhound.fi
patch subject: [PATCH] KVM: x86: cleanup unused variables
config: i386-buildonly-randconfig-006-20231030 (https://download.01.org/0day-ci/archive/20231030/202310300228.s4py0SQf-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231030/202310300228.s4py0SQf-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/202310300228.s4py0SQf-lkp@intel.com/
All errors (new ones prefixed by >>):
arch/x86/kvm/emulate.c: In function 'decode_modrm':
>> arch/x86/kvm/emulate.c:950:9: error: 'rc' undeclared (first use in this function); did you mean 'rq'?
950 | rc = do_insn_fetch_bytes(_ctxt, sizeof(_type)); \
| ^~
arch/x86/kvm/emulate.c:1225:45: note: in expansion of macro 'insn_fetch'
1225 | modrm_ea += insn_fetch(u16, ctxt);
| ^~~~~~~~~~
arch/x86/kvm/emulate.c:950:9: note: each undeclared identifier is reported only once for each function it appears in
950 | rc = do_insn_fetch_bytes(_ctxt, sizeof(_type)); \
| ^~
arch/x86/kvm/emulate.c:1225:45: note: in expansion of macro 'insn_fetch'
1225 | modrm_ea += insn_fetch(u16, ctxt);
| ^~~~~~~~~~
arch/x86/kvm/emulate.c: In function 'decode_abs':
>> arch/x86/kvm/emulate.c:950:9: error: 'rc' undeclared (first use in this function); did you mean 'rq'?
950 | rc = do_insn_fetch_bytes(_ctxt, sizeof(_type)); \
| ^~
arch/x86/kvm/emulate.c:1317:35: note: in expansion of macro 'insn_fetch'
1317 | op->addr.mem.ea = insn_fetch(u16, ctxt);
| ^~~~~~~~~~
arch/x86/kvm/emulate.c: In function 'decode_imm':
>> arch/x86/kvm/emulate.c:950:9: error: 'rc' undeclared (first use in this function); did you mean 'rq'?
950 | rc = do_insn_fetch_bytes(_ctxt, sizeof(_type)); \
| ^~
arch/x86/kvm/emulate.c:4560:27: note: in expansion of macro 'insn_fetch'
4560 | op->val = insn_fetch(s8, ctxt);
| ^~~~~~~~~~
vim +950 arch/x86/kvm/emulate.c
6226686954c4cc drivers/kvm/x86_emulate.c Avi Kivity 2007-11-20 945
67cbc90db5c0f0 arch/x86/kvm/emulate.c Takuya Yoshikawa 2011-05-15 946 /* Fetch next part of the instruction being emulated. */
e85a10852c26d7 arch/x86/kvm/emulate.c Takuya Yoshikawa 2011-07-30 947 #define insn_fetch(_type, _ctxt) \
9506d57de3bc82 arch/x86/kvm/emulate.c Paolo Bonzini 2014-05-06 948 ({ _type _x; \
9506d57de3bc82 arch/x86/kvm/emulate.c Paolo Bonzini 2014-05-06 949 \
9506d57de3bc82 arch/x86/kvm/emulate.c Paolo Bonzini 2014-05-06 @950 rc = do_insn_fetch_bytes(_ctxt, sizeof(_type)); \
67cbc90db5c0f0 arch/x86/kvm/emulate.c Takuya Yoshikawa 2011-05-15 951 if (rc != X86EMUL_CONTINUE) \
67cbc90db5c0f0 arch/x86/kvm/emulate.c Takuya Yoshikawa 2011-05-15 952 goto done; \
9506d57de3bc82 arch/x86/kvm/emulate.c Paolo Bonzini 2014-05-06 953 ctxt->_eip += sizeof(_type); \
8616abc2537933 arch/x86/kvm/emulate.c Nick Desaulniers 2017-06-27 954 memcpy(&_x, ctxt->fetch.ptr, sizeof(_type)); \
17052f16a51af6 arch/x86/kvm/emulate.c Paolo Bonzini 2014-05-06 955 ctxt->fetch.ptr += sizeof(_type); \
9506d57de3bc82 arch/x86/kvm/emulate.c Paolo Bonzini 2014-05-06 956 _x; \
67cbc90db5c0f0 arch/x86/kvm/emulate.c Takuya Yoshikawa 2011-05-15 957 })
67cbc90db5c0f0 arch/x86/kvm/emulate.c Takuya Yoshikawa 2011-05-15 958
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2023-10-29 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 9:38 [PATCH] KVM: x86: cleanup unused variables José Pekkarinen
2023-10-29 12:26 ` José Pekkarinen
2023-10-29 18:41 ` kernel test robot [this message]
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=202310300228.s4py0SQf-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jose.pekkarinen@foxhound.fi \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).