linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Eugenio Perez Martin <eperezma@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	jasowang@redhat.com, Yongji Xie <xieyongji@bytedance.com>,
	Cindy Lu <lulu@redhat.com>,
	linux-kernel@vger.kernel.org,
	Stefano Garzarella <sgarzare@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Maxime Coquelin <mcoqueli@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	virtualization@lists.linux.dev,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	Laurent Vivier <lvivier@redhat.com>
Subject: Re: [RFC 0/6] Add multiple address spaces support to VDUSE
Date: Sun, 22 Jun 2025 22:09:00 -0700	[thread overview]
Message-ID: <aFjhbCnEI7KZW8Sr@infradead.org> (raw)
In-Reply-To: <CAJaqyWek+ckdXFZdhpcXwDB7a5X=PMSktEADVpR5Nbi-n+MR0w@mail.gmail.com>

On Fri, Jun 20, 2025 at 08:25:50AM +0200, Eugenio Perez Martin wrote:
> This code does not touch the DMA API at all. Actually, we could even
> remove all the DMA code and these changes would work the same. Can't
> we just continue with this series and remove the abuse of the DMA API
> in parallel?

But it touches vduse.  And vduse is marked broken because it still has
this long standing issues.  You don't add "ehancements" to code marked
BROKEN begfore fixing that.


      reply	other threads:[~2025-06-23  5:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06 11:50 [RFC 0/6] Add multiple address spaces support to VDUSE Eugenio Pérez
2025-06-06 11:50 ` [RFC 1/6] vduse: add v1 API definition Eugenio Pérez
2025-06-09  1:41   ` Jason Wang
2025-06-09  1:50     ` Jason Wang
2025-06-09  6:10       ` Eugenio Perez Martin
2025-06-10  8:35         ` Jason Wang
2025-08-07 10:55           ` Eugenio Perez Martin
2025-08-08  0:50             ` Jason Wang
2025-08-10 10:18               ` Eugenio Perez Martin
2025-08-11  2:58                 ` Jason Wang
2025-08-11  9:01                   ` Eugenio Perez Martin
2025-08-12  2:55                     ` Jason Wang
2025-08-12  6:03                       ` Eugenio Perez Martin
2025-06-06 11:50 ` [RFC 2/6] vduse: add vq group support Eugenio Pérez
2025-06-09  1:55   ` Jason Wang
2025-06-09  6:03     ` Eugenio Perez Martin
2025-06-10  8:53       ` Jason Wang
2025-06-06 11:50 ` [RFC 3/6] vduse: add vq group asid support Eugenio Pérez
2025-06-12  0:30   ` Jason Wang
2025-06-12  7:24     ` Eugenio Perez Martin
2025-06-13  1:21       ` Jason Wang
2025-08-07 11:10         ` Eugenio Perez Martin
2025-06-06 11:50 ` [RFC 4/6] vduse: send update_iotlb_v2 message Eugenio Pérez
2025-06-06 11:50 ` [RFC 5/6] vduse: reset group asid in reset Eugenio Pérez
2025-06-12  0:32   ` Jason Wang
2025-06-12  7:24     ` Eugenio Perez Martin
2025-06-06 11:50 ` [RFC 6/6] vduse: bump version number Eugenio Pérez
2025-06-09  5:51 ` [RFC 0/6] Add multiple address spaces support to VDUSE Christoph Hellwig
2025-06-20  6:25   ` Eugenio Perez Martin
2025-06-23  5:09     ` Christoph Hellwig [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=aFjhbCnEI7KZW8Sr@infradead.org \
    --to=hch@infradead.org \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lulu@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mcoqueli@redhat.com \
    --cc=mst@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xieyongji@bytedance.com \
    --cc=xuanzhuo@linux.alibaba.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 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).