From: Dave Hansen <dave.hansen@intel.com>
To: kernel test robot <lkp@intel.com>,
LeoLiu-oc <LeoLiu-oc@zhaoxin.com>,
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
Subject: Re: [PATCH v2] crypto: x86/sm2 -add Zhaoxin SM2 algorithm implementation
Date: Wed, 15 Nov 2023 11:21:41 -0800 [thread overview]
Message-ID: <541fff8a-ad8f-43f5-9a44-c64302698029@intel.com> (raw)
In-Reply-To: <202311160022.csCILGmA-lkp@intel.com>
> vim +/asm +43 arch/x86/crypto/sm2-zhaoxin-gmi_glue.c
>
> 35
> 36 /* Zhaoxin sm2 verify function */
> 37 static inline int zhaoxin_gmi_sm2_verify(unsigned char *key, unsigned char *hash, unsigned char *sig,
> 38 unsigned char *scratch)
> 39 {
> 40 uint64_t cword, f_ok;
> 41 cword = (uint64_t)0x8;
> 42
> > 43 asm(".byte 0xf2, 0x0f, 0xa6, 0xc0"
> 44 :"=c"(f_ok), "+a"(hash), "+b"(key), "+d"(cword), "+S"(scratch), "+D"(sig));
> 45
> 46 return f_ok;
> 47 }
> 48
When you go fix your compile error, can you please look around the tree
and see what folks do for replacing .byte? AS_SHA1_NI, for example.
next prev parent reply other threads:[~2023-11-15 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 9:47 [PATCH] crypto: x86/sm2 -add Zhaoxin SM2 algorithm implementation LeoLiu-oc
2023-11-09 15:00 ` Dave Hansen
2023-11-15 2:05 ` LeoLiu-oc
2023-11-10 14:27 ` kernel test robot
2023-11-15 7:17 ` [PATCH v2] " LeoLiu-oc
2023-11-15 16:58 ` kernel test robot
2023-11-15 19:21 ` Dave Hansen [this message]
2023-11-21 8:04 ` LeoLiu-oc
2023-11-22 6:43 ` [PATCH v3] " LeoLiu-oc
2023-11-22 14:26 ` Dave Hansen
2023-11-29 7:24 ` LeoLiu-oc
2023-11-29 8:04 ` LeoLiu-oc
2023-12-01 9:27 ` Herbert Xu
2023-12-05 7:26 ` LeoLiu-oc
2023-12-21 6:21 ` [PATCH v4] " LeoLiu-oc
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=541fff8a-ad8f-43f5-9a44-c64302698029@intel.com \
--to=dave.hansen@intel.com \
--cc=CobeChen@zhaoxin.com \
--cc=LeoLiu-oc@zhaoxin.com \
--cc=Leoliu@zhaoxin.com \
--cc=TonyWWang@zhaoxin.com \
--cc=YunShen@zhaoxin.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=jiaxi.chen@linux.intel.com \
--cc=jmattson@google.com \
--cc=kim.phillips@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--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