DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, techboard@dpdk.org, david.marchand@redhat.com,
	thomas@monjalon.net, mb@smartsharesystems.com
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [RFC v2 0/3] Import Kernel uAPI header files
Date: Fri,  6 Sep 2024 17:23:34 +0200	[thread overview]
Message-ID: <20240906152337.2805036-1-maxime.coquelin@redhat.com> (raw)

This series enables importing Linux Kernel uAPI headers
into the DPDK repository. It aims at solving alignment
issues between the build system and the system applications
linked ot DPDK libraries are run on.

It can also help simplify spaghetti code done to support
different versions of the Linux Kernel headers used by
the build system.

Guidelines and import script are also part of first patch.
A uAPI checker script is added in this 2nd RFC, goals is to
use it in CI for any patch touching linux-headers/uapi.

Follow-up patches are an example of imported uAPI inclusion
of VDUSE header into the Vhost library.

Morten, I did not apply your Ack on patch 1, as it has
some significant changes and additions.

Changes in RFC v2:
==================
- Fix typos in documentation and commit messags (David, Morten)
- Add uAPI checker script
- Add uAPI to global_inc
- Fix build issues on FreeBSD and documentation (CI, David)
- Simplify import script (David)

Maxime Coquelin (3):
  uapi: introduce kernel uAPI headers import
  uapi: import VDUSE header
  vduse: use import VDUSE uAPI header

 devtools/check-linux-uapi.sh           |  74 ++++++
 devtools/import-linux-uapi.sh          |  45 ++++
 doc/guides/contributing/index.rst      |   1 +
 doc/guides/contributing/linux_uapi.rst |  77 ++++++
 lib/vhost/meson.build                  |   5 +-
 lib/vhost/vduse.c                      |   2 +-
 lib/vhost/vduse.h                      |  22 --
 linux-headers/uapi/.gitignore          |   3 +
 linux-headers/uapi/linux/vduse.h       | 353 +++++++++++++++++++++++++
 meson.build                            |   8 +-
 10 files changed, 561 insertions(+), 29 deletions(-)
 create mode 100755 devtools/check-linux-uapi.sh
 create mode 100755 devtools/import-linux-uapi.sh
 create mode 100644 doc/guides/contributing/linux_uapi.rst
 create mode 100644 linux-headers/uapi/.gitignore
 create mode 100644 linux-headers/uapi/linux/vduse.h

-- 
2.46.0


             reply	other threads:[~2024-09-06 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 15:23 Maxime Coquelin [this message]
2024-09-06 15:23 ` [RFC v2 1/3] uapi: introduce kernel uAPI headers import Maxime Coquelin
2024-09-07 14:06   ` Morten Brørup
2024-09-07 14:34   ` David Marchand
2024-09-11 19:55     ` Maxime Coquelin
2024-09-06 15:23 ` [RFC v2 2/3] uapi: import VDUSE header Maxime Coquelin
2024-09-06 15:23 ` [RFC v2 3/3] vduse: use import VDUSE uAPI header Maxime Coquelin
2024-09-09  0:31 ` [RFC v2 0/3] Import Kernel uAPI header files Stephen Hemminger
2024-09-09  7:34   ` Maxime Coquelin

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=20240906152337.2805036-1-maxime.coquelin@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).