From: kernel test robot <lkp@intel.com>
To: Moti Haimovski <mhaimovski@habana.ai>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Oded Gabbay <ogabbay@kernel.org>
Subject: [ogabbay:gaudi2 59/61] drivers/misc/habanalabs/common/mmu/mmu.c:785: Error: unrecognized opcode `mfence'
Date: Tue, 28 Jun 2022 16:32:34 +0800 [thread overview]
Message-ID: <202206281642.qItsyHKa-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git gaudi2
head: a76819ab38942fcb341142a55e9dc81f3eaf08e3
commit: 950d1a3888fe751fb5b2e51a44ebf89d963fdde5 [59/61] habanalabs: add gaudi2 MMU support
config: riscv-randconfig-c023-20220627 (https://download.01.org/0day-ci/archive/20220628/202206281642.qItsyHKa-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.3.0
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
# https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git/commit/?id=950d1a3888fe751fb5b2e51a44ebf89d963fdde5
git remote add ogabbay https://git.kernel.org/pub/scm/linux/kernel/git/ogabbay/linux.git
git fetch --no-tags ogabbay gaudi2
git checkout 950d1a3888fe751fb5b2e51a44ebf89d963fdde5
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=riscv SHELL=/bin/bash drivers/misc/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/misc/habanalabs/common/mmu/mmu.c: Assembler messages:
>> drivers/misc/habanalabs/common/mmu/mmu.c:785: Error: unrecognized opcode `mfence'
vim +785 drivers/misc/habanalabs/common/mmu/mmu.c
780
781 void hl_mmu_hr_flush(struct hl_ctx *ctx)
782 {
783 /* a flush operation requires memory barrier */
784 mb();
> 785 asm volatile ("mfence" : : : "memory");
786 }
787
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-28 8:33 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=202206281642.qItsyHKa-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhaimovski@habana.ai \
--cc=ogabbay@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
all inboxes | Powered by JetHome®