From: kernel test robot <lkp@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: arch/powerpc/kvm/e500mc.c:95:15: error: invalid instruction
Date: Fri, 21 Jul 2023 19:34:39 +0800 [thread overview]
Message-ID: <202307211945.TSPcyOhh-lkp@intel.com> (raw)
Hi Sean,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f7e3a1bafdea735050dfde00523cf505dc7fd309
commit: e83ca8cfa286c9fc78b585b0e66df7f542bcbcf2 KVM: PPC: booke: Mark three local functions "static"
date: 4 months ago
config: powerpc-randconfig-r001-20230721 (https://download.01.org/0day-ci/archive/20230721/202307211945.TSPcyOhh-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce: (https://download.01.org/0day-ci/archive/20230721/202307211945.TSPcyOhh-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/202307211945.TSPcyOhh-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/powerpc/kvm/e500mc.c:95:15: error: invalid instruction
95 | asm volatile("tlbilxlpid");
| ^
<inline asm>:1:2: note: instantiated into assembly here
1 | tlbilxlpid
| ^~~~~~~~~~
>> arch/powerpc/kvm/e500mc.c:95:15: error: invalid instruction
95 | asm volatile("tlbilxlpid");
| ^
<inline asm>:1:2: note: instantiated into assembly here
1 | tlbilxlpid
| ^~~~~~~~~~
2 errors generated.
vim +95 arch/powerpc/kvm/e500mc.c
73196cd364a2d9 Scott Wood 2011-12-20 88
73196cd364a2d9 Scott Wood 2011-12-20 89 void kvmppc_e500_tlbil_all(struct kvmppc_vcpu_e500 *vcpu_e500)
73196cd364a2d9 Scott Wood 2011-12-20 90 {
73196cd364a2d9 Scott Wood 2011-12-20 91 unsigned long flags;
73196cd364a2d9 Scott Wood 2011-12-20 92
73196cd364a2d9 Scott Wood 2011-12-20 93 local_irq_save(flags);
188e267ce249b4 Mihai Caraman 2014-09-01 94 mtspr(SPRN_MAS5, MAS5_SGS | get_lpid(&vcpu_e500->vcpu));
73196cd364a2d9 Scott Wood 2011-12-20 @95 asm volatile("tlbilxlpid");
73196cd364a2d9 Scott Wood 2011-12-20 96 mtspr(SPRN_MAS5, 0);
73196cd364a2d9 Scott Wood 2011-12-20 97 local_irq_restore(flags);
73196cd364a2d9 Scott Wood 2011-12-20 98 }
73196cd364a2d9 Scott Wood 2011-12-20 99
:::::: The code at line 95 was first introduced by commit
:::::: 73196cd364a2d972d73fa08da9d81ca3215bed68 KVM: PPC: e500mc support
:::::: TO: Scott Wood <scottwood@freescale.com>
:::::: CC: Avi Kivity <avi@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-07-21 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 11:34 kernel test robot [this message]
2023-07-21 23:38 ` arch/powerpc/kvm/e500mc.c:95:15: error: invalid instruction Sean Christopherson
2023-07-24 17:15 ` Nick Desaulniers
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=202307211945.TSPcyOhh-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mpe@ellerman.id.au \
--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