From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Eugenio Perez Martin <eperezma@redhat.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
dev@dpdk.org, chenbox@nvidia.com,
Yongji Xie <xieyongji@bytedance.com>,
mst@redhat.com, jasowangio@gmail.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH 1/9] uapi: import VDUSE and VFIO header from v7.3-rc3 kernel
Date: Thu, 24 Sep 2026 08:37:08 -0700 [thread overview]
Message-ID: <20260924083708.2436f5dd@phoenix.local> (raw)
In-Reply-To: <CAJFAV8w+cau6y0dqdDP7iNHsdjSBNvj6B6m6iy2JCnVf5nLNng@mail.gmail.com>
On Thu, 24 Sep 2026 16:00:19 +0200
David Marchand <david.marchand@redhat.com> wrote:
> We import and update all uapi headers or none in DPDK, for a given
> kernel version.
> And the CI checks that the imported headers are aligned with the
> announced kernel version (meaning that we can't update our local copy
> of the header).
>
> We could import linux/stddef.h but it may become a problem in the future.
> Or pass a -D'__counted_by(a)=' option in the DPDK project CFLAGS if
> the compiler does not support __counted_by...
> Or another option would be to update all users of linux/vfio.h in DPDK... :-(
>
> Other ideas?
I think you need to have headers as a complete set.
For iproute2 ended up having to build a dependency graph so if
foo.h includes bar.h that both foo.h and bar.h are in private tree.
Yes it is a nuisance, but you can't expect kernel to support header cherry picking.
next prev parent reply other threads:[~2026-09-24 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 10:14 [PATCH 0/9] Add vduse live migration features Eugenio Pérez
2026-09-24 10:14 ` [PATCH 1/9] uapi: import VDUSE and VFIO header from v7.3-rc3 kernel Eugenio Pérez
2026-09-24 12:32 ` Eugenio Perez Martin
2026-09-24 14:00 ` David Marchand
2026-09-24 15:37 ` Stephen Hemminger [this message]
2026-09-25 10:21 ` Eugenio Perez Martin
2026-09-24 15:38 ` Stephen Hemminger
2026-09-24 15:50 ` Maxime Coquelin
2026-09-25 9:56 ` Eugenio Perez Martin
2026-09-24 10:14 ` [PATCH 2/9] vhost: introduce ASID support Eugenio Pérez
2026-09-24 10:14 ` [PATCH 3/9] vhost: add VDUSE API version negotiation Eugenio Pérez
2026-09-24 10:14 ` [PATCH 4/9] vhost: add virtqueues groups support to VDUSE Eugenio Pérez
2026-09-24 10:15 ` [PATCH 5/9] vhost: add ASID support to VDUSE IOTLB operations Eugenio Pérez
2026-09-24 10:15 ` [PATCH 6/9] vhost: claim VDUSE support for API version 1 Eugenio Pérez
2026-09-24 10:15 ` [PATCH 7/9] vhost: add net status feature to VDUSE Eugenio Pérez
2026-09-24 10:15 ` [PATCH 8/9] vhost: Support VDUSE QUEUE_READY feature Eugenio Pérez
2026-09-24 10:15 ` [PATCH 9/9] vhost: Support vduse suspend feature Eugenio Pérez
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=20260924083708.2436f5dd@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=xieyongji@bytedance.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.