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 08:34:26 -0400 [thread overview]
Message-ID: <20250423083349-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CA+Lg+WFSwHD5UMC=vQRGm+x3oG69nDFkJqkbzJy61mOJ+VTteQ@mail.gmail.com>
On Wed, Apr 23, 2025 at 12:48:59PM +0200, David George wrote:
> Thanks for the response Michael.
>
> And apologies for the earlier html content.
>
> > See no good reason for that, that header is there so modules outside
> > of vhost don't use it by mistake.
>
> I suppose what I would really be suggesting is adding the possibility
> of a driver outside of vhost/ being able to include _something_,
> enough for it to implement its own vhost target. If you don't see this
> as being useful outside of my use, or my case too narrow, then I
> suppose there probably is no good reason.
>
> Alternatively, what did you think of the suggestion of introducing a
> mechanism of a custom backend for vhost_net? In principal it could
> make the existing mechanism a little neater perhaps?
>
> David
An out of tree module isn't a usecase I care about.
If you make the code neater, I'll be happy to accept the patch.
--
MST
prev parent reply other threads:[~2025-04-23 12:34 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 ` Supporting out of tree custom vhost target modules Michael S. Tsirkin
2025-04-23 10:48 ` David George
2025-04-23 12:34 ` Andrew Lunn
2025-04-23 12:34 ` Michael S. Tsirkin [this message]
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=20250423083349-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 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.