From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
dev@dpdk.org, techboard@dpdk.org, david.marchand@redhat.com,
thomas@monjalon.net, mb@smartsharesystems.com,
stephen@networkplumber.org
Subject: Re: [RFC v3 0/3] Import Kernel uAPI header files
Date: Thu, 12 Sep 2024 14:08:08 +0200 [thread overview]
Message-ID: <656c4c4b-5aca-4668-b292-a40441fbee17@redhat.com> (raw)
In-Reply-To: <6df4dd8b-be68-4ca3-8593-9e694577a4d8@amd.com>
Hi Ferruh,
On 9/12/24 10:30, Ferruh Yigit wrote:
> On 9/11/2024 8:32 PM, Maxime Coquelin wrote:
>> 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.
>>
>
> Hi Maxime,
>
> Is the imported Linux Kernel uAPI headers are always backward compatible?
Yes, at least that's what is advertised! :)
"
The binary interface provided by the kernel to user space cannot be
broken except under the most severe circumstances.
"
> If I build and run on identical platform, lets say has kernel v5.4,
> and DPDK has the kernel uAPI header from v6.10, is this has any chance
> to create backward compatibility issues?
It should not if backward compatibility is preserved as advertised.
> Or can it enable some features which are indeed not exist/supported in
> the platform that has old version of kernel?
It can enable new feature, like for example a new ioctl command.
In this case, it should return something like ENOIOCTLCMD if the Kernel
does not support it.
>
>> 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 3rd 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 (again) apply your Ack on patch 1, as it
>> has some significant changes and additions.
>>
>> Changes in RFC v3:
>> ==================
>> - Support nested headers include
>> - Interactive mode to select which headers to include
>> - Store version in a file instead of git commit messages
>> - All imported headers aligned on same version
>> - Improve loops in scripts (David)
>> - Update documentation
>>
>>
>> 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 imported VDUSE uAPI header
>>
>> devtools/check-linux-uapi.sh | 85 ++++++
>> devtools/import-linux-uapi.sh | 119 +++++++++
>> doc/guides/contributing/index.rst | 1 +
>> doc/guides/contributing/linux_uapi.rst | 71 +++++
>> lib/vhost/meson.build | 5 +-
>> lib/vhost/vduse.c | 2 +-
>> lib/vhost/vduse.h | 22 --
>> linux-headers/uapi/.gitignore | 4 +
>> linux-headers/uapi/linux/vduse.h | 353 +++++++++++++++++++++++++
>> linux-headers/uapi/version | 1 +
>> meson.build | 8 +-
>> 11 files changed, 642 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
>> create mode 100644 linux-headers/uapi/version
>>
>
next prev parent reply other threads:[~2024-09-12 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 19:32 Maxime Coquelin
2024-09-11 19:32 ` [RFC v3 1/3] uapi: introduce kernel uAPI headers import Maxime Coquelin
2024-09-17 11:36 ` David Marchand
2024-09-17 14:32 ` Maxime Coquelin
2024-09-19 8:39 ` Thomas Monjalon
2024-09-11 19:32 ` [RFC v3 2/3] uapi: import VDUSE header Maxime Coquelin
2024-09-11 19:32 ` [RFC v3 3/3] vduse: use imported VDUSE uAPI header Maxime Coquelin
2024-09-12 8:30 ` [RFC v3 0/3] Import Kernel uAPI header files Ferruh Yigit
2024-09-12 12:08 ` Maxime Coquelin [this message]
2024-09-12 13:16 ` Ferruh Yigit
2024-09-12 13:47 ` 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=656c4c4b-5aca-4668-b292-a40441fbee17@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.org \
--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).