From: Jordan Crouse <jcrouse@codeaurora.org>
To: Akhil P Oommen <akhilpo@codeaurora.org>
Cc: freedreno@lists.freedesktop.org, dri-devel@freedesktop.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
mka@chromium.org, jonathan@marek.ca, robdclark@gmail.com,
dianders@chromium.org
Subject: Re: [PATCH v2 2/2] drm/msm: Leave inuse count intact on map failure
Date: Wed, 23 Sep 2020 08:51:47 -0600 [thread overview]
Message-ID: <20200923145146.GC31425@jcrouse1-lnx.qualcomm.com> (raw)
In-Reply-To: <1600786527-7343-2-git-send-email-akhilpo@codeaurora.org>
On Tue, Sep 22, 2020 at 08:25:27PM +0530, Akhil P Oommen wrote:
> Leave the inuse count intact on map failure to keep the accounting
> accurate.
>
> Signed-off-by: Akhil P Oommen <akhilpo@codeaurora.org>
Reviewed-by: Jordan Crouse <jcrouse@codeaurora.org>
> ---
> drivers/gpu/drm/msm/msm_gem_vma.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/msm_gem_vma.c b/drivers/gpu/drm/msm/msm_gem_vma.c
> index 80a8a26..f914ddb 100644
> --- a/drivers/gpu/drm/msm/msm_gem_vma.c
> +++ b/drivers/gpu/drm/msm/msm_gem_vma.c
> @@ -88,8 +88,10 @@ msm_gem_map_vma(struct msm_gem_address_space *aspace,
> ret = aspace->mmu->funcs->map(aspace->mmu, vma->iova, sgt,
> size, prot);
>
> - if (ret)
> + if (ret) {
> vma->mapped = false;
> + vma->inuse--;
> + }
>
> return ret;
> }
> --
> 2.7.4
>
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-09-23 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 14:55 [PATCH v2 1/2] drm/msm: Fix premature purging of BO Akhil P Oommen
2020-09-22 14:55 ` [PATCH v2 2/2] drm/msm: Leave inuse count intact on map failure Akhil P Oommen
2020-09-23 14:51 ` Jordan Crouse [this message]
2020-09-23 14:50 ` [PATCH v2 1/2] drm/msm: Fix premature purging of BO Jordan Crouse
2020-09-23 18:28 ` Akhil P Oommen
2020-09-24 2:29 ` Rob Clark
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=20200923145146.GC31425@jcrouse1-lnx.qualcomm.com \
--to=jcrouse@codeaurora.org \
--cc=akhilpo@codeaurora.org \
--cc=dianders@chromium.org \
--cc=dri-devel@freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=robdclark@gmail.com \
/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