[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220621151022.1416300-1-cyndis@kapsi.fi>
Date: Tue, 21 Jun 2022 18:10:12 +0300
From: Mikko Perttunen <cyndis@...si.fi>
To: thierry.reding@...il.com, jonathanh@...dia.com, joro@...tes.org,
will@...nel.org, robin.murphy@....com, robh+dt@...nel.org,
krzysztof.kozlowski@...onical.com
Cc: linux-tegra@...r.kernel.org, dri-devel@...ts.freedesktop.org,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Mikko Perttunen <mperttunen@...dia.com>
Subject: [PATCH v6 00/10] Host1x context isolation support
From: Mikko Perttunen <mperttunen@...dia.com>
-------------
Merging notes
-------------
The changes to DT bindings should be applied on top of Thierry's patch
'dt-bindings: display: tegra: Convert to json-schema'.
The change to the arm-smmu driver should be omitted if Robin Murphy's
IOMMU bus cleanup series is merged.
***
New in v6:
Rebased on 5.19-rc3 (-next is too broken)
Added patch to fix TRANSCFG offset on NVDEC.
***
***
New in v5:
Rebased
Renamed host1x_context to host1x_memory_context
Small change in DRM side client driver ops to reduce churn with some
upcoming changes
Add NVDEC support
***
***
New in v4:
Addressed review comments. See individual patches.
***
***
New in v3:
Added device tree bindings for new property.
***
***
New in v2:
Added support for Tegra194
Use standard iommu-map property instead of custom mechanism
***
This series adds support for Host1x 'context isolation'. Since
when programming engines through Host1x, userspace can program in
any addresses it wants, we need some way to isolate the engines'
memory spaces. Traditionally this has either been done imperfectly
with a single shared IOMMU domain, or by copying and verifying the
programming command stream at submit time (Host1x firewall).
Since Tegra186 there is a privileged (only usable by kernel)
Host1x opcode that allows setting the stream ID sent by the engine
to the SMMU. So, by allocating a number of context banks and stream
IDs for this purpose, and using this opcode at the beginning of
each job, we can implement isolation. Due to the limited number of
context banks only each process gets its own context, and not
each channel.
This feature also allows sharing engines among multiple VMs when
used with Host1x's hardware virtualization support - up to 8 VMs
can be configured with a subset of allowed stream IDs, enforced
at hardware level.
To implement this, this series adds a new host1x context bus, which
will contain the 'struct device's corresponding to each context
bank / stream ID, changes to device tree and SMMU code to allow
registering the devices and using the bus, as well as the Host1x
stream ID programming code and support in TegraDRM.
Thanks,
Mikko
Mikko Perttunen (9):
iommu/arm-smmu: Attach to host1x context device bus
dt-bindings: host1x: Add iommu-map property
gpu: host1x: Add context device management code
gpu: host1x: Program context stream ID on submission
arm64: tegra: Add Host1x context stream IDs on Tegra186+
drm/tegra: falcon: Set DMACTX field on DMA transactions
drm/tegra: nvdec: Fix TRANSCFG register offset
drm/tegra: Support context isolation
drm/tegra: Implement stream ID related callbacks on engines
Thierry Reding (1):
dt-bindings: display: tegra: Convert to json-schema
.../display/tegra/nvidia,tegra114-mipi.txt | 41 --
.../display/tegra/nvidia,tegra114-mipi.yaml | 74 ++
.../display/tegra/nvidia,tegra124-dpaux.yaml | 149 ++++
.../display/tegra/nvidia,tegra124-sor.yaml | 206 ++++++
.../display/tegra/nvidia,tegra124-vic.yaml | 71 ++
.../display/tegra/nvidia,tegra186-dc.yaml | 85 +++
.../tegra/nvidia,tegra186-display.yaml | 310 ++++++++
.../tegra/nvidia,tegra186-dsi-padctl.yaml | 45 ++
.../display/tegra/nvidia,tegra20-dc.yaml | 181 +++++
.../display/tegra/nvidia,tegra20-dsi.yaml | 159 +++++
.../display/tegra/nvidia,tegra20-epp.yaml | 70 ++
.../display/tegra/nvidia,tegra20-gr2d.yaml | 73 ++
.../display/tegra/nvidia,tegra20-gr3d.yaml | 214 ++++++
.../display/tegra/nvidia,tegra20-hdmi.yaml | 126 ++++
.../display/tegra/nvidia,tegra20-host1x.txt | 675 ------------------
.../display/tegra/nvidia,tegra20-host1x.yaml | 352 +++++++++
.../display/tegra/nvidia,tegra20-isp.yaml | 67 ++
.../display/tegra/nvidia,tegra20-mpe.yaml | 73 ++
.../display/tegra/nvidia,tegra20-tvo.yaml | 58 ++
.../display/tegra/nvidia,tegra20-vi.yaml | 163 +++++
.../display/tegra/nvidia,tegra210-csi.yaml | 52 ++
.../pinctrl/nvidia,tegra124-dpaux-padctl.txt | 59 --
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 11 +
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 11 +
drivers/gpu/drm/tegra/drm.h | 11 +
drivers/gpu/drm/tegra/falcon.c | 8 +
drivers/gpu/drm/tegra/falcon.h | 1 +
drivers/gpu/drm/tegra/nvdec.c | 13 +-
drivers/gpu/drm/tegra/submit.c | 48 +-
drivers/gpu/drm/tegra/uapi.c | 43 +-
drivers/gpu/drm/tegra/vic.c | 67 +-
drivers/gpu/host1x/Makefile | 1 +
drivers/gpu/host1x/context.c | 160 +++++
drivers/gpu/host1x/context.h | 27 +
drivers/gpu/host1x/dev.c | 12 +-
drivers/gpu/host1x/dev.h | 2 +
drivers/gpu/host1x/hw/channel_hw.c | 52 +-
drivers/gpu/host1x/hw/host1x06_hardware.h | 10 +
drivers/gpu/host1x/hw/host1x07_hardware.h | 10 +
drivers/iommu/arm/arm-smmu/arm-smmu.c | 13 +
include/linux/host1x.h | 26 +
41 files changed, 3037 insertions(+), 792 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.txt
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra124-dpaux.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra124-sor.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra124-vic.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra186-dc.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra186-display.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra186-dsi-padctl.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dc.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-dsi.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-epp.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-gr2d.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-gr3d.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-hdmi.yaml
delete mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.txt
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-host1x.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-isp.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-mpe.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-tvo.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra20-vi.yaml
create mode 100644 Documentation/devicetree/bindings/display/tegra/nvidia,tegra210-csi.yaml
delete mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-dpaux-padctl.txt
create mode 100644 drivers/gpu/host1x/context.c
create mode 100644 drivers/gpu/host1x/context.h
--
2.36.1
Powered by blists - more mailing lists