From: Mark Rutland <mark.rutland@arm.com>
To: Jordan Crouse <jcrouse@codeaurora.org>
Cc: freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 6/6] drm/msm: a5xx: Support per-instance pagetables
Date: Tue, 7 Mar 2017 18:14:32 +0000 [thread overview]
Message-ID: <20170307181432.GG3514@leverpostej> (raw)
In-Reply-To: <1488906860-11073-7-git-send-email-jcrouse@codeaurora.org>
On Tue, Mar 07, 2017 at 10:14:20AM -0700, Jordan Crouse wrote:
> Support per-instance pagetables for 5XX targets. Per-instance
> pagetables allow each open DRM instance to have its own VM memory
> space to prevent accidently or maliciously copying or overwriting
> buffers from other instances. It also opens the door for SVM since
> any given CPU side address can be more reliably mapped into the
> instance's GPU VM space without conflict.
>
> To support this create a new dynamic domain (pagetable) for each open
> DRM file and map buffer objects for each instance into that pagetable.
> Use the GPU to switch to the pagetable for the instance while doing a
> submit.
>
> Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
> ---
> arch/arm64/boot/dts/qcom/msm8996.dtsi | 2 +
> drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 64 ++++++++++++++++++++++++++++++-
> drivers/gpu/drm/msm/adreno/a5xx_gpu.h | 17 ++++++++
> drivers/gpu/drm/msm/adreno/a5xx_preempt.c | 61 +++++++++++++++++++++++------
> drivers/gpu/drm/msm/adreno/adreno_gpu.h | 2 +
> drivers/gpu/drm/msm/msm_drv.c | 60 ++++++++++++++++++++++-------
> drivers/gpu/drm/msm/msm_drv.h | 3 ++
> drivers/gpu/drm/msm/msm_gem_vma.c | 38 +++++++++++++++---
> 8 files changed, 216 insertions(+), 31 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi
> index 2903020..6372f3a 100644
> --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi
> @@ -867,7 +867,9 @@
>
> qcom,skip-init;
> qcom,register-save;
> +
Pointless whitespace change?
> arm,smmu-enable-stall;
> + qcom,dynamic;
As commented on the RFC series adding code for this property, it is at
best not clear what this means, and at present I do not beleive this
should be in the DT at all.
Thanks,
Mark.
next prev parent reply other threads:[~2017-03-07 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 17:14 [PATCH 0/6] drm/msm: Add per-instance pagetables Jordan Crouse
2017-03-07 17:14 ` [PATCH 1/6] drm/msm: Enable 64 bit mode by default Jordan Crouse
[not found] ` <1488906860-11073-1-git-send-email-jcrouse-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-03-07 17:14 ` [PATCH 2/6] drm/msm: Pass the MMU domain index in struct msm_file_private Jordan Crouse
2017-03-07 17:14 ` [PATCH 3/6] drm/msm: Make separate iommu function tables for v1 and v2 MMUs Jordan Crouse
2017-03-07 17:14 ` [PATCH 4/6] drm/msm: Use TTBR1 for kernel side GPU buffer objects Jordan Crouse
2017-03-07 17:14 ` [PATCH 5/6] drm/msm: Support dynamic IOMMU domains Jordan Crouse
2017-03-07 17:14 ` [PATCH 6/6] drm/msm: a5xx: Support per-instance pagetables Jordan Crouse
2017-03-07 18:14 ` Mark Rutland [this message]
2017-03-07 21:53 ` [PATCH 0/6] drm/msm: Add " Daniel Vetter
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=20170307181432.GG3514@leverpostej \
--to=mark.rutland@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.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