From: Eric Auger <eric.auger@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: eric.auger.pro@gmail.com, jasowang@redhat.com,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
peterx@redhat.com
Subject: Re: [RFC] vhost: Clear the pending messages on vhost_init_device_iotlb()
Date: Mon, 7 Nov 2022 22:10:06 +0100 [thread overview]
Message-ID: <b8487793-d7b8-0557-a4c2-b62754e14830@redhat.com> (raw)
In-Reply-To: <20221107153924-mutt-send-email-mst@kernel.org>
Hi Michael,
On 11/7/22 21:42, Michael S. Tsirkin wrote:
> On Mon, Nov 07, 2022 at 09:34:31PM +0100, 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. Despite the device iotlb gets
>> re-initialized, the messages are not cleared. Fix that by calling
>> vhost_clear_msg() at the end of vhost_init_device_iotlb().
>>
>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>> ---
>> drivers/vhost/vhost.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
>> index 40097826cff0..422a1fdee0ca 100644
>> --- a/drivers/vhost/vhost.c
>> +++ b/drivers/vhost/vhost.c
>> @@ -1751,6 +1751,7 @@ int vhost_init_device_iotlb(struct vhost_dev *d, bool enabled)
>> }
>>
>> vhost_iotlb_free(oiotlb);
>> + vhost_clear_msg(d);
>>
>> return 0;
>> }
> Hmm. Can't messages meanwhile get processes and affect the
> new iotlb?
Isn't the msg processing stopped at the moment this function is called
(VHOST_SET_FEATURES)?
Thanks
Eric
>
>
>> --
>> 2.37.3
next prev parent reply other threads:[~2022-11-07 21:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 20:34 Eric Auger
2022-11-07 20:42 ` Michael S. Tsirkin
2022-11-07 21:10 ` Eric Auger [this message]
2022-11-07 23:06 ` Michael S. Tsirkin
2022-11-08 3:09 ` Jason Wang
2022-11-08 7:31 ` Eric Auger
2022-11-08 8:55 ` Michael S. Tsirkin
2022-11-08 9:13 ` Jason Wang
2022-11-08 9:31 ` Michael S. Tsirkin
2022-11-08 10:17 ` Eric Auger
2022-11-09 3:44 ` Jason Wang
2022-11-09 7:29 ` Eric Auger
2022-11-09 3:39 ` Jason Wang
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=b8487793-d7b8-0557-a4c2-b62754e14830@redhat.com \
--to=eric.auger@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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
all inboxes | Powered by JetHome®