From: "Michael S. Tsirkin" <mst@redhat.com>
To: David George <dgeorgester@gmail.com>
Cc: netdev@vger.kernel.org, jasowang@redhat.com
Subject: Re: Supporting out of tree custom vhost target modules
Date: Wed, 23 Apr 2025 06:01:43 -0400 [thread overview]
Message-ID: <20250423060040-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CA+Lg+WFYqXdNUJ2ZQ0=TY58T+Pyay4ONT=8z3LASQXSqN3A0VA@mail.gmail.com>
On Wed, Apr 23, 2025 at 11:47:49AM +0200, David George wrote:
> Hello all
>
> I am in the process of writing an out of tree kernel module that does a very
> similar job to vhost_net. The problem is that plain tap devices aren't quite
> going to cover what I want to do (1:N device mapping and various exotic
> offloads).
>
> The approach I am taking at the moment is to tweak vhost/net.c to suit my needs
> and operate it as an out of tree module. The problem with this approach is the
> "vhost.h" is not in include/ so won't be usable without the whole source tree
> to compile against.
>
> Is promoting vhost.h from drivers/vhost to include/xyz/ something that could be
> considered?
>
> Alternatively, what I want to do could perhaps be done through an API to
> register a custom socket associated with a custom misc dev within vhost_net,
> but that is a lot more invasive.
>
> Thanks,
> David George
See no good reason for that, that header is there so modules outside
of vhost don't use it by mistake.
next parent reply other threads:[~2025-04-23 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+Lg+WFYqXdNUJ2ZQ0=TY58T+Pyay4ONT=8z3LASQXSqN3A0VA@mail.gmail.com>
2025-04-23 10:01 ` Michael S. Tsirkin [this message]
2025-04-23 10:48 ` Supporting out of tree custom vhost target modules David George
2025-04-23 12:34 ` Andrew Lunn
2025-04-23 12:34 ` Michael S. Tsirkin
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=20250423060040-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgeorgester@gmail.com \
--cc=jasowang@redhat.com \
--cc=netdev@vger.kernel.org \
/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).