From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jia Jia <physicalmtea@gmail.com>
Cc: stefanha@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] vhost/vsock: fix device IOTLB feature lifecycle
Date: Mon, 3 Aug 2026 23:19:30 -0400 [thread overview]
Message-ID: <20260803231911-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260731103414.1746316-1-physicalmtea@gmail.com>
On Fri, Jul 31, 2026 at 06:34:12PM +0800, Jia Jia wrote:
> As suggested, split the changes into two patches.
>
> Patch 1 detaches and frees the device IOTLB when ACCESS_PLATFORM is
> cleared. The device and virtqueue IOTLB pointers, metadata caches, and
> acked features are updated while all virtqueue mutexes are held. It also
> drops old IOTLB miss messages and wakes readers.
>
> Patch 2 keeps the current IOTLB when ACCESS_PLATFORM remains enabled,
> so a runtime logging update does not discard valid translations.
pls do not post v2 as reply to v1. confuses tools. thanks!
> Changes since v1:
> - discard the existing IOTLB instead of returning -EBUSY
> - serialize the switch against all virtqueues
> - clear old IOTLB messages and wake readers
> - move the existing-IOTLB preservation change to a separate patch
>
> Jia Jia (2):
> vhost/vsock: discard IOTLB when ACCESS_PLATFORM is cleared
> vhost/vsock: keep IOTLB across feature updates
>
> drivers/vhost/vsock.c | 46 +++++++++++++++++++++++++++++++++++++------
> 1 file changed, 40 insertions(+), 6 deletions(-)
>
> --
> 2.34.1
next prev parent reply other threads:[~2026-08-04 3:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 4:09 [PATCH] vhost/vsock: prevent stale IOTLB after ACCESS_PLATFORM changes Jia Jia
2026-07-30 4:36 ` sashiko-bot
2026-07-30 13:55 ` Stefan Hajnoczi
2026-07-30 14:48 ` Michael S. Tsirkin
2026-07-30 14:51 ` Michael S. Tsirkin
2026-07-31 4:41 ` Jia Jia
2026-07-31 9:38 ` Michael S. Tsirkin
2026-07-31 10:34 ` [PATCH v2 0/2] vhost/vsock: fix device IOTLB feature lifecycle Jia Jia
2026-07-31 10:34 ` [PATCH v2 1/2] vhost/vsock: discard IOTLB when ACCESS_PLATFORM is cleared Jia Jia
2026-07-31 10:56 ` sashiko-bot
2026-08-04 3:18 ` Michael S. Tsirkin
2026-08-04 4:18 ` Jia Jia
2026-08-04 7:21 ` Jia Jia
2026-07-31 10:34 ` [PATCH v2 2/2] vhost/vsock: keep IOTLB across feature updates Jia Jia
2026-07-31 11:03 ` sashiko-bot
2026-08-04 3:20 ` Michael S. Tsirkin
2026-08-04 4:26 ` Jia Jia
2026-08-04 3:19 ` Michael S. Tsirkin [this message]
2026-08-04 4:30 ` [PATCH v2 0/2] vhost/vsock: fix device IOTLB feature lifecycle Jia Jia
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=20260803231911-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=physicalmtea@gmail.com \
--cc=stefanha@redhat.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.