[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3fe5971a-5991-488f-cef5-473c9faa1ba1@redhat.com>
Date: Sun, 29 Jan 2023 18:58:09 +0100
From: Eric Auger <eric.auger@...hat.com>
To: eric.auger.pro@...il.com, mst@...hat.com, jasowang@...hat.com,
kvm@...r.kernel.org, netdev@...r.kernel.org,
virtualization@...ts.linux-foundation.org
Cc: peterx@...hat.com, lvivier@...hat.com
Subject: Re: [PATCH 0/2] vhost/net: Clear the pending messages when the
backend is removed
Hi,
On 1/17/23 16:15, Eric Auger wrote:
> When the vhost iotlb is used along with a guest virtual iommu
> and the guest gets rebooted, some MISS messages may have been
> recorded just before the reboot and spuriously executed by
> the virtual iommu after the reboot. This is due to the fact
> the pending messages are not cleared.
>
> As vhost does not have any explicit reset user API,
> VHOST_NET_SET_BACKEND looks a reasonable point where to clear
> the pending messages, in case the backend is removed (fd = -1).
>
> This version is a follow-up on the discussions held in [1].
>
> The first patch removes an unused 'enabled' parameter in
> vhost_init_device_iotlb().
Gentle Ping. Does it look a reasonable fix now?
Thanks
Eric
>
> Best Regards
>
> Eric
>
> History:
> [1] RFC: [RFC] vhost: Clear the pending messages on vhost_init_device_iotlb()
> https://lore.kernel.org/all/20221107203431.368306-1-eric.auger@redhat.com/
>
> Eric Auger (2):
> vhost: Remove the enabled parameter from vhost_init_device_iotlb
> vhost/net: Clear the pending messages when the backend is removed
>
> drivers/vhost/net.c | 5 ++++-
> drivers/vhost/vhost.c | 5 +++--
> drivers/vhost/vhost.h | 3 ++-
> 3 files changed, 9 insertions(+), 4 deletions(-)
>
Powered by blists - more mailing lists