From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mx.groups.io with SMTP id smtpd.web10.4799.1604704002089453767 for ; Fri, 06 Nov 2020 15:06:42 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@intel.onmicrosoft.com header.s=selector2-intel-onmicrosoft-com header.b=BUGbKwWg; spf=pass (domain: intel.com, ip: 134.134.136.126, mailfrom: jiewen.yao@intel.com) IronPort-SDR: LYkVrnRDzIFPFdYIqBfaP8BvoW2YVSNRPO8vqTAil/9rCOJgOVWA56czKaRTSMT4OC8yUsY/wL NEhM4UrjnJsw== X-IronPort-AV: E=McAfee;i="6000,8403,9797"; a="157391556" X-IronPort-AV: E=Sophos;i="5.77,457,1596524400"; d="scan'208";a="157391556" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Nov 2020 15:06:40 -0800 IronPort-SDR: aF6xhqwPv8afXwhv7tK6dajwPubJciPVQ1cTWDxo0g4I+sz25q8fkOeBcjwTp6BVc8/Yy87PJk pKffDyp08lRA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,457,1596524400"; d="scan'208";a="364333555" Received: from orsmsx602.amr.corp.intel.com ([10.22.229.15]) by FMSMGA003.fm.intel.com with ESMTP; 06 Nov 2020 15:06:40 -0800 Received: from orsmsx612.amr.corp.intel.com (10.22.229.25) by ORSMSX602.amr.corp.intel.com (10.22.229.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 6 Nov 2020 15:06:39 -0800 Received: from orsmsx603.amr.corp.intel.com (10.22.229.16) by ORSMSX612.amr.corp.intel.com (10.22.229.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 6 Nov 2020 15:06:39 -0800 Received: from ORSEDG602.ED.cps.intel.com (10.7.248.7) by orsmsx603.amr.corp.intel.com (10.22.229.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5 via Frontend Transport; Fri, 6 Nov 2020 15:06:39 -0800 Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.103) by edgegateway.intel.com (134.134.137.103) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1713.5; Fri, 6 Nov 2020 15:06:38 -0800 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CI15FxT72H1vvxr1rqD9w3yJ/B51nd60uq2yCSdFAaFlbvhmIm3yHq2nEqNB12Zc9HDQnEjfkrUt8XnvY/e8ejAbYVcjBHgYzLRSm6Q3dcM5JZ1+c2+lmhKIapejlJroUyPj6KAHICfiWZpxUhBTpNURVo6Lvx/Mponz/gqzWowUm+KTrQ7dwRRRzEg5+Q0BmsxR5HizS76P6U5EPRCdIP1aP0dsEIDdT3kIdn0mxEkcZO3CJ73MEF3+v/QQybu0g9c7RryP82IMIzQaBd2A/6NOh+F/kvl3GUqqh/q8TzvjQOFK0K/mIpvSdO/uVC7A/wA00ET4zkgXhQkv3CwuIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6AgK7wR3Uk6ad5OKyHQtHfLk3w2LX/u6qQlwn0JLa/E=; b=bKl1pjWnR8eVDN6xWeb1pwQJLB9yA39c+m+b+8YyjDJ0A8KY2X9o/WnZzAeb5xT/4xrdCC7fgtd1Ar488maFKu+iC+iKB5+i398MoqD2lQrY8Ls/kr8TGuEIGAJwaOAIMBjV+xC9JUUeLDXJD3WcjYXIhHpxccB/GBYMMz13ISv+fMxcW2QcXVvn0tO3FW+qxBSf1lyuyWU6AV6VwbG3wcjUx6MgIlLqgIX9HfEUcMmto9paCQ6o3l1DFKeNzV5ZtC8q1yPsIEm8Q9CikbAYFTUYW2GgiYqqo1ZjhSrnfKs04PJ6uVoRxjQIajQ8sujU2Ow6ROj6ntGZuQ7hQ3WsTg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel.onmicrosoft.com; s=selector2-intel-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6AgK7wR3Uk6ad5OKyHQtHfLk3w2LX/u6qQlwn0JLa/E=; b=BUGbKwWgqEFlOR9qNzEOik4+Kf/XDms/9TIoKTfajcC8Os1B9fQevPZ0FGS7LA67+AtmbnpaGJt1rxgEvCuxizuLO1RiAQE+7IMzCosnMZdkFPEvA5Cs1u81d6htKF/AF0PkLOb6hvFgXRAteGIdNrJHuAWjUiTC42O5cZMIKaw= Received: from BN6PR11MB1284.namprd11.prod.outlook.com (2603:10b6:404:49::9) by BN6PR11MB1281.namprd11.prod.outlook.com (2603:10b6:404:47::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.27; Fri, 6 Nov 2020 23:06:37 +0000 Received: from BN6PR11MB1284.namprd11.prod.outlook.com ([fe80::b859:f1c:1717:16a]) by BN6PR11MB1284.namprd11.prod.outlook.com ([fe80::b859:f1c:1717:16a%12]) with mapi id 15.20.3541.021; Fri, 6 Nov 2020 23:06:37 +0000 From: "Yao, Jiewen" To: "Zurcher, Christopher J" , "devel@edk2.groups.io" , Laszlo Ersek , gaoliming CC: "Wang, Jian J" , "Lu, XiaoyuX" , "Kinney, Michael D" , "Ard Biesheuvel" Subject: Re: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: Add native instruction support for X64 Thread-Topic: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: Add native instruction support for X64 Thread-Index: AQHWsiyB4+1/v20uXEu0lqu2S9yUHqm6nppAgAAEk9CAADbo4IAADdPggACSlmCAAEPtsA== Date: Fri, 6 Nov 2020 23:06:37 +0000 Message-ID: References: <20201103215834.7533-1-christopher.j.zurcher@intel.com> <1644D590FF4B7423.25549@groups.io> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-version: 11.5.1.3 dlp-product: dlpe-windows dlp-reaction: no-action authentication-results: intel.com; dkim=none (message not signed) header.d=none;intel.com; dmarc=none action=none header.from=intel.com; x-originating-ip: [101.80.124.211] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 22369650-42b6-48ec-cd6d-08d882a89d36 x-ms-traffictypediagnostic: BN6PR11MB1281: x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:9508; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: H7nCmRHG7R8RJCmg+3zX/bFC/58ftXPFEWDeP+kJxs7P8TDFnl9xTetNzX16BInE0AOWNeLy6S2Zx3LlO64lslRIe9+rw+pn50PScqSJKxrqZKpACOsHrmUpQClY3fAx+DFGbzIwfKtIq3IG9uYCswhjlEKr8/8Aydi4rYzLn7aMQaq3RcxYCCdd2MnoNmOIq+7HjRnzbPQtxR4VCdQVnKnYDzVYmgzU4in8/aQZvXjUxCwpcCQwXDaHQDmmreq9P+Zee6v9GW1OL90yftyvTZasxSiFN1BN/L3w3mm0z61jzsqvC+zV9lCH1G19KhT972V2HrvEp5if0VF77lQUNoDymJZ+PiZ6+vQ2VHdcqoYkR/Nadln7WqwGWsWSrvo6dTiDRWFDam2256EBwWUb2w== x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:BN6PR11MB1284.namprd11.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(346002)(136003)(39860400002)(366004)(396003)(376002)(7696005)(9686003)(76116006)(316002)(66946007)(110136005)(66556008)(26005)(186003)(8936002)(8676002)(52536014)(33656002)(2906002)(966005)(55016002)(54906003)(53546011)(64756008)(86362001)(83380400001)(71200400001)(66446008)(4326008)(19627235002)(5660300002)(30864003)(6506007)(66476007)(478600001);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata: qyYhbu/skaMUFX8HCD/1tpIIf42UpBvPJgeN6wrZ/I+C+daUGaN10E7Mfnx3VB36C9L4jxakQ2Ve//FY8qaFD9X212GPeu4rE+V7SIYgFjnepd5/ZTZk3ieVNFUEvdIZjZIUc7tW2cApq4tF00ffbeRTp35rN1aPesMEHRqGmFnAcL72mlgJ9NsdUwuOOC859PdjZ8FpPrZd86yYSgyPv1EivK/NHFpyUs1HIHD529eCdnoXiSdaZ5/optNJuZBNsNBbxUztX2ttRXGiiOb2vY3GT3/1qInnmkhOszWPbCSdPWRVWmcPy1clmDRTnduGWLepaIadVeu/qvK4BjlrFutrlPpBenCymlFQ58Z2dSMHw0F69DIyafx5toRHC93YMlDMlqQaZnGktUykBYz42ro4RzSL+atJ1V5JV94Zk4lbrZznmsS/uTxQUL6yUDnilpL6GeBOzoS2wuiUBsQFotOGU+PabC4LmZE8Uj+k0O/rNUh0jljuOOuL2e3ZLr/ra0+czNccZeF6OxEL+zScXQpPdILPqUz1sTeO6goD4fK8PXcKq6BibsxVEueCs7/e/pdUZcOqXKRWiz/ui6vyFsE4etMx5uMg2Fy6g/VXYIgNqBlFydJLVIwbMahSUVtL0Stlwa/gy4I1h+IfdeKdEg== MIME-Version: 1.0 X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: BN6PR11MB1284.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 22369650-42b6-48ec-cd6d-08d882a89d36 X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Nov 2020 23:06:37.4737 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 46c98d88-e344-4ed4-8496-4ed7712e255d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: cN/8xY0qBvt1LlnrOvNJuN8UlHAbJBBi4nGxc1SmBxdpoznXLgG1g60UvBfvBrxY9+K2KYk/t97p/miZ+2iUXQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB1281 Return-Path: jiewen.yao@intel.com X-OriginatorOrg: intel.com Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable So, if someone wants to use this accelerator in Linux with GCC, what he/she= need to do? > -----Original Message----- > From: Zurcher, Christopher J > Sent: Saturday, November 7, 2020 3:36 AM > To: Yao, Jiewen ; devel@edk2.groups.io; Laszlo > Ersek ; gaoliming > Cc: Wang, Jian J ; Lu, XiaoyuX > ; Kinney, Michael D ; > Ard Biesheuvel > Subject: RE: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: Add nativ= e > instruction support for X64 >=20 > Yes, in response to your request, it was discussed on the mailing list t= hat the > OpenSSL assembly code is not compatible with GCC in this format. It is f= ully > functional with VS toolchain and CLANGPDB toolchain. The GCC toolchain > appears to be unable to handle some aspects of NASM code, particularly t= he > COMMON section and the "wrt ..imagebase" style of position-independent > code. > See 7.6.1 here: https://www.nasm.us/xdoc/2.13.02rc3/html/nasmdoc7.html >=20 > Mike/Laszlo/Liming, > Can you help me resolve the CI failures? >=20 > Thanks, > Christopher Zurcher >=20 > > -----Original Message----- > > From: Yao, Jiewen > > Sent: Friday, November 6, 2020 02:23 > > To: Zurcher, Christopher J ; > > devel@edk2.groups.io > > Cc: Wang, Jian J ; Lu, XiaoyuX > ; > > Kinney, Michael D ; Ard Biesheuvel > > > > Subject: RE: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: Add nat= ive > > instruction support for X64 > > > > Hi Zurcher > > I am not CI person, so I recommend you have a discussion with Mike, > Laszlo, > > or Liming to see what is the best way to resolve the coding style issu= e. Or > > how to change CI rule to add exception somewhere. > > > > However, I do have concern, when you say: "the module is not compatibl= e > with > > GCC builds." > > > > In previous review, I already gave the comment to pass build with GCC = and > > CLANG besides MSVC. Do you mean this patch cannot pass GCC build? > > > > Thank you > > Yao Jiewen > > > > > -----Original Message----- > > > From: Zurcher, Christopher J > > > Sent: Friday, November 6, 2020 5:50 PM > > > To: Yao, Jiewen ; devel@edk2.groups.io > > > Cc: Wang, Jian J ; Lu, XiaoyuX > > > ; Kinney, Michael D > ; > > > Ard Biesheuvel > > > Subject: RE: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: Add > native > > > instruction support for X64 > > > > > > I think some of these errors are not relevant based on the nature of= the > > > commit: > > > > > > One of the errors reported is that the added typedefs (ptrdiff_t, wc= har_t) > > do > > > not follow coding guidelines, but the typedefs are required for Open= SSL > > > compatibility and they match the already-existing style: > > > > > > typedef UINTN size_t; > > > typedef UINTN u_int; > > > +typedef INTN ptrdiff_t; > > > typedef INTN ssize_t; > > > typedef INT32 time_t; > > > typedef UINT8 __uint8_t; > > > typedef UINT8 sa_family_t; > > > typedef UINT8 u_char; > > > typedef UINT32 uid_t; > > > typedef UINT32 gid_t; > > > +typedef CHAR16 wchar_t; > > > > > > Another error is that the auto-generated assembly files do not start= with > > > capital letters, but these filenames come from OpenSSL with lowercas= e > > > filenames, and we already have opensslconf.h in the Include folder w= hich > > > has a lowercase filename. > > > > > > Another error type reported is that the auto-generated assembly file= s do > > not > > > have "SPDX-License-Identifier: BSD-2-Clause-Patent" but it was alrea= dy > > > discussed on the list that these would be checked in with the OpenSS= L > > header > > > similar to opensslconf.h: > > > > https://github.com/tianocore/edk2/blob/master/CryptoPkg/Library/Include/ > > > openssl/opensslconf.h > > > > > > Additionally, there is an error that OpensslLibX64.inf is not in > > CryptoPkg.dsc, > > > but I am not sure if it is appropriate to include as the module is n= ot > > > compatible with GCC builds. > > > > > > How should I proceed here? > > > > > > Thanks, > > > Christopher Zurcher > > > > > > > -----Original Message----- > > > > From: Yao, Jiewen > > > > Sent: Thursday, November 5, 2020 22:14 > > > > To: devel@edk2.groups.io; Yao, Jiewen ; > Zurcher, > > > > Christopher J > > > > Cc: Wang, Jian J ; Lu, XiaoyuX > > > ; > > > > Kinney, Michael D ; Ard Biesheuvel > > > > > > > > Subject: RE: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: Add > native > > > > instruction support for X64 > > > > > > > > Hi Zurcher > > > > I created https://github.com/tianocore/edk2/pull/1092 > > > > > > > > However, there are failures in CI test. So this patch is NOT merge= d. > > > > > > > > Please take a look and resolve it. > > > > > > > > Thank you > > > > Yao Jiewen > > > > > > > > > -----Original Message----- > > > > > From: devel@edk2.groups.io On Behalf Of > Yao, > > > > > Jiewen > > > > > Sent: Friday, November 6, 2020 1:56 PM > > > > > To: Zurcher, Christopher J ; > > > > > devel@edk2.groups.io > > > > > Cc: Wang, Jian J ; Lu, XiaoyuX > > > > > ; Kinney, Michael D > > > ; > > > > > Ard Biesheuvel > > > > > Subject: Re: [edk2-devel] [PATCH v5 0/2] CryptoPkg/OpensslLib: A= dd > > > native > > > > > instruction support for X64 > > > > > > > > > > Patch 1/2 reviewed-by: Jiewen Yao > > > > > > > > > > > -----Original Message----- > > > > > > From: Christopher J Zurcher > > > > > > Sent: Wednesday, November 4, 2020 5:59 AM > > > > > > To: devel@edk2.groups.io > > > > > > Cc: Yao, Jiewen ; Wang, Jian J > > > > > > ; Lu, XiaoyuX ; > Kinney, > > > > > > Michael D ; Ard Biesheuvel > > > > > > > > > > > > Subject: [PATCH v5 0/2] CryptoPkg/OpensslLib: Add native > instruction > > > > > > support for X64 > > > > > > > > > > > > V5 Changes: > > > > > > Move ApiHooks.c into X64 folder > > > > > > Update process_files.pl to clean architecture-specific subfo= lders > > > > without > > > > > > removing them > > > > > > Rebased INF file to merge latest changes regarding RngLib vs= . > > TimerLib > > > > > > > > > > > > V4 Changes: > > > > > > Add copyright header to uefi-asm.conf > > > > > > Move [Sources.X64] block to cover entire X64-specific config > > > > > > > > > > > > V3 Changes: > > > > > > Added definitions for ptrdiff_t and wchar_t to CrtLibSupport= .h for > > > > > > LLVM/Clang build support. > > > > > > Added -UWIN32 to GCC Flags for LLVM/Clang build support. > > > > > > Added missing AES GCM assembly file. > > > > > > > > > > > > V2 Changes: > > > > > > Limit scope of assembly config to SHA and AES functions. > > > > > > Removed IA32 native support (reduced config was causing buil= d > > failure > > > > > and > > > > > > can be added in a later patch). > > > > > > Removed XMM instructions from assembly generation. > > > > > > Added automatic copyright header porting for generated assem= bly > > > files. > > > > > > > > > > > > This patch adds support for building the native instruction > > algorithms > > > > for > > > > > > the X64 architecture in OpensslLib. The process_files.pl scrip= t was > > > > modified > > > > > > to parse the .asm file targets from the OpenSSL build config d= ata > > struct, > > > > and > > > > > > generate the necessary assembly files for the EDK2 build > environment. > > > > > > > > > > > > For the X64 variant, OpenSSL includes calls to a Windows error > > handling > > > > API, > > > > > > and that function has been stubbed out in ApiHooks.c. > > > > > > > > > > > > For all variants, a constructor is added to call the required = CPUID > > > > function > > > > > > within OpenSSL to facilitate processor capability checks in th= e > > native > > > > > > algorithms. > > > > > > > > > > > > Additional native architecture variants should be simple to ad= d by > > > > following > > > > > > the changes made for this architecture. > > > > > > > > > > > > The OpenSSL assembly files are traditionally generated at buil= d time > > > > using a > > > > > > perl script. To avoid that burden on EDK2 users, these end-res= ult > > > > assembly > > > > > > files are generated during the configuration steps performed b= y the > > > > > package > > > > > > maintainer (through process_files.pl). The perl generator scri= pts > > inside > > > > > > OpenSSL do not parse file comments as they are only meant to > create > > > > > > intermediate build files, so process_files.pl contains additio= nal > > hooks > > > > to > > > > > > preserve the copyright headers as well as clean up tabs and li= ne > > endings > > > > to > > > > > > comply with EDK2 coding standards. The resulting file headers = align > > > with > > > > > > the generated .h files which are already included in the EDK2 > > repository. > > > > > > > > > > > > Cc: Jiewen Yao > > > > > > Cc: Jian J Wang > > > > > > Cc: Xiaoyu Lu > > > > > > Cc: Mike Kinney > > > > > > Cc: Ard Biesheuvel > > > > > > > > > > > > Christopher J Zurcher (2): > > > > > > CryptoPkg/OpensslLib: Add native instruction support for X64 > > > > > > CryptoPkg/OpensslLib: Commit the auto-generated assembly fil= es > for > > > X64 > > > > > > > > > > > > CryptoPkg/Library/OpensslLib/OpensslLib.inf > > | > > > > 2 +- > > > > > > CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf > > | > > > > 2 +- > > > > > > CryptoPkg/Library/OpensslLib/OpensslLibX64.inf > > | > > > > 653 +++ > > > > > > CryptoPkg/Library/Include/CrtLibSupport.h > > | > > > > 2 + > > > > > > CryptoPkg/Library/Include/openssl/opensslconf.h > > | > > > > 3 - > > > > > > CryptoPkg/Library/OpensslLib/OpensslLibConstructor.c > > | > > > > 34 + > > > > > > CryptoPkg/Library/OpensslLib/X64/ApiHooks.c > > | > > > > 18 + > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni-mb- > x86_64.nasm > > > | > > > > > > 732 +++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni-sha1- > > > x86_64.nasm | > > > > > > 1916 ++++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni-sha256- > > > x86_64.nasm > > > > > | > > > > > > 78 + > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni-x86_64.nasm > > > | > > > > > > 5103 ++++++++++++++++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/vpaes-x86_64.nasm > > > | > > > > > > 1173 +++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/modes/aesni-gcm- > > > x86_64.nasm > > > > > > | 34 + > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/modes/ghash- > x86_64.nasm > > > | > > > > > > 1569 ++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha1-mb- > x86_64.nasm > > > | > > > > > > 3137 ++++++++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha1-x86_64.nasm > > > | > > > > > > 2884 +++++++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha256-mb- > > > x86_64.nasm > > > > > | > > > > > > 3461 +++++++++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha256- > x86_64.nasm > > > | > > > > > > 3313 +++++++++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha512- > x86_64.nasm > > > | > > > > > > 1938 ++++++++ > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/x86_64cpuid.nasm > > | > > > > 491 > > > > > > ++ > > > > > > CryptoPkg/Library/OpensslLib/process_files.pl > > | > > > > 232 +- > > > > > > CryptoPkg/Library/OpensslLib/uefi-asm.conf > > | > > > > 21 + > > > > > > 22 files changed, 26746 insertions(+), 50 deletions(-) > > > > > > create mode 100644 > CryptoPkg/Library/OpensslLib/OpensslLibX64.inf > > > > > > create mode 100644 > > > > > CryptoPkg/Library/OpensslLib/OpensslLibConstructor.c > > > > > > create mode 100644 CryptoPkg/Library/OpensslLib/X64/ApiHooks.= c > > > > > > create mode 100644 > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni- > > > > > > mb-x86_64.nasm > > > > > > create mode 100644 > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni- > > > > > > sha1-x86_64.nasm > > > > > > create mode 100644 > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni- > > > > > > sha256-x86_64.nasm > > > > > > create mode 100644 > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/aesni- > > > > > > x86_64.nasm > > > > > > create mode 100644 > > > CryptoPkg/Library/OpensslLib/X64/crypto/aes/vpaes- > > > > > > x86_64.nasm > > > > > > create mode 100644 > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/modes/aesni-gcm- > > > x86_64.nasm > > > > > > create mode 100644 > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/modes/ghash- > x86_64.nasm > > > > > > create mode 100644 > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha1- > > > > > > mb-x86_64.nasm > > > > > > create mode 100644 > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha1- > > > > > > x86_64.nasm > > > > > > create mode 100644 > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha256- > > > > > > mb-x86_64.nasm > > > > > > create mode 100644 > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha256- > > > > > > x86_64.nasm > > > > > > create mode 100644 > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/sha/sha512- > > > > > > x86_64.nasm > > > > > > create mode 100644 > > > > > > CryptoPkg/Library/OpensslLib/X64/crypto/x86_64cpuid.nasm > > > > > > create mode 100644 CryptoPkg/Library/OpensslLib/uefi-asm.conf > > > > > > > > > > > > -- > > > > > > 2.28.0.windows.1 > > > > > > > > > > > > > > > > > > > >=20 > > > > >