All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Tomeu Vizoso <tomeu@tomeuvizoso.net>,
	Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
	stable@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 8/8] drm/panfrost: Make sure the shrinker does not reclaim referenced BOs
Date: Fri, 29 Nov 2019 17:07:34 +0100	[thread overview]
Message-ID: <20191129170734.50bb02ad@collabora.com> (raw)
In-Reply-To: <64a6a09a-e83a-05be-8576-79a74f971286@arm.com>

On Fri, 29 Nov 2019 15:48:15 +0000
Steven Price <steven.price@arm.com> wrote:

> On 29/11/2019 13:59, Boris Brezillon wrote:
> > Userspace might tag a BO purgeable while it's still referenced by GPU
> > jobs. We need to make sure the shrinker does not purge such BOs until
> > all jobs referencing it are finished.
> > 
> > Fixes: 013b65101315 ("drm/panfrost: Add madvise and shrinker support")
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>  
> 
> I'm happy with this, but I would also argue that it was previously user
> space's job not to mark a BO purgeable while it's in use by the GPU.

I was not aware of this design choice.

> This is in some ways an ABI change so we should be sure this is
> something that we want to support "forever" more.

Well, in that case, the ABI change is bringing extra robustness, with
AFAICT, no downside for those that were taking care of that in
userspace.

> But if Mesa has
> 'always' been assuming this behaviour we might as well match.

I think so, and VC4 seems to have the same expectations.

> 
> Reviewed-by: Steven Price <steven.price@arm.com>

Thanks for the review.

WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: stable@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Rob Herring <robh+dt@kernel.org>,
	Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Subject: Re: [PATCH 8/8] drm/panfrost: Make sure the shrinker does not reclaim referenced BOs
Date: Fri, 29 Nov 2019 17:07:34 +0100	[thread overview]
Message-ID: <20191129170734.50bb02ad@collabora.com> (raw)
Message-ID: <20191129160734.8pWIHU-bCnh0bikYjMOE5j7gQRzakQynMEHPtCEqdmI@z> (raw)
In-Reply-To: <64a6a09a-e83a-05be-8576-79a74f971286@arm.com>

On Fri, 29 Nov 2019 15:48:15 +0000
Steven Price <steven.price@arm.com> wrote:

> On 29/11/2019 13:59, Boris Brezillon wrote:
> > Userspace might tag a BO purgeable while it's still referenced by GPU
> > jobs. We need to make sure the shrinker does not purge such BOs until
> > all jobs referencing it are finished.
> > 
> > Fixes: 013b65101315 ("drm/panfrost: Add madvise and shrinker support")
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>  
> 
> I'm happy with this, but I would also argue that it was previously user
> space's job not to mark a BO purgeable while it's in use by the GPU.

I was not aware of this design choice.

> This is in some ways an ABI change so we should be sure this is
> something that we want to support "forever" more.

Well, in that case, the ABI change is bringing extra robustness, with
AFAICT, no downside for those that were taking care of that in
userspace.

> But if Mesa has
> 'always' been assuming this behaviour we might as well match.

I think so, and VC4 seems to have the same expectations.

> 
> Reviewed-by: Steven Price <steven.price@arm.com>

Thanks for the review.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-11-29 16:07 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 13:59 [PATCH 0/8] panfrost: Fixes for 5.4 Boris Brezillon
2019-11-29 13:59 ` [PATCH 1/8] drm/panfrost: Make panfrost_job_run() return an ERR_PTR() instead of NULL Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 14:19   ` Steven Price
2019-11-29 14:19     ` Steven Price
2019-11-29 14:31     ` Boris Brezillon
2019-11-29 14:31       ` Boris Brezillon
2019-11-29 14:38       ` Steven Price
2019-11-29 14:38         ` Steven Price
2019-11-29 19:32         ` Boris Brezillon
2019-11-29 19:32           ` Boris Brezillon
2019-11-29 13:59 ` [PATCH 2/8] drm/panfrost: Fix a race in panfrost_ioctl_madvise() Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 14:24   ` Steven Price
2019-11-29 14:24     ` Steven Price
2019-11-29 14:33     ` Boris Brezillon
2019-11-29 14:33       ` Boris Brezillon
2019-11-29 14:40       ` Steven Price
2019-11-29 14:40         ` Steven Price
2019-11-29 20:07         ` Daniel Vetter
2019-11-29 20:07           ` Daniel Vetter
2019-11-29 21:45           ` Boris Brezillon
2019-11-29 21:45             ` Boris Brezillon
2019-12-05 23:08       ` Rob Herring
2019-12-05 23:08         ` Rob Herring
2019-12-06  7:53         ` Boris Brezillon
2019-12-06  7:53           ` Boris Brezillon
2019-12-06  8:08           ` Boris Brezillon
2019-12-06  8:08             ` Boris Brezillon
2019-11-29 13:59 ` [PATCH 3/8] drm/panfrost: Fix a BO leak in panfrost_ioctl_mmap_bo() Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 14:26   ` Steven Price
2019-11-29 14:26     ` Steven Price
2019-11-29 13:59 ` [PATCH 4/8] drm/panfrost: Fix a race in panfrost_gem_free_object() Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 14:28   ` Steven Price
2019-11-29 14:28     ` Steven Price
2019-11-29 13:59 ` [PATCH 5/8] drm/panfrost: Open/close the perfcnt BO Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 14:34   ` Steven Price
2019-11-29 14:34     ` Steven Price
2019-11-29 13:59 ` [PATCH 6/8] drm/panfrost: Make sure imported/exported BOs are never purged Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 14:14   ` Boris Brezillon
2019-11-29 14:14     ` Boris Brezillon
2019-11-29 14:45   ` Steven Price
2019-11-29 14:45     ` Steven Price
2019-11-29 14:52     ` Boris Brezillon
2019-11-29 14:52       ` Boris Brezillon
2019-11-29 20:12   ` Daniel Vetter
2019-11-29 20:12     ` Daniel Vetter
2019-11-29 21:09     ` Boris Brezillon
2019-11-29 21:09       ` Boris Brezillon
2019-12-02  8:52       ` Daniel Vetter
2019-12-02  8:52         ` Daniel Vetter
2019-12-02  9:50         ` Boris Brezillon
2019-12-02  9:50           ` Boris Brezillon
2019-11-29 13:59 ` [PATCH 7/8] drm/panfrost: Add the panfrost_gem_mapping concept Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 15:37   ` Steven Price
2019-11-29 15:37     ` Steven Price
2019-11-29 20:14   ` Daniel Vetter
2019-11-29 20:14     ` Daniel Vetter
2019-11-29 21:36     ` Boris Brezillon
2019-11-29 21:36       ` Boris Brezillon
2019-12-02  8:55       ` Daniel Vetter
2019-12-02  8:55         ` Daniel Vetter
2019-12-02  9:13         ` Boris Brezillon
2019-12-02  9:13           ` Boris Brezillon
2019-12-02  9:44           ` Daniel Vetter
2019-12-02  9:44             ` Daniel Vetter
2019-12-04 11:41             ` Steven Price
2019-12-04 11:41               ` Steven Price
2019-11-29 13:59 ` [PATCH 8/8] drm/panfrost: Make sure the shrinker does not reclaim referenced BOs Boris Brezillon
2019-11-29 13:59   ` Boris Brezillon
2019-11-29 15:48   ` Steven Price
2019-11-29 15:48     ` Steven Price
2019-11-29 16:07     ` Boris Brezillon [this message]
2019-11-29 16:07       ` Boris Brezillon
2019-11-29 16:12       ` Steven Price
2019-11-29 16:12         ` Steven Price
2019-12-02 12:50   ` Robin Murphy
2019-12-02 12:50     ` Robin Murphy
2019-12-02 13:32     ` Boris Brezillon
2019-12-02 13:32       ` Boris Brezillon
2019-11-29 14:23 ` [PATCH 0/8] panfrost: Fixes for 5.4 Alyssa Rosenzweig
2019-12-06 17:16 ` Rob Herring

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=20191129170734.50bb02ad@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=alyssa.rosenzweig@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh+dt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=steven.price@arm.com \
    --cc=tomeu@tomeuvizoso.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.