Bug 1994599 - atomic-queue is ExclusiveArch with no support for ppc64le
Summary: atomic-queue is ExclusiveArch with no support for ppc64le
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: atomic-queue
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Ben Beasley
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: PPCTracker
TreeView+ depends on / blocked
 
Reported: 2021-08-17 13:54 UTC by Ben Beasley
Modified: 2021-10-31 01:31 UTC (History)
2 users (show)

Fixed In Version: atomic-queue-0-0.5.20211020gitee3d91c.fc36 atomic-queue-0-0.6.20211022git7013a8b.fc33 atomic-queue-0-0.6.20211022git7013a8b.fc35 atomic-queue-0-0.6.20211022git7013a8b.fc34 atomic-queue-0-0.1.20211022git7013a8b.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-20 18:06:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ben Beasley 2021-08-17 13:54:56 UTC
Upstream uses architecture-specific assembly for the implementation of “spin_lock_pause()” in include/atomic_queue/defs.h. There are implementations for x86/x86_64 and ARM (32 and 64 bit).

An implementation for PowerPC is needed to support that architecture.

See https://bugzilla.redhat.com/show_bug.cgi?id=1988151 for a candidate and for discussion. The candidate presented there references the incompatibly-licensed Linux kernel, but the snippet itself is so trivial, and the available choices for a correct implementation so few, that it may not present copyright/license issues.

Comment 1 Fedora Update System 2021-10-20 18:04:42 UTC
FEDORA-2021-3f8d80e4d5 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3f8d80e4d5

Comment 2 Fedora Update System 2021-10-20 18:06:06 UTC
FEDORA-2021-3f8d80e4d5 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Ben Beasley 2021-10-20 18:09:01 UTC
I’m working with upstream to add support for s390x/ppc64le in https://github.com/max0x7ba/atomic_queue/issues/33. Initial support for these architectures is now in Rawhide.

The current support for these architectures assumes 64-byte cache lines, which is less than the actual value (128 bytes on ppc64le, 256 bytes on s390x). This can be expected to lead to less-than-optimal performance. Upstream is aware of the correct cache line sizes, but some other adjustments in the code will be required to support larger values. Once that settles, out, I plan to build updates for F35 and earlier stable releases, including EPEL8.

Comment 4 Dan Horák 2021-10-20 18:24:55 UTC
Great job, Ben, thanks.

Comment 5 Fedora Update System 2021-10-22 18:00:05 UTC
FEDORA-2021-ea7701eb2b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea7701eb2b

Comment 6 Fedora Update System 2021-10-22 18:20:33 UTC
FEDORA-2021-fc7123fd2f has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fc7123fd2f

Comment 7 Fedora Update System 2021-10-22 19:55:05 UTC
FEDORA-2021-500e763e43 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-500e763e43

Comment 8 Fedora Update System 2021-10-22 19:55:09 UTC
FEDORA-EPEL-2021-4436a91518 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4436a91518

Comment 9 Fedora Update System 2021-10-23 02:23:53 UTC
FEDORA-2021-ea7701eb2b has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ea7701eb2b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ea7701eb2b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2021-10-23 03:31:51 UTC
FEDORA-EPEL-2021-4436a91518 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4436a91518

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2021-10-23 03:45:26 UTC
FEDORA-2021-500e763e43 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-500e763e43`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-500e763e43

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2021-10-23 04:05:13 UTC
FEDORA-2021-fc7123fd2f has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-fc7123fd2f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fc7123fd2f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2021-10-31 01:01:34 UTC
FEDORA-2021-500e763e43 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2021-10-31 01:08:18 UTC
FEDORA-2021-ea7701eb2b has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2021-10-31 01:14:44 UTC
FEDORA-2021-fc7123fd2f has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2021-10-31 01:31:25 UTC
FEDORA-EPEL-2021-4436a91518 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.