qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
	Jason Wang <jasowang@redhat.com>,
	"eric.auger.pro@gmail.com" <eric.auger.pro@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"sgarzare@redhat.com" <sgarzare@redhat.com>,
	"lvivier@redhat.com" <lvivier@redhat.com>,
	Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH] hw/virtio/vhost: Disable IOTLB callbacks when IOMMU gets disabled
Date: Thu, 20 Feb 2025 16:57:51 +0100	[thread overview]
Message-ID: <fa16f5f1-48a2-4c5d-8b80-4ec012871302@redhat.com> (raw)
In-Reply-To: <20250220102429-mutt-send-email-mst@kernel.org>

Hi Michael,


On 2/20/25 4:25 PM, Michael S. Tsirkin wrote:
> On Fri, Jan 31, 2025 at 10:55:26AM +0100, Eric Auger wrote:
>> I tested [PATCH] virtio: Remove virtio devices on device_shutdown()
>> https://lore.kernel.org/all/20240808075141.3433253-1-kirill.shutemov@linux.intel.com/
>>
>> and it fixes my issue
>>
>> Eric
>
> To make sure, we are dropping this in favor of the guest fix (which
> I intent to merge shortly), correct?

Yes this should be dropped in favour of the implementation of the
shutdown callback on guest side. Did you send your patch, I did not see it.

however on qemu side, there is "[PATCH v3 0/5] Fix vIOMMU reset order"
that needs to be merged to fix qmp system_reset.

Thanks

Eric
>



  reply	other threads:[~2025-02-20 15:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 17:33 [PATCH] hw/virtio/vhost: Disable IOTLB callbacks when IOMMU gets disabled Eric Auger
2025-01-21  3:27 ` Jason Wang
2025-01-21  7:15   ` Eric Auger
2025-01-21 16:25   ` Eric Auger
2025-01-22  7:17     ` Jason Wang
2025-01-22  7:55       ` Eric Auger
2025-01-23  1:34         ` Jason Wang
2025-01-23  8:31           ` Eric Auger
2025-01-24  1:48             ` Jason Wang
2025-01-24  2:44             ` Duan, Zhenzhong
2025-01-24  3:30               ` Jason Wang
2025-01-24  3:41                 ` Jason Wang
2025-01-24  4:00                   ` Duan, Zhenzhong
2025-01-24  9:20                     ` Jason Wang
2025-01-24  9:50                       ` Duan, Zhenzhong
2025-01-24 17:56                   ` Eric Auger
2025-01-24 15:18                 ` Peter Xu
2025-01-26  7:56                   ` Jason Wang
2025-01-27  0:44                     ` Jason Wang
2025-01-30 17:35                       ` Peter Xu
2025-01-24 17:47               ` Eric Auger
2025-01-26  7:09                 ` Duan, Zhenzhong
2025-01-31  9:55               ` Eric Auger
2025-02-20 15:25                 ` Michael S. Tsirkin
2025-02-20 15:57                   ` Eric Auger [this message]
2025-02-20 23:27                     ` Michael S. Tsirkin
2025-01-21  8:31 ` Laurent Vivier
2025-01-21  8:45   ` Stefano Garzarella
2025-01-21  8:49     ` Eric Auger
2025-01-21  8:48   ` Eric Auger
2025-01-21 16:32   ` Eric Auger
2025-01-21  9:18 ` Duan, Zhenzhong
2025-01-21 10:34   ` Eric Auger
2025-01-21 10:43     ` Duan, Zhenzhong

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=fa16f5f1-48a2-4c5d-8b80-4ec012871302@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=eric.auger.pro@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=zhenzhong.duan@intel.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).