From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: ferruh.yigit@amd.com, thomas@monjalon.net,
bruce.richardson@intel.com, konstantin.v.ananyev@yandex.ru,
ruifeng.wang@arm.com, zhoumin@loongson.cn,
drc@linux.vnet.ibm.com, kda@semihalf.com,
roretzla@linux.microsoft.com
Subject: [PATCH 0/2] Introduce x86 specific identification API
Date: Fri, 22 Sep 2023 11:37:19 +0200 [thread overview]
Message-ID: <20230922093722.2057688-1-david.marchand@redhat.com> (raw)
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
next reply other threads:[~2023-09-22 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 9:37 David Marchand [this message]
2023-09-22 9:37 ` [PATCH 1/2] eal: introduce x86 processor identification David Marchand
2023-09-22 9:46 ` Bruce Richardson
2023-09-25 9:42 ` David Marchand
2023-09-22 10:38 ` Bruce Richardson
2023-09-22 10:55 ` Bruce Richardson
2023-09-25 9:46 ` David Marchand
2023-09-25 10:16 ` Bruce Richardson
2023-09-25 10:52 ` Morten Brørup
2023-09-22 9:37 ` [PATCH 2/2] common/mlx5: use EAL " David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230922093722.2057688-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=ferruh.yigit@amd.com \
--cc=kda@semihalf.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=roretzla@linux.microsoft.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=zhoumin@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).