From: "Christian König" <christian.koenig@amd.com>
To: xinhui pan <xinhui.pan@amd.com>, amd-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/ttm: Double check mem_type of BO while eviction
Date: Wed, 10 Nov 2021 08:42:21 +0100 [thread overview]
Message-ID: <6c8a5217-0bbd-1d1d-2204-2f86885ec27b@amd.com> (raw)
In-Reply-To: <20211110043149.57554-2-xinhui.pan@amd.com>
Am 10.11.21 um 05:31 schrieb xinhui pan:
> BO might sit in a wrong lru list as there is a small period of memory
> moving and lru list updating.
>
> Lets skip eviction if we hit such mismatch.
>
> Suggested-by: Christian König <christian.koenig@amd.com>
> Signed-off-by: xinhui pan <xinhui.pan@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com> for the series.
Going to add a CC: stable to the second patch and push it to drm-misc-fixes.
Thanks,
Christian.
> ---
> drivers/gpu/drm/ttm/ttm_bo.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index e307004f0b28..0137a302f261 100644
> --- a/drivers/gpu/drm/ttm/ttm_bo.c
> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> @@ -594,7 +594,8 @@ static bool ttm_bo_evict_swapout_allowable(struct ttm_buffer_object *bo,
> *busy = !ret;
> }
>
> - if (ret && place && !bo->bdev->funcs->eviction_valuable(bo, place)) {
> + if (ret && place && (bo->resource->mem_type != place->mem_type ||
> + !bo->bdev->funcs->eviction_valuable(bo, place))) {
> ret = false;
> if (*locked) {
> dma_resv_unlock(bo->base.resv);
prev parent reply other threads:[~2021-11-10 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 4:31 [PATCH 1/2] drm/ttm: Put BO in its memory manager's lru list xinhui pan
2021-11-10 4:31 ` [PATCH 2/2] drm/ttm: Double check mem_type of BO while eviction xinhui pan
2021-11-10 7:42 ` Christian König [this message]
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=6c8a5217-0bbd-1d1d-2204-2f86885ec27b@amd.com \
--to=christian.koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=xinhui.pan@amd.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