From: Darren Kenny <darren.kenny@oracle.com>
To: Alexander Bulekov <alxndr@bu.edu>, qemu-devel@nongnu.org
Cc: "Alexander Bulekov" <alxndr@bu.edu>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Mauro Matteo Cascella" <mcascell@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Bandan Das" <bsd@redhat.com>,
"Edgar E . Iglesias" <edgar.iglesias@gmail.com>,
"Bin Meng" <bin.meng@windriver.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Jon Maloy" <jmaloy@redhat.com>, "Siqi Chen" <coc.cyqh@gmail.com>
Subject: Re: [PATCH v5 0/4] memory: prevent dma-reentracy issues
Date: Thu, 26 Jan 2023 16:18:46 +0000 [thread overview]
Message-ID: <m2cz71jml5.fsf@oracle.com> (raw)
In-Reply-To: <20230126052558.572634-1-alxndr@bu.edu>
Hi Alex,
From my perspective, I'm happy with the changes made, so from me at
least:
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
Thanks,
Darren.
On Thursday, 2023-01-26 at 00:25:54 -05, Alexander Bulekov wrote:
> These patches aim to solve two types of DMA-reentrancy issues:
>
> 1.) mmio -> dma -> mmio case
> To solve this, we track whether the device is engaged in io by
> checking/setting a reentrancy-guard within APIs used for MMIO access.
>
> 2.) bh -> dma write -> mmio case
> This case is trickier, since we dont have a generic way to associate a
> bh with the underlying Device/DeviceState. Thus, this version allows a
> device to associate a reentrancy-guard with a bh, when creating it.
> (Instead of calling qemu_bh_new, you call qemu_bh_new_guarded)
>
> I replaced most of the qemu_bh_new invocations with the guarded analog,
> except for the ones where the DeviceState was not trivially accessible
>
> v4-> v5:
> - Add corresponding checkpatch checks
> - Save/restore reentrancy-flag when entering/exiting BHs
> - Improve documentation
> - Check object_dynamic_cast return value
>
> v3 -> v4: Instead of changing all of the DMA APIs, instead add an
> optional reentrancy guard to the BH API.
>
> v2 -> v3: Bite the bullet and modify the DMA APIs, rather than
> attempting to guess DeviceStates in BHs.
>
> Alexander Bulekov (4):
> memory: prevent dma-reentracy issues
> async: Add an optional reentrancy guard to the BH API
> checkpatch: add qemu_bh_new/aio_bh_new checks
> hw: replace most qemu_bh_new calls with qemu_bh_new_guarded
>
> docs/devel/multiple-iothreads.txt | 7 +++++++
> hw/9pfs/xen-9p-backend.c | 4 +++-
> hw/block/dataplane/virtio-blk.c | 3 ++-
> hw/block/dataplane/xen-block.c | 5 +++--
> hw/block/virtio-blk.c | 5 +++--
> hw/char/virtio-serial-bus.c | 3 ++-
> hw/display/qxl.c | 9 ++++++---
> hw/display/virtio-gpu.c | 6 ++++--
> hw/ide/ahci.c | 3 ++-
> hw/ide/core.c | 3 ++-
> hw/misc/imx_rngc.c | 6 ++++--
> hw/misc/macio/mac_dbdma.c | 2 +-
> hw/net/virtio-net.c | 3 ++-
> hw/nvme/ctrl.c | 6 ++++--
> hw/scsi/mptsas.c | 3 ++-
> hw/scsi/scsi-bus.c | 3 ++-
> hw/scsi/vmw_pvscsi.c | 3 ++-
> hw/usb/dev-uas.c | 3 ++-
> hw/usb/hcd-dwc2.c | 3 ++-
> hw/usb/hcd-ehci.c | 3 ++-
> hw/usb/hcd-uhci.c | 2 +-
> hw/usb/host-libusb.c | 6 ++++--
> hw/usb/redirect.c | 6 ++++--
> hw/usb/xen-usb.c | 3 ++-
> hw/virtio/virtio-balloon.c | 5 +++--
> hw/virtio/virtio-crypto.c | 3 ++-
> include/block/aio.h | 18 ++++++++++++++++--
> include/hw/qdev-core.h | 7 +++++++
> include/qemu/main-loop.h | 7 +++++--
> scripts/checkpatch.pl | 8 ++++++++
> softmmu/memory.c | 17 +++++++++++++++++
> softmmu/trace-events | 1 +
> tests/unit/ptimer-test-stubs.c | 3 ++-
> util/async.c | 18 +++++++++++++++++-
> util/main-loop.c | 5 +++--
> util/trace-events | 1 +
> 36 files changed, 150 insertions(+), 43 deletions(-)
>
> --
> 2.39.0
next prev parent reply other threads:[~2023-01-26 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 5:25 [PATCH v5 0/4] memory: prevent dma-reentracy issues Alexander Bulekov
2023-01-26 5:25 ` [PATCH v5 1/4] " Alexander Bulekov
2023-01-26 20:54 ` Peter Xu
2023-01-26 5:25 ` [PATCH v5 2/4] async: Add an optional reentrancy guard to the BH API Alexander Bulekov
2023-01-26 5:25 ` [PATCH v5 3/4] checkpatch: add qemu_bh_new/aio_bh_new checks Alexander Bulekov
2023-01-26 14:57 ` Stefan Hajnoczi
2023-01-26 5:25 ` [PATCH v5 4/4] hw: replace most qemu_bh_new calls with qemu_bh_new_guarded Alexander Bulekov
2023-01-26 16:18 ` Darren Kenny [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-26 5:24 [PATCH v5 0/4] memory: prevent dma-reentracy issues Alexander Bulekov
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=m2cz71jml5.fsf@oracle.com \
--to=darren.kenny@oracle.com \
--cc=alxndr@bu.edu \
--cc=berrange@redhat.com \
--cc=bin.meng@windriver.com \
--cc=bsd@redhat.com \
--cc=coc.cyqh@gmail.com \
--cc=david@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=eduardo@habkost.net \
--cc=jasowang@redhat.com \
--cc=jmaloy@redhat.com \
--cc=kraxel@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mcascell@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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 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.