From: Peter Xu <peterx@redhat.com>
To: Viktor Prutyanov <viktor@daynix.com>
Cc: mst@redhat.com, jasowang@redhat.com, marcel.apfelbaum@gmail.com,
pbonzini@redhat.com, david@redhat.com, philmd@linaro.org,
qemu-devel@nongnu.org, yan@daynix.com,
yuri.benditovich@daynix.com
Subject: Re: [RFC PATCH 3/4] memory: add interface for triggering IOMMU notify_flag_changed handler
Date: Wed, 26 Apr 2023 10:20:18 -0400 [thread overview]
Message-ID: <ZEkzIj017GA3OMMc@x1n> (raw)
In-Reply-To: <20230424112147.17083-4-viktor@daynix.com>
On Mon, Apr 24, 2023 at 02:21:46PM +0300, Viktor Prutyanov wrote:
> +void memory_region_iommu_notify_flags_changed(MemoryRegion *mr)
> +{
> + IOMMUMemoryRegion *iommu_mr;
> +
> + if (mr->alias) {
> + memory_region_iommu_notify_flags_changed(mr->alias);
> + return;
> + }
> + iommu_mr = IOMMU_MEMORY_REGION(mr);
> + memory_region_update_iommu_notify_flags(iommu_mr, NULL);
Do we still want to trap the error if the update failed?
The other question: whether vhost can simply use the existing register /
unregister calls for iommu notifiers, rather than modifying the flags on
its own? I'd assume this happens very rare anyway. Or is there other
concerns?
--
Peter Xu
next prev parent reply other threads:[~2023-04-26 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 11:21 [RFC PATCH 0/4] vhost: register and change IOMMU flag depending on ATS state Viktor Prutyanov
2023-04-24 11:21 ` [RFC PATCH 1/4] pci: add handling of Enable bit in ATS Control Register Viktor Prutyanov
2023-04-26 5:31 ` Jason Wang
2023-04-26 5:48 ` Jason Wang
2023-05-02 21:35 ` Viktor Prutyanov
2023-04-24 11:21 ` [RFC PATCH 2/4] virtio-pci: add handling of ATS state change Viktor Prutyanov
2023-04-26 5:50 ` Jason Wang
2023-04-24 11:21 ` [RFC PATCH 3/4] memory: add interface for triggering IOMMU notify_flag_changed handler Viktor Prutyanov
2023-04-26 14:20 ` Peter Xu [this message]
2023-04-24 11:21 ` [RFC PATCH 4/4] vhost: register and change IOMMU flag depending on ATS state Viktor Prutyanov
2023-04-26 5:54 ` 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=ZEkzIj017GA3OMMc@x1n \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=viktor@daynix.com \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.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 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.