From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Eric Auger <eric.auger@redhat.com>
Subject: can QEMU's arm smmu model handle non-PCI devices?
Date: Mon, 23 May 2022 15:52:00 +0100 [thread overview]
Message-ID: <CAFEAcA-NnZQ+4hoScoZMjOyta9EWv_LusXeZ5HRv4kXSqZjD0w@mail.gmail.com> (raw)
Hi; in real hardware an SMMUv3 might be sat in front of any
DMA-capable device. Putting one in front of a PCI bus is common
but not the only use case. Does QEMU's SMMUv3 model handle that,
or is the implementation currently restricted to only handling DMA
from PCI devices?
I ask because for the Realm Management Extension (aka Confidential
Compute Architecture) we're going to need to put SMMUs in front of
other devices (such as the GIC), so that their DMA is checked against
the RME Granule Protection Tables. So if we don't currently handle
non-PCI devices then that's a bit of extra preliminary work that we'll
want to do :-)
thanks
-- PMM
next reply other threads:[~2022-05-23 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 14:52 Peter Maydell [this message]
2022-05-23 19:40 ` can QEMU's arm smmu model handle non-PCI devices? Eric Auger
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=CAFEAcA-NnZQ+4hoScoZMjOyta9EWv_LusXeZ5HRv4kXSqZjD0w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eric.auger@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.