Rather than have every driver implement their own set of cpuid() ugly stuff, provide an abstracted (gcc/clang vs MSVC) API for querying about x86 processor details.
Note: - coming up with a cross arch API seems a difficult task, hence a arch specific API has been preferred. If other arches have ideas how to abstract I am open to suggestions though I won't have the time to implement it for this release, - usage of this arch specific API must not become the common practice and maintainers will have to be wary that drivers are still working fine with generic/common processor/arch features, -- David Marchand David Marchand (2): eal: introduce x86 processor identification common/mlx5: use EAL x86 processor identification MAINTAINERS | 1 + app/test/meson.build | 1 + app/test/test_cpu.c | 37 ++++++++ drivers/common/mlx5/mlx5_common.c | 81 +++++------------ lib/eal/common/eal_common_cpu.c | 141 ++++++++++++++++++++++++++++++ lib/eal/common/eal_cpu.h | 77 ++++++++++++++++ lib/eal/common/meson.build | 1 + lib/eal/version.map | 6 ++ 8 files changed, 285 insertions(+), 60 deletions(-) create mode 100644 app/test/test_cpu.c create mode 100644 lib/eal/common/eal_common_cpu.c create mode 100644 lib/eal/common/eal_cpu.h -- 2.41.0
