[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJaqyWdLB1dWASf6NXW_8VXUNoWQ=G4pGjZLRbD_3U=2rfXkig@mail.gmail.com>
Date: Tue, 16 Sep 2025 08:37:12 +0200
From: Eugenio Perez Martin <eperezma@...hat.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Cindy Lu <lulu@...hat.com>, Stefano Garzarella <sgarzare@...hat.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, Laurent Vivier <lvivier@...hat.com>,
virtualization@...ts.linux.dev, linux-kernel@...r.kernel.org,
jasowang@...hat.com, Yongji Xie <xieyongji@...edance.com>,
Maxime Coquelin <mcoqueli@...hat.com>
Subject: Re: [PATCH 0/6] Add multiple address spaces support to VDUSE
On Tue, Sep 16, 2025 at 12:42 AM Michael S. Tsirkin <mst@...hat.com> wrote:
>
> On Tue, Aug 26, 2025 at 01:27:03PM +0200, Eugenio Pérez wrote:
> > When used by vhost-vDPA bus driver for VM, the control virtqueue
> > should be shadowed via userspace VMM (QEMU) instead of being assigned
> > directly to Guest. This is because QEMU needs to know the device state
> > in order to start and stop device correctly (e.g for Live Migration).
> >
> > This requies to isolate the memory mapping for control virtqueue
> > presented by vhost-vDPA to prevent guest from accessing it directly.
> >
> > This series add support to multiple address spaces in VDUSE device
> > allowing selective virtqueue isolation through address space IDs (ASID).
>
>
> There hasn't been a new version of this yet, has there?
>
No, I was on PTO last week. I plan to send it today.
Thanks!
Powered by blists - more mailing lists