https://github.com/amd/aocl-utils

AOCL-Utils library to get CPU architecture, Cache information and CPU features flags etc.

https://github.com/amd/aocl-utils

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (14.6%) to scientific vocabulary
Last synced: 11 months ago · JSON representation

Repository

AOCL-Utils library to get CPU architecture, Cache information and CPU features flags etc.

Basic Info
Statistics
  • Stars: 10
  • Watchers: 8
  • Forks: 5
  • Open Issues: 0
  • Releases: 4
Created over 3 years ago · Last pushed about 1 year ago
Metadata Files
Readme License Support

Readme.md

AOCL-UTILS

AOCL-Utils is an effort to extract common functionalities across libraries. Its main features include:

  • Au_cpuid

    • Core details
    • Available flags
    • Usable ISA
  • Aucoremodule

    • Thread pinning
    • Status
    • Logger
    • RNG

NOTE: This library detects only AMD "Zen" CPUs. There are no plans to support other x86 implementations. Some utilities may fail or behave unexpectedly on older AMD architectures.

Core module is internal to AOCL-Utils. To use its features, link to libaoclutils, which combines all available utility modules.

Table of Contents

Project structure

The project is structured as follows:

  • Library: This directory contains the source code for the project.

  • SDK: The release folder.

  • Tests: This directory contains the necessary unit tests for the project.

  • Tools: The necessary tools to work with the project.

  • scripts: Utility scripts to work with the project.

BUILD AND INSTALL

Dependencies

Refer supported package matrix document (supportedpackagematrix.md file)

Getting started

The same commands apply to both Linux and Windows. Only the environment setup differs. The default compiler and generator are the platform defaults.

For a specific compiler and generator: console cmake -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_C_COMPILER=clang -G "Unix Makefiles" .. Note: Replace clang with the chosen compiler and "Unix Makefiles" with the chosen generator.

Checkout the latest code

console git clone cd aocl-utils

Configure

console cmake -B default -DCMAKE_INSTALL_PREFIX=install_dir

Build

console cmake --build default --config release -j

Install

console cmake --install default --config release This command places:

  1. Header files in <Install Path>/include
  2. Static and dynamic libraries for aucore and aucpuid

Note: 1. This command creates lib/lib64 directory for the binaries. To have custom library path, use CMAKEINSTALLLIBDIR. 2. Rightly update the include path and library path in the project to link with the installed libraries. or use LDLIBRARYPATH to point to the installed library path.(PATH environment variable in windows) 3. Refer to the API documentation and examples in the Example folder to understand how to link and use the modules.

Important: 1. Most CPUID APIs (and their headers) introduced in 4.2 are deprecated; they will be removed in a future release. See the API documentation for the newer APIs. 2. Old APIs can be enabled with AU_ENABLE_OLD_API=ON during the build, otherwise deprecated warnings will be shown. 3. The aoclutils module combines aucore and aucpuid. 4. The aoclutils module is the default module for all functionalities.

Testing

Build with AU_BUILD_TESTS=ON to enable tests: console ctest -C Release QEMU (qemu-x86_64) is required for running tests on Linux distributions. On Windows, tests are disabled because QEMU-user is unavailable there.

console sudo apt-get install qemu-user # For Ubuntu sudo dnf install qemu-user # For Fedora/RHEL/CentOS # qemu tests are disable on windows as qemu-user is not available on windows

Examples

Build with AU_BUILD_EXAMPLES=ON to enable examples: console cmake -B build -DAU_BUILD_EXAMPLES=ON -G Ninja cmake --build build --config Release

The binaries are in the default/release folder. Refer to the SDK/Examples folder Readme.md for details on out of tree compilation.

List of build options

```console

Build Flags Description Default Alternate

AUBUILDDOCS Generate Docs during build OFF ON AUBUILDEXAMPLES Build examples OFF ON AUBUILDTESTS Build tests OFF ON AUBUILDTYPE Build type Release Debug, Developer AUENABLEOLDAPI Enable OLD alci* APIs OFF ON AUBUILDSHAREDLIBS Build shared libraries ON OFF AUBUILDSTATICLIBS Build static libraries ON OFF AUBUILDWITHASAN Enable ASAN options OFF ON AUBUILDWITHTSAN Enable TSAN options OFF ON AUBUILDWITH_MEMSAN Enable MEMSAN options OFF ON ```

List of functionalities provided by each utils modules

au_core (internal)

| Functionality | Headerfiles(C) | Headerfiles(C++) | | -------------- | ------------------------- | ---------------------- | | thread pinning | Capi/au/threadpinning.h | Au/ThreadPinning.hh | | status | | Au/Status.hh | | logger | Capi/au/logger.h | Au/Logger/Logger.hh |

Current API Stack(Core)

  1. ThreadPinning

Current ThreadPinning API stack

au_cpuid

| Functionality | Headerfiles(C) | Headerfiles(C++) | |------------------------------|-----------------------|--------------------------| | cpu architecture detection | Capi/au/cpuid.h | Au/Cpuid/X86Cpu.hh | | cpuid feature flag detection | Capi/au/cpuid.h | Au/Cpuid/X86Cpu.hh | | Deprecated APIs | Bcl/alci/arch.h | Bcl/alci/cxx/cpu.hh |

Current API Stack(Cpuid)

Current Cpuid API stack

Note

  1. The APIs in the grey box are deprecated and will be removed in the future release.
  2. X86Cpu.hh(CPP)/cpuid.h(C) is the new header file that contains the new APIs.

aoclutils

  • All features of aucpuid and aucore combined.

The C headers are in the <installpath>/include/Capi folder and the C++ headers are in the include/Au folder. Deprecated APIs are in the include/alci folder. Note: Refer to API documentation and Examples in Examples folder to understand how to link and use the modules.

Integration with other projects

Following are the build systems to integrate in library/application with AOCL-Utils:

CMAKE

In the CMake file, use the following:

```console TARGETINCLUDEDIRECTORIES() – path of libaoclutils include directory

TARGETLINKLIBRARIES() – path to link libaoclutils binaries ```

Make

In the compiler flags of Make file, use the following:

```console “–I” - path of libaoclutils include directory

“-l, -L” - path to link libaoclutils binaries ```

Owner

  • Name: AMD
  • Login: amd
  • Kind: organization
  • Email: dl.DevSecOps-Github-Admin@amd.com

GitHub Events

Total
  • Release event: 1
  • Watch event: 4
  • Delete event: 1
  • Push event: 9
  • Fork event: 2
  • Create event: 12
Last Year
  • Release event: 1
  • Watch event: 4
  • Delete event: 1
  • Push event: 9
  • Fork event: 2
  • Create event: 12

Committers

Last synced: about 1 year ago

All Time
  • Total Commits: 4
  • Total Committers: 2
  • Avg Commits per committer: 2.0
  • Development Distribution Score (DDS): 0.5
Past Year
  • Commits: 2
  • Committers: 1
  • Avg Commits per committer: 2.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Mohammad Younas Khan Pathan m****n@a****m 2
Abhiram S a****s@a****m 2
Committer Domains (Top 20 + Academic)
amd.com: 2

Issues and Pull Requests

Last synced: about 1 year ago

All Time
  • Total issues: 0
  • Total pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Total issue authors: 0
  • Total pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels