From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 54C47C4332F for ; Fri, 10 Nov 2023 18:17:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345376AbjKJSRn (ORCPT ); Fri, 10 Nov 2023 13:17:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36796 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235504AbjKJSPV (ORCPT ); Fri, 10 Nov 2023 13:15:21 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8CC5D38EA9; Fri, 10 Nov 2023 06:28:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1699626492; x=1731162492; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=v2cWD40pnESfklx3IChr4sF09jcu/aufcX8F+y8XgNo=; b=EuB5IoKzgmRJh+mYdcNMhgPi8H2EoaGa7w9ytCpWPkjHwa8Wp9SC9yGb cHXx9biyONatMuCQBWuae6wKgDXuORvRqkTSIZ3leLzGZVzKJMb+9enhn Ogi/q7ITZTGCqiZCPmye9oVoX0vHWOSOBHESuPk25HHkJtFK4mKwFFCF6 Z4vFO1q18+sv3LYGMZR6AqLb5hFNTKHfeRkBbjyhLAF49TbTi/0Bm5YJW QnSU6JA8Pg/jiuQFcI1bNC12knwMkfTwA+GGe1Fwgz1DNgvBhB8UFgp4i F+NGiJWKIOxS56DSFVcHQ6Qvez1jBnS5ToH4tQJtY5WFbPX7RLFBUtlX9 A==; X-IronPort-AV: E=McAfee;i="6600,9927,10890"; a="370393012" X-IronPort-AV: E=Sophos;i="6.03,291,1694761200"; d="scan'208";a="370393012" Received: from fmviesa002.fm.intel.com ([10.60.135.142]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Nov 2023 06:28:12 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.03,291,1694761200"; d="scan'208";a="5065666" Received: from lkp-server01.sh.intel.com (HELO 17d9e85e5079) ([10.239.97.150]) by fmviesa002.fm.intel.com with ESMTP; 10 Nov 2023 06:28:06 -0800 Received: from kbuild by 17d9e85e5079 with local (Exim 4.96) (envelope-from ) id 1r1SUO-0009e2-0h; Fri, 10 Nov 2023 14:28:04 +0000 Date: Fri, 10 Nov 2023 22:27:58 +0800 From: kernel test robot To: LeoLiu-oc , herbert@gondor.apana.org.au, davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com, seanjc@google.com, kim.phillips@amd.com, pbonzini@redhat.com, babu.moger@amd.com, jiaxi.chen@linux.intel.com, jmattson@google.com, pawan.kumar.gupta@linux.intel.com, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Cc: oe-kbuild-all@lists.linux.dev, CobeChen@zhaoxin.com, TonyWWang@zhaoxin.com, YunShen@zhaoxin.com, Leoliu@zhaoxin.com, LeoLiuoc Subject: Re: [PATCH] crypto: x86/sm2 -add Zhaoxin SM2 algorithm implementation Message-ID: <202311102217.ZDrXGyK9-lkp@intel.com> References: <20231109094744.545887-1-LeoLiu-oc@zhaoxin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231109094744.545887-1-LeoLiu-oc@zhaoxin.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi LeoLiu-oc, kernel test robot noticed the following build errors: [auto build test ERROR on herbert-cryptodev-2.6/master] [also build test ERROR on herbert-crypto-2.6/master tip/x86/core linus/master v6.6 next-20231110] [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/LeoLiu-oc/crypto-x86-sm2-add-Zhaoxin-SM2-algorithm-implementation/20231109-231229 base: https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git master patch link: https://lore.kernel.org/r/20231109094744.545887-1-LeoLiu-oc%40zhaoxin.com patch subject: [PATCH] crypto: x86/sm2 -add Zhaoxin SM2 algorithm implementation config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20231110/202311102217.ZDrXGyK9-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/20231110/202311102217.ZDrXGyK9-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 | Closes: https://lore.kernel.org/oe-kbuild-all/202311102217.ZDrXGyK9-lkp@intel.com/ All errors (new ones prefixed by >>): arch/x86/crypto/sm2-zhaoxin-gmi_asm.S: Assembler messages: >> arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:38: Error: bad register name `%r12' >> arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:39: Error: bad register name `%rbx' >> arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:41: Error: bad register name `%rsi' >> arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:42: Error: bad register name `%rdi' >> arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:43: Error: bad register name `%rdx' arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:44: Error: bad register name `%rdx' >> arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:45: Error: bad register name `%rcx' arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:46: Error: bad register name `%r12' arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:53: Error: bad register name `%rcx' arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:55: Error: bad register name `%rbx' arch/x86/crypto/sm2-zhaoxin-gmi_asm.S:56: Error: bad register name `%r12' vim +38 arch/x86/crypto/sm2-zhaoxin-gmi_asm.S 26 27 .text 28 .align 32 29 ############################################################################### 30 # int zhaoxin_gmi_sm2_verify ( 31 # unsigned char *key, /*key*/ 32 # unsigned char *hash, /*hash*/ 33 # unsigned char *sig, /*signature*/ 34 # unsigned char *scratch /*8 kbytes scratch space*/ 35 # ); 36 ############################################################################### 37 SYM_FUNC_START(zhaoxin_gmi_sm2_verify) > 38 push %r12 > 39 push %rbx 40 > 41 mov HASH_PTR, %rax > 42 mov KEY_PTR, %rbx > 43 mov SIG_PTR, %r12 44 mov $8, %rdx > 45 mov SCRATCH_PTR, %rsi -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki