From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Christian Speich" <c.speich@avm.de>,
qemu-devel@nongnu.org, "Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: [PATCH] virtio: vhost-user-device: Make user creatable again
Date: Sat, 4 Oct 2025 13:33:48 -0400 [thread overview]
Message-ID: <20251004133102-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <aNpaSpF_qY6z03Q3@redhat.com>
On Mon, Sep 29, 2025 at 11:07:06AM +0100, Daniel P. Berrangé wrote:
> > Well that's because e.g. kvmtest actually depends on pci-testdev.
> > IOW it's actually supported.
>
> This again just sounds like a downstream 'support' rationalization.
> I'm still not seeing a compelling reason why the vhost user generic
> device should be disabled by default in upstream, especially if we
> mark it as an experimental device with an x- prefix.
>
> With regards,
> Daniel
We can do that. I am still somewhat puzzled by whether making
it unsupported/experimental addresses the actual need, which
seems to be to expose it to end users?
Once something is used in the field, we can't take it back
whether we added x- to the name or not.
What are your thoughts if it's not marked as experimental?
--
MST
next prev parent reply other threads:[~2025-10-04 17:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 14:30 [PATCH] virtio: vhost-user-device: Make user creatable again Christian Speich
2025-09-19 14:46 ` Stefano Garzarella
2025-09-19 20:07 ` Michael S. Tsirkin
2025-09-22 10:40 ` Christian Speich via
2025-09-22 10:56 ` Michael S. Tsirkin
2025-09-22 11:11 ` Christian Speich via
2025-09-22 14:37 ` Michael S. Tsirkin
2025-09-25 7:56 ` Christian Speich
2025-09-25 9:33 ` Michael S. Tsirkin
2025-09-25 10:14 ` Christian Speich
2025-09-22 11:33 ` Daniel P. Berrangé
2025-09-22 12:15 ` Michael S. Tsirkin
2025-09-22 12:49 ` Daniel P. Berrangé
2025-09-22 13:08 ` Michael S. Tsirkin
2025-09-22 13:26 ` Christian Speich via
2025-09-22 13:30 ` Michael S. Tsirkin
2025-09-22 13:42 ` Christian Speich
2025-09-22 15:14 ` Alex Bennée
2025-09-29 8:12 ` Christian Speich
2025-09-29 8:22 ` Daniel P. Berrangé
2025-09-29 8:24 ` Michael S. Tsirkin
2025-09-29 9:52 ` Alex Bennée
2025-09-29 10:07 ` Daniel P. Berrangé
2025-10-04 17:33 ` Michael S. Tsirkin [this message]
2025-10-09 10:20 ` Daniel P. Berrangé
2025-10-09 16:49 ` Alex Bennée
2025-09-22 12:51 ` Alex Bennée
2025-09-22 13:33 ` Christian Speich
2025-09-22 14:38 ` Daniel P. Berrangé
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=20251004133102-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=c.speich@avm.de \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.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.