Closed Bug 1657255 Opened 6 years ago Closed 5 years ago

Run CI for disable SHA1/SHA2 ARM crypto extensions.

Categories

(NSS :: Test, enhancement)

ARM64
Linux
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: m_kato, Assigned: m_kato)

Details

Attachments

(1 file)

CI's hardware seems to be AWS a1 instance, so it supports ARM Crypto extensions.

I have added SHA1/SHA2 optimization using ARM Crypto extensions, but according to NSS's CI, we don't run CI with NSS_DISABLE_HW_SHA1 and NSS_DISABLE_HW_SHA2 . We should add it for non-ARM Crypto extension hardware (such as Raspberry Pi3/4)

Also, actually, we still run NoSSE4.1 on aarch64 CI, but this is unnecessary for aarch64.

Also we should add NoAES on aarch64 like x86 too.

Actually, we have the implementation of ARM Crypto extension, so CI is always
run with this extension. It means that we don't run CI without ARM Crypto
extension. So I would like to add NoAES and NoSHA for aarch64 CI.

Also, we still run NoSSE4_1 on aarch64 CI, so we shouldn't run this on aarch64
hardware.

Assignee: nobody → m_kato
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 3.58
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: