FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=main 2025-09-11T16:08:05Z 2025-09-11T16:08:05Z Timothy Pearson tpearson@raptorengineering.com 2025-09-10T16:54:24Z urn:sha1:5daf8ed625af70ebb7e4740ab98a6054e9e52329 Separate ossl's existing AES-NI GCM implementation into a common ossl_aes_gcm.c and add conditionals to switch between OpenSSL's AES-NI and POWER8 GCM routines depending on the architecture. Since the existing AVX-512 implementation is less agnostic, move it into a separate ossl_aes_gcm_avx512.c. Reviewed by: markj MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D44274 2025-08-15T17:06:03Z John Baldwin jhb@FreeBSD.org 2025-08-15T17:04:05Z urn:sha1:9630e68f94a45b64087b18cc21be07ba3d3c3e8e Fixes: 4757b351ea9d ("openssl: Import version 3.5.1") 2024-07-15T22:43:39Z Warner Losh imp@FreeBSD.org 2024-07-15T04:46:32Z urn:sha1:e9ac41698b2f322d55ccf9da50a3596edb2c1800 This is a residual of the $FreeBSD$ removal. MFC After: 3 days (though I'll just run the command on the branches) Sponsored by: Netflix 2024-06-21T07:29:04Z Shawn Anastasio sanatasio@raptorengineering.com 2024-06-21T07:15:55Z urn:sha1:3465f14dac7dc4efaf1f8b4e10c2a00b2db7c513 Summary: Add support for building ossl(4) on powerpc64* by implementing ossl_cpuid and other support functions for powerpc. The required assembly files for ppc were already present in-tree. Test Plan: The changes were tested using the in-tree tools/tools/crypto/cryptocheck.c tool on both powerpc64 and powerpc64le on a POWER9 system. Reviewed by: #powerpc, jhibbits, jhb Differential Revision: https://reviews.freebsd.org/D41837 2023-12-04T17:29:11Z Mark Johnston markj@FreeBSD.org 2023-12-04T17:29:11Z urn:sha1:e655cc70dfcda5cfedb5a1d9bef1e87d55519f64 OpenSSL itself keeps only a single copy of this header. Do the same in sys/crypto/openssl to avoid the extra maintenance burden. This requires adjusting the include paths for generated asm files. No functional change intended. Reported by: jrtc27 Reviewed by: jhb MFC after: 3 months Differential Revision: https://reviews.freebsd.org/D42866 2023-11-30T17:49:48Z Mark Johnston markj@FreeBSD.org 2023-11-30T17:46:54Z urn:sha1:629a72376d51aad812d6f1279403bc81c38c35d2 This provides substantially higher throughput than the fallback implementation. Reviewed by: jhb MFC after: 3 months Sponsored by: Klara, Inc. Sponsored by: Stormshield Differential Revision: https://reviews.freebsd.org/D41305 2023-11-30T17:49:47Z Mark Johnston markj@FreeBSD.org 2023-11-30T17:46:08Z urn:sha1:44f8e1e8530e1d2e95e84bbbe3d22ac9cb2557fe OpenSSL provides implementations of several AES modes which use bitslicing and can be accelerated on CPUs which support the NEON extension. This patch adds arm platform support to ossl(4) and provides an AES-CBC implementation, though bsaes_cbc_encrypt() only implements decryption. The real goal is to provide an accelerated AES-GCM implementation; this will be added in a subsequent patch. Initially derived from https://reviews.freebsd.org/D37420. Reviewed by: jhb Sponsored by: Klara, Inc. Sponsored by: Stormshield MFC after: 3 months Differential Revision: https://reviews.freebsd.org/D41304 2023-08-16T17:54:58Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:58Z urn:sha1:031beb4e239bfce798af17f5fe8dba8bcaf13d99 Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ 2023-06-02T16:17:11Z Mark Johnston markj@FreeBSD.org 2023-06-02T16:01:41Z urn:sha1:9b1d87286c78266dc76d32a06ed19bf3e93c0a3b This lets one use ossl(4) for AES-GCM operations on contemporary amd64 platforms. A kernel benchmark indicates that this gives roughly equivalent throughput to aesni(4) for various buffer sizes. Bulk processing is done in aesni-gcm-x86_64.S, the rest is handled in a C wrapper ported from OpenSSL's gcm128.c. Sponsored by: Stormshield Sponsored by: Klara, Inc. Reviewed by: jhb MFC after: 3 months Differential Revision: https://reviews.freebsd.org/D39967 2023-06-02T16:15:01Z Mark Johnston markj@FreeBSD.org 2023-06-02T15:58:29Z urn:sha1:9a3444d91c706dda65040138acbdb8c932213960 aes-gcm-avx512.S is generated from OpenSSL 3.1 and implements AES-GCM. ossl_x86.c detects whether the CPU implements the required AVX512 instructions; if not, the ossl(4) module does not provide an AES-GCM implementation. The VAES implementation increases throughput for all buffer sizes in both directions, up to 2x for sufficiently large buffers. The "process" implementation is in two parts: a generic OCF layer in ossl_aes.c that calls a set of MD functions to do the heavy lifting. The intent there is to make it possible to add other implementations for other platforms, e.g., to reduce the diff required for D37421. A follow-up commit will add a fallback path to legacy AES-NI, so that ossl(4) can be used in preference to aesni(4) on all amd64 platforms. In the long term we would like to replace aesni(4) and armv8crypto(4) with ossl(4). Note, currently this implementation will not be selected by default since aesni(4) and ossl(4) return the same probe priority for crypto sessions, and the opencrypto framework selects the first registered implementation to break a tie. Since aesni(4) is compiled into the kernel, aesni(4) wins. A separate change may modify ossl(4) to have priority. Sponsored by: Stormshield Sponsored by: Klara, Inc. Reviewed by: jhb MFC after: 3 months Differential Revision: https://reviews.freebsd.org/D39783