From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>
Cc: qemu-devel@nongnu.org, "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>,
"Darren Kenny" <darren.kenny@oracle.com>,
"Bin Meng" <bin.meng@windriver.com>,
"Paolo Bonzini" <pbonzini@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 v6 0/4] memory: prevent dma-reentracy issues
Date: Mon, 13 Feb 2023 15:26:49 -0500 [thread overview]
Message-ID: <20230213152618-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230213021141.mmzdpzj6ekmml3bx@mozz.bu.edu>
On Sun, Feb 12, 2023 at 09:11:41PM -0500, Alexander Bulekov wrote:
> ping
>
> On 230204 2307, 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.
> >
> > v5 -> v6:
> > - Only apply checkpatch checks to code in paths containing "/hw/"
> > (/hw/ and include/hw/)
> > - Fix a bug in a _guarded call added to hw/block/virtio-blk.c
> > 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.
As long as we are adding the new APIs virtio things look ok to me.
Pls merge with rest of patches.
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> > 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/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 +
> > 35 files changed, 147 insertions(+), 41 deletions(-)
> >
> > --
> > 2.39.0
> >
next prev parent reply other threads:[~2023-02-13 20:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 4:07 [PATCH v6 0/4] memory: prevent dma-reentracy issues Alexander Bulekov
2023-02-05 4:07 ` [PATCH v6 1/4] " Alexander Bulekov
2023-03-10 11:14 ` Fiona Ebner
2023-03-10 12:23 ` Alexander Bulekov
2023-03-10 12:31 ` Alexander Bulekov
2023-03-10 12:45 ` Peter Maydell
2023-03-10 13:02 ` Alexander Bulekov
2023-03-10 13:28 ` Alexander Bulekov
2023-03-10 13:37 ` Peter Maydell
2023-03-10 13:07 ` Mark Cave-Ayland
2023-02-05 4:07 ` [PATCH v6 2/4] async: Add an optional reentrancy guard to the BH API Alexander Bulekov
2023-02-05 4:07 ` [PATCH v6 3/4] checkpatch: add qemu_bh_new/aio_bh_new checks Alexander Bulekov
2023-02-05 4:07 ` [PATCH v6 4/4] hw: replace most qemu_bh_new calls with qemu_bh_new_guarded Alexander Bulekov
2023-03-01 20:54 ` Michael S. Tsirkin
2023-03-02 9:25 ` Paul Durrant
2023-03-08 13:40 ` Alexander Bulekov
2023-03-10 10:38 ` Thomas Huth
2023-02-13 2:11 ` [PATCH v6 0/4] memory: prevent dma-reentracy issues Alexander Bulekov
2023-02-13 20:26 ` Michael S. Tsirkin [this message]
2023-02-16 11:14 ` Thomas Huth
2023-02-28 16:07 ` Alexander Bulekov
2023-02-28 16:28 ` Peter Xu
2023-02-13 14:58 ` Darren Kenny
2023-02-22 14:13 ` Stefan Hajnoczi
2023-03-01 20:55 ` Michael S. Tsirkin
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=20230213152618-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alxndr@bu.edu \
--cc=berrange@redhat.com \
--cc=bin.meng@windriver.com \
--cc=bsd@redhat.com \
--cc=coc.cyqh@gmail.com \
--cc=darren.kenny@oracle.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=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 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).