linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	0day robot <lkp@intel.com>
Subject: drivers/crypto/nintendo-aes.c:72: Error: unrecognised instruction dcbf
Date: Tue, 28 Sep 2021 19:06:10 +0800	[thread overview]
Message-ID: <202109281903.fSNwxgBV-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3010 bytes --]

tree:   https://github.com/0day-ci/linux/commits/Emmanuel-Gil-Peyrot/crypto-nintendo-aes-add-a-new-AES-driver/20210922-122123
head:   27d5ea5f78903c9d07dacbbb1eceae4fb23ed601
commit: e2320d1d64125b864ed1e2d1a33b4b07801ddd33 crypto: nintendo-aes - add a new AES driver
date:   6 days ago
config: nios2-allyesconfig (attached as .config)
compiler: nios2-linux-gcc (GCC) 11.2.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://github.com/0day-ci/linux/commit/e2320d1d64125b864ed1e2d1a33b4b07801ddd33
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Emmanuel-Gil-Peyrot/crypto-nintendo-aes-add-a-new-AES-driver/20210922-122123
        git checkout e2320d1d64125b864ed1e2d1a33b4b07801ddd33
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nios2 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 >>):

   drivers/crypto/nintendo-aes.c: Assembler messages:
>> drivers/crypto/nintendo-aes.c:72: Error: unrecognised instruction dcbf
>> drivers/crypto/nintendo-aes.c:94: Error: unrecognised instruction dcbi


vim +72 drivers/crypto/nintendo-aes.c

    61	
    62	static int
    63	do_crypt(const void *src, void *dst, u32 len, u32 flags)
    64	{
    65		u32 blocks = ((len >> 4) - 1) & AES_CTRL_BLOCK;
    66		u32 status;
    67		u32 counter = OP_TIMEOUT;
    68		u32 i;
    69	
    70		/* Flush out all of src, we can’t know whether any of it is in cache */
    71		for (i = 0; i < len; i += 32)
  > 72			__asm__("dcbf 0, %0" : : "r" (src + i));
    73		__asm__("sync" : : : "memory");
    74	
    75		/* Set the addresses for DMA */
    76		iowrite32be(virt_to_phys((void *)src), base + AES_SRC);
    77		iowrite32be(virt_to_phys(dst), base + AES_DEST);
    78	
    79		/* Start the operation */
    80		iowrite32be(flags | blocks, base + AES_CTRL);
    81	
    82		/* TODO: figure out how to use interrupts here, this will probably
    83		 * lower throughput but let the CPU do other things while the AES
    84		 * engine is doing its work. */
    85		do {
    86			status = ioread32be(base + AES_CTRL);
    87			cpu_relax();
    88		} while ((status & AES_CTRL_EXEC) && --counter);
    89	
    90		/* Do we ever get called with dst ≠ src?  If so we have to invalidate
    91		 * dst in addition to the earlier flush of src. */
    92		if (unlikely(dst != src)) {
    93			for (i = 0; i < len; i += 32)
  > 94				__asm__("dcbi 0, %0" : : "r" (dst + i));
    95			__asm__("sync" : : : "memory");
    96		}
    97	
    98		return counter ? 0 : 1;
    99	}
   100	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 60806 bytes --]

                 reply	other threads:[~2021-09-28 11:07 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=202109281903.fSNwxgBV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linkmauve@linkmauve.fr \
    --cc=linux-kernel@vger.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 NNTP newsgroup(s).