qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
	Alex Williamson <alex.williamson@redhat.com>
Cc: lvivier@redhat.com, thuth@redhat.com, qemu-ppc@nongnu.org,
	abologna@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/7] memory: Allow replay of IOMMU mapping notifications
Date: Fri, 25 Sep 2015 13:25:55 +0200	[thread overview]
Message-ID: <56052F43.8030108@redhat.com> (raw)
In-Reply-To: <20150925052434.GD11620@voom.redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 25/09/2015 07:24, David Gibson wrote:
>> When memory_listener_register() replays mappings, it does so on 
>> an rcu copy of the flatview for each AddressSpace.  Here we
>> don't seem to have anything protecting against concurrency... do
>> we need to worry about that?
> 
> I was assuming that the IOMMU mappings are protected by the BQL. I
> _think_ that's the case (for every IOMMU we have so far), but I'm 
> not really sure how to be sure.

Yes, even in listener_add_address_space there's no real need to use
address_space_get_flatview because updates to both the memory maps and
the MemoryListener list are protected by the BQL.  It could just read
as->current_map directly.

listener_add_address_space plays it a bit safe because QEMU doesn't
(yet?) have stuff like rcu_dereference_check.  It's sad that we'll
have to reinvent so much debugging stuff from Linux...

Paolo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWBS9AAAoJEL/70l94x66D5l0H/AxF9flRUf6PaNO6RLpd0N8y
z17BXqKuGIIevkGtF66xCRNDTRgfHKlugKkSQjaQIlGlh2k/nKfozcFERiE6/unv
QmUS3+c3ryLMhOC4VidU90Krq1ZsXLLNE1Z81aSQwD4Y0LXEp3hFuL1F/K6tDUtY
Vzk2KJu/bEaeDhJa4UglBOBLGWIYNRvokIFc2TdoMjdBvKfygLHfjL3rroQOle4U
40/mBO+3J58cyfCBYha0U9DxVTvceaFubj3M72W3ajenXZ15lq75B0M9GCNNujHE
oaP8ehQ5wByyiGGmcZkStEXU/ups7J6cMWWjpTak3PqO0O5DVo+j5P4QbvJE57Q=
=gQRk
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-09-25 11:26 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 [this message]
2015-09-25 11:20   ` Paolo Bonzini
2015-09-25 11:33     ` David Gibson
2015-09-25 12:04       ` Paolo Bonzini
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=56052F43.8030108@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).