From: Cornelia Huck <cohuck@redhat.com>
To: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, borntraeger@de.ibm.com,
pasic@linux.vnet.ibm.com, pmorel@linux.vnet.ibm.com,
agraf@suse.de, richard.henderson@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 3/3] s390x/pci: add iommu replay callback
Date: Tue, 5 Sep 2017 11:28:22 +0200 [thread overview]
Message-ID: <20170905112822.0e9319cd.cohuck@redhat.com> (raw)
In-Reply-To: <1504239778-29893-4-git-send-email-zyimin@linux.vnet.ibm.com>
On Fri, 1 Sep 2017 06:22:58 +0200
Yi Min Zhao <zyimin@linux.vnet.ibm.com> wrote:
> Let's introduce iommu replay callback for s390 pci iommu memory region.
> Currently we don't need any dma mapping replay. So let it return
> directly. This implementation will avoid meaningless loops calling
> translation callback.
>
> Reviewed-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
> Reviewed-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> Signed-off-by: Yi Min Zhao <zyimin@linux.vnet.ibm.com>
> ---
> hw/s390x/s390-pci-bus.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/hw/s390x/s390-pci-bus.c b/hw/s390x/s390-pci-bus.c
> index bd8a3e1e1c..69f45e3715 100644
> --- a/hw/s390x/s390-pci-bus.c
> +++ b/hw/s390x/s390-pci-bus.c
> @@ -397,6 +397,16 @@ static IOMMUTLBEntry s390_translate_iommu(IOMMUMemoryRegion *mr, hwaddr addr,
> return ret;
> }
>
> +static void s390_pci_iommu_replay(IOMMUMemoryRegion *iommu,
> + IOMMUNotifier *notifier)
> +{
> + /* It's impossible to plug a pci device on s390x that already has iommu
> + * mappings which need to be replayed, that is due to the "one iommu per
> + * zpci device" construct. So we don't need iommu replay currently.
I must say that 'currently' still throws me off. Does this refer to
vfio? If yes, reword to something like 'Should we support migration of
vfio-pci devices in the future, we need to revisit this.'?
> + */
> + return;
> +}
> +
> static S390PCIIOMMU *s390_pci_get_iommu(S390pciState *s, PCIBus *bus,
> int devfn)
> {
> @@ -1045,6 +1055,7 @@ static void s390_iommu_memory_region_class_init(ObjectClass *klass, void *data)
> IOMMUMemoryRegionClass *imrc = IOMMU_MEMORY_REGION_CLASS(klass);
>
> imrc->translate = s390_translate_iommu;
> + imrc->replay = s390_pci_iommu_replay;
> }
>
> static const TypeInfo s390_iommu_memory_region_info = {
next prev parent reply other threads:[~2017-09-05 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 4:22 [Qemu-devel] [PATCH v2 0/3] three zpci patches Yi Min Zhao
2017-09-01 4:22 ` [Qemu-devel] [PATCH v2 1/3] s390x/pci: remove idx from msix msg data Yi Min Zhao
2017-09-05 8:29 ` Cornelia Huck
2017-09-05 8:44 ` Yi Min Zhao
2017-09-05 8:50 ` Cornelia Huck
2017-09-05 9:08 ` Yi Min Zhao
2017-09-05 9:15 ` Cornelia Huck
2017-09-05 9:21 ` Yi Min Zhao
2017-09-05 9:25 ` Cornelia Huck
2017-09-01 4:22 ` [Qemu-devel] [PATCH v2 2/3] s390x/pci: fixup ind_offset of msix routing entry Yi Min Zhao
2017-09-05 9:29 ` Cornelia Huck
2017-09-01 4:22 ` [Qemu-devel] [PATCH v2 3/3] s390x/pci: add iommu replay callback Yi Min Zhao
2017-09-05 9:28 ` Cornelia Huck [this message]
2017-09-05 9:51 ` Yi Min Zhao
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=20170905112822.0e9319cd.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=zyimin@linux.vnet.ibm.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).