Identify emag 8180 CPU
ClosedPublic
Actions

Authored by tuexen on Aug 18 2019, 9:35 AM.

Details

Reviewers

manu
emaste
andrew

Commits

rS352004: MFC r351511:
rS351511: Identify eMAG CPU used in Ampere Computing systems.

Summary

Allow the emag 8180 CPU used in Ampere Computing systems to be identified. This is based on NetBSD as suggested in PR237055.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Skipped

Unit

Tests Skipped

Build Status

Buildable 26104

Event Timeline

tuexen created this revision.Aug 18 2019, 9:35 AM

Herald added a subscriber: imp. · View Herald TranscriptAug 18 2019, 9:35 AM

Harbormaster completed remote builds in B25945: Diff 60964.Aug 18 2019, 9:35 AM

I tried a similar version of this change and my eMAG reports CPU 0: APM eMAG 8180 r3p2 affinity: 0 0

I used 'ampere' in the struct name and comments though.
https://github.com/emaste/freebsd/commit/d7bcf2058a7258fb89ef87f9e43604dec203cb3c

emaste accepted this revision.Aug 21 2019, 1:22 PM

This revision is now accepted and ready to land.Aug 21 2019, 1:22 PM

Don't report APM and Ampere to be consistent with other entries. Also add comments to note that the CPU comes from Ampere even though using constants from Applied Micro.

This revision now requires review to proceed.Aug 26 2019, 1:18 PM

Harbormaster completed remote builds in B26104: Diff 61286.Aug 26 2019, 1:18 PM

In D21314#464437, @emaste wrote:

I tried a similar version of this change and my eMAG reports CPU 0: APM eMAG 8180 r3p2 affinity: 0 0

I used 'ampere' in the struct name and comments though.

I think not reporting APM and Ampere improves consistency. So I changed that. However, I left the apm in the structure names since it corresponds with the APM in the constant for the implementer constant and the implementer name. However, I added a comment to provide a hint that these CPUs are now managed by Ampere Computing.