From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Srujana Challa <schalla@marvell.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"eperezma@redhat.com" <eperezma@redhat.com>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [EXTERNAL] Re: [PATCH v2 0/2] vhost-vdpa: Add support for NO-IOMMU mode
Date: Sat, 19 Oct 2024 20:16:44 -0400 [thread overview]
Message-ID: <20241019201059-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <ZxCrqPPbidzZb6w1@infradead.org>
On Wed, Oct 16, 2024 at 11:16:08PM -0700, Christoph Hellwig wrote:
> On Wed, Oct 16, 2024 at 01:41:51PM -0400, Michael S. Tsirkin wrote:
> > It's basically because vfio does, so we have to follow suit.
>
> That's a very bold argument, especially without any rationale of
>
> a) why you need to match the feature set
Because people want to move from some vendor specific solution with vfio
to a standard vdpa compatible one with vdpa.
We could just block them since we don't support tainted kernels anyway,
but it's a step in the right direction since it allows moving to
virtio, and the kernel is tained so no big support costs (although
qe costs do exist, as with any code).
> b) how even adding it to vfio was agood idea
That ship has sailed.
--
MST
next prev parent reply other threads:[~2024-10-20 0:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 14:05 [PATCH v2 0/2] vhost-vdpa: Add support for NO-IOMMU mode Srujana Challa
2024-09-20 14:05 ` [PATCH v2 1/2] vhost-vdpa: introduce module parameter for no-IOMMU mode Srujana Challa
2024-09-21 17:28 ` kernel test robot
2024-09-20 14:05 ` [PATCH v2 2/2] vhost-vdpa: introduce NO-IOMMU backend feature bit Srujana Challa
2024-09-24 7:43 ` Jason Wang
2024-09-24 10:01 ` [EXTERNAL] " Srujana Challa
2024-10-01 8:47 ` [PATCH v2 0/2] vhost-vdpa: Add support for NO-IOMMU mode Christoph Hellwig
2024-10-14 13:18 ` [EXTERNAL] " Srujana Challa
2024-10-15 3:48 ` Christoph Hellwig
2024-10-16 17:28 ` Srujana Challa
2024-10-17 6:19 ` Christoph Hellwig
2024-10-17 8:53 ` Srujana Challa
2024-10-18 4:54 ` Jason Wang
2024-10-18 5:24 ` Christoph Hellwig
2024-10-18 13:08 ` Srujana Challa
2024-10-16 17:41 ` Michael S. Tsirkin
2024-10-17 6:16 ` Christoph Hellwig
2024-10-20 0:16 ` Michael S. Tsirkin [this message]
2024-10-23 6:58 ` Christoph Hellwig
2024-10-23 8:19 ` Michael S. Tsirkin
2024-10-24 9:05 ` Christoph Hellwig
2024-11-06 12:38 ` Srujana Challa
2024-11-06 15:45 ` Christoph Hellwig
2024-11-07 6:08 ` Srujana Challa
2024-11-12 7:11 ` Srujana Challa
2024-11-06 18:11 ` Michael S. Tsirkin
2024-11-06 18:14 ` 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=20241019201059-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=jerinj@marvell.com \
--cc=kvm@vger.kernel.org \
--cc=ndabilpuram@marvell.com \
--cc=schalla@marvell.com \
--cc=virtualization@lists.linux.dev \
/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.