From: Will Deacon <will@kernel.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>, joro@8bytes.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
robh+dt@kernel.org, linux-acpi@vger.kernel.org,
sudeep.holla@arm.com, robin.murphy@arm.com, guohanjun@huawei.com,
devicetree@vger.kernel.org, iommu@lists.linux-foundation.org,
zhangfei.gao@linaro.org, wangzhou1@hisilicon.com,
Jonathan.Cameron@huawei.com, lorenzo.pieralisi@arm.com,
linux-arm-kernel@lists.infradead.org, eric.auger@redhat.com,
rjw@rjwysocki.net, lenb@kernel.org
Subject: Re: [PATCH v15 0/3] iommu/arm-smmu-v3: Add stall support
Date: Tue, 8 Jun 2021 12:42:34 +0100 [thread overview]
Message-ID: <162314710744.3707892.6632600736379822229.b4-ty@kernel.org> (raw)
In-Reply-To: <20210526161927.24268-1-jean-philippe@linaro.org>
On Wed, 26 May 2021 18:19:25 +0200, Jean-Philippe Brucker wrote:
> Add stall support for SMMUv3, enabling I/O page faults and SVA for
> compatible devices. No change since last version [1], but I'd still like
> this to be considered for upstream, because there exists hardware and
> applications.
>
> Stall is implemented by the Kunpeng 920 processor for its compression
> and crypto accelerators, with which I tested the SVA infrastructure.
> Using the userspace accelerator API [2], a program can obtain a queue
> from one of these devices and submit compression or encryption work
> within the program's address space. UADK [3] provides a library to do
> this, and there is an openssl plugin [4] to use it.
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/3] dt-bindings: document stall property for IOMMU masters
https://git.kernel.org/will/c/ed1d08b9d0c9
[2/3] ACPI/IORT: Enable stall support for platform devices
https://git.kernel.org/will/c/6522b1e0c78f
[3/3] iommu/arm-smmu-v3: Add stall support for platform devices
https://git.kernel.org/will/c/395ad89d11fd
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-08 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 16:19 [PATCH v15 0/3] iommu/arm-smmu-v3: Add stall support Jean-Philippe Brucker
2021-05-26 16:19 ` [PATCH v15 1/3] dt-bindings: document stall property for IOMMU masters Jean-Philippe Brucker
2021-05-26 16:19 ` [PATCH v15 2/3] ACPI/IORT: Enable stall support for platform devices Jean-Philippe Brucker
2021-05-26 16:19 ` [PATCH v15 3/3] iommu/arm-smmu-v3: Add " Jean-Philippe Brucker
2021-06-08 11:42 ` Will Deacon [this message]
2021-06-09 9:43 ` [PATCH v15 0/3] iommu/arm-smmu-v3: Add stall support Jean-Philippe Brucker
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=162314710744.3707892.6632600736379822229.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric.auger@redhat.com \
--cc=guohanjun@huawei.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.com \
--cc=wangzhou1@hisilicon.com \
--cc=zhangfei.gao@linaro.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