From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Li, Chunming" <Chunming.Li@verisilicon.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>
Cc: "Wen, Jianxian" <Jianxian.Wen@verisilicon.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"Liu, Renwei" <Renwei.Liu@verisilicon.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] hw/arm/smmuv3: Support non-PCI/PCIe devices connection
Date: Fri, 20 Aug 2021 09:33:08 +0200 [thread overview]
Message-ID: <b212add7-f36b-98ce-ccf5-c5209afea3b6@redhat.com> (raw)
In-Reply-To: <49C79B700B5D8F45B8EF0861B4EF3B3B01142F5748@SHASXM03.verisilicon.com>
On 8/20/21 4:36 AM, Li, Chunming wrote:
> The current SMMU V3 device model only support PCI/PCIe devices,
> so we update it to support non-PCI/PCIe devices.
>
> hw/arm/smmuv3:
> . Create IOMMU memory regions for non-PCI/PCIe devices based on their SID
> . Add sid-map property to store non-PCI/PCIe devices SID
> . Update implementation of CFGI commands based on device SID
> hw/arm/smmu-common:
> . Differentiate PCI/PCIe and non-PCI/PCIe devices SID getting strategy
> hw/arm/virt:
> . Add PL330 DMA controller and connect with SMMUv3 for testing
> . Add smmuv3_sidmap for non-PCI/PCIe devices SID setting
>
> Signed-off-by: Chunming Li <chunming.li@verisilicon.com>
> Signed-off-by: Renwei Liu <renwei.liu@verisilicon.com>
> ---
> This patch depends on PL330 memory region connection patch:
> https://patchew.org/QEMU/4C23C17B8E87E74E906A25A3254A03F4FA1FEC31@SHASXM03.verisilicon.com/
>
> hw/arm/smmuv3.c | 75 ++++++++++++++++++------
> hw/arm/virt.c | 110 ++++++++++++++++++++++++++++++++++-
> include/hw/arm/smmu-common.h | 12 +++-
> include/hw/arm/smmuv3.h | 2 +
> include/hw/arm/virt.h | 3 +
> 5 files changed, 181 insertions(+), 21 deletions(-)
>
> diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c
> index 01b60bee4..c4da05d8b 100644
> --- a/hw/arm/smmuv3.c
> +++ b/hw/arm/smmuv3.c
> @@ -32,6 +32,7 @@
> #include "hw/arm/smmuv3.h"
> #include "smmuv3-internal.h"
> #include "smmu-internal.h"
> +#include "hw/qdev-properties.h"
>
> /**
> * smmuv3_trigger_irq - pulse @irq if enabled and update
> @@ -612,7 +613,7 @@ static SMMUTransCfg *smmuv3_get_config(SMMUDevice *sdev, SMMUEventInfo *event)
> return cfg;
> }
>
> -static void smmuv3_flush_config(SMMUDevice *sdev)
> +static void __attribute__((unused)) smmuv3_flush_config(SMMUDevice *sdev)
> {
Why keep this function if unused?
next prev parent reply other threads:[~2021-08-20 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 2:36 [PATCH] hw/arm/smmuv3: Support non-PCI/PCIe devices connection Li, Chunming
2021-08-20 7:33 ` Philippe Mathieu-Daudé [this message]
2021-08-20 7:42 ` Li, Chunming
2021-08-20 7:57 ` Philippe Mathieu-Daudé
2021-08-20 8:52 ` Peter Maydell
2021-08-20 9:04 ` Li, Chunming
2021-08-20 9:15 ` Peter Maydell
2021-08-24 8:21 ` Li, Chunming
2021-08-26 15:57 ` Peter Maydell
2021-08-27 0:22 ` Li, Chunming
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=b212add7-f36b-98ce-ccf5-c5209afea3b6@redhat.com \
--to=philmd@redhat.com \
--cc=Chunming.Li@verisilicon.com \
--cc=Jianxian.Wen@verisilicon.com \
--cc=Renwei.Liu@verisilicon.com \
--cc=eric.auger@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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 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).