Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable CRYPTO_is_AVX512IFMA_capable #1858

Merged
merged 2 commits into from
Sep 19, 2024

Conversation

justsmth
Copy link
Contributor

@justsmth justsmth commented Sep 17, 2024

Description of changes:

  • Fix CRYPTO_is_AVX512IFMA_capable

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.

@justsmth justsmth requested a review from a team as a code owner September 17, 2024 21:08
@codecov-commenter
Copy link

codecov-commenter commented Sep 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.46%. Comparing base (7090b90) to head (35e1a1c).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1858      +/-   ##
==========================================
- Coverage   78.46%   78.46%   -0.01%     
==========================================
  Files         585      585              
  Lines       99457    99458       +1     
  Branches    14236    14237       +1     
==========================================
- Hits        78038    78035       -3     
- Misses      20784    20787       +3     
- Partials      635      636       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@cpu
Copy link

cpu commented Sep 18, 2024

Fix CRYPTO_is_AVX512IFMA_capable

It's hard to gauge the impact of this fix (or more importantly, it's absence) as a casual reader. Will using aws-lc 1.35.0 on some platforms potentially not benefit from AVX512 support until this fix lands?

@justsmth
Copy link
Contributor Author

Fix CRYPTO_is_AVX512IFMA_capable

It's hard to gauge the impact of this fix (or more importantly, it's absence) as a casual reader. Will using aws-lc 1.35.0 on some platforms potentially not benefit from AVX512 support until this fix lands?

Correct, the new RSA AVX512 (IFMA) code in v1.35.0 doesn't actually get used due to this issue. Hopefully, we can release a v1.35.1 later today with this fix. (We plan to delay the release of aws-lc-rs until this fix can be included.)

@cpu
Copy link

cpu commented Sep 18, 2024

We plan to delay the release of aws-lc-rs until this fix can be included

Great, thanks @justsmth 🙇

@justsmth justsmth force-pushed the CRYPTO_is_AVX512IFMA_capable branch 3 times, most recently from c37fac4 to ed1d2b2 Compare September 18, 2024 20:29
dkostic
dkostic previously approved these changes Sep 18, 2024
@justsmth justsmth changed the title Fix CRYPTO_is_AVX512IFMA_capable Disable CRYPTO_is_AVX512IFMA_capable Sep 19, 2024
@justsmth
Copy link
Contributor Author

justsmth commented Sep 19, 2024

There are Intel SDE tests failing on Windows when AVX512IFMA usage is enabled. (All tests for Linux pass.) Prima facie, the failures appear to be unrelated, but we need time to understand the failures.

@justsmth justsmth merged commit 8430348 into aws:main Sep 19, 2024
109 of 110 checks passed
@justsmth justsmth deleted the CRYPTO_is_AVX512IFMA_capable branch September 19, 2024 18:41
smittals2 added a commit that referenced this pull request Sep 19, 2024
## What's Changed
* More tweaks for Ruby integration by @samuel40791765 in
#1852
* Implementation of EVP_PKEY_CTX_ctrl_str for various key types by
@justsmth in #1850
* Add MLKEM768 Hybrid Groups to libssl by @alexw91 in
#1849
* add support for PEM_write_bio_PrivateKey_traditional by
@samuel40791765 in #1845
* Update s2n-bignum subtree by @torben-hansen in
#1861
* Add asserts in testing to fix Coverity alert by @smittals2 in
#1864
* Disable CRYPTO_is_AVX512IFMA_capable by @justsmth in
#1858


**Full Changelog**:
v1.35.0...v1.35.1

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license and the ISC license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants