From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: lvivier@redhat.com, thuth@redhat.com, qemu-devel@nongnu.org,
abologna@redhat.com, alex.williamson@redhat.com,
qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/7] memory: Allow replay of IOMMU mapping notifications
Date: Fri, 25 Sep 2015 14:04:14 +0200 [thread overview]
Message-ID: <5605383E.1090406@redhat.com> (raw)
In-Reply-To: <20150925113349.GL11620@voom.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 25/09/2015 13:33, David Gibson wrote:
> 1) Is there a case where using the no-replay functions makes
> sense?
>
> I'm not sure. I think vfio is the only user so far, so I guess
> that's technically a no. I was reluctant to change the interface
> and semantics just off the bat, though.
Considering memory_region_listener does the reply, I think it's okay.
For solving the problem that Laurent mentioned, using int128 seems
like the easiest solution...
Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWBTg7AAoJEL/70l94x66De7AIAIBdzM9tzuZzlMYKG0505+a+
E3K+CrWG0EwN1yzCWU/g4Au17BrSKQ7dVaxeemw48txHtlxxRaTU/WpV0ZGZLS2H
upk3hdgbbgMR7IDgpPHx0MPXDD3nW3h2Xnom5jDr0UF/xpcnVRe+osvs5R3AS8GI
bbbm/QZ3qkIUBUz7w97/d8wYCkZarsB8LoVYoy1nBLvr0QBsL+V0AGV1aw9DpgDk
BtagDntAZQK1doYDVyThK6Ht4agVRF0FEUKR1fej27CriwJJnCOK5zVBP6S9gIZZ
FycmNat1OT573ATlqkjXK6zHsWSvmoM0gdE4Fq3+k/qme3Waz9/v++EEBgqNHXU=
=k/Kg
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-09-25 12:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 4:33 [Qemu-devel] [PATCH 0/7] VFIO extensions to allow VFIO devices on spapr-pci-host-bridge David Gibson
2015-09-24 4:33 ` [Qemu-devel] [PATCH 1/7] vfio: Remove unneeded union from VFIOContainer David Gibson
2015-09-24 16:01 ` Alex Williamson
2015-09-25 5:14 ` David Gibson
2015-09-24 16:10 ` Thomas Huth
2015-09-24 4:33 ` [Qemu-devel] [PATCH 2/7] vfio: Generalize vfio_listener_region_add failure path David Gibson
2015-09-24 4:33 ` [Qemu-devel] [PATCH 3/7] vfio: Check guest IOVA ranges against host IOMMU capabilities David Gibson
2015-09-24 17:32 ` Alex Williamson
2015-09-25 5:20 ` David Gibson
2015-09-24 4:33 ` [Qemu-devel] [PATCH 4/7] vfio: Record host IOMMU's available IO page sizes David Gibson
2015-09-24 17:32 ` Alex Williamson
2015-09-25 5:21 ` David Gibson
2015-09-24 4:33 ` [Qemu-devel] [PATCH 5/7] memory: Allow replay of IOMMU mapping notifications David Gibson
2015-09-24 16:08 ` Laurent Vivier
2015-09-25 5:39 ` David Gibson
2015-09-24 17:32 ` Alex Williamson
2015-09-25 5:24 ` David Gibson
2015-09-25 11:25 ` Paolo Bonzini
2015-09-25 11:20 ` Paolo Bonzini
2015-09-25 11:33 ` David Gibson
2015-09-25 12:04 ` Paolo Bonzini [this message]
2015-09-26 6:54 ` David Gibson
2015-09-28 8:59 ` Paolo Bonzini
2015-09-29 3:30 ` David Gibson
2015-09-29 7:15 ` Paolo Bonzini
2015-09-30 2:15 ` David Gibson
2015-09-24 4:33 ` [Qemu-devel] [PATCH 6/7] vfio: Allow hotplug of containers onto existing guest IOMMU mappings David Gibson
2015-09-24 4:33 ` [Qemu-devel] [PATCH 7/7] vfio: Expose a VFIO PCI device's group for EEH David Gibson
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=5605383E.1090406@redhat.com \
--to=pbonzini@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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).