From: Greg KH <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: stable@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
Danilo Krummrich <dakr@redhat.com>
Subject: Re: [PATCH 6.6.y] nouveau: set placement to original placement on uvmm validate.
Date: Mon, 12 Aug 2024 16:37:04 +0200 [thread overview]
Message-ID: <2024081257-smile-moonshine-d6a5@gregkh> (raw)
In-Reply-To: <20240807160341.2476-2-dakr@kernel.org>
On Wed, Aug 07, 2024 at 06:03:42PM +0200, Danilo Krummrich wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> When a buffer is evicted for memory pressure or TTM evict all,
> the placement is set to the eviction domain, this means the
> buffer never gets revalidated on the next exec to the correct domain.
>
> I think this should be fine to use the initial domain from the
> object creation, as least with VM_BIND this won't change after
> init so this should be the correct answer.
>
> Fixes: b88baab82871 ("drm/nouveau: implement new VM_BIND uAPI")
> Cc: Danilo Krummrich <dakr@redhat.com>
> Cc: <stable@vger.kernel.org> # v6.6
> Signed-off-by: Dave Airlie <airlied@redhat.com>
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> Link: https://patchwork.freedesktop.org/patch/msgid/20240515025542.2156774-1-airlied@gmail.com
> (cherry picked from commit 9c685f61722d30a22d55bb8a48f7a48bb2e19bcc)
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
> ---
> drivers/gpu/drm/nouveau/nouveau_uvmm.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-08-12 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 14:10 FAILED: patch "[PATCH] nouveau: set placement to original placement on uvmm" failed to apply to 6.6-stable tree gregkh
2024-08-07 16:03 ` [PATCH 6.6.y] nouveau: set placement to original placement on uvmm validate Danilo Krummrich
2024-08-12 14:37 ` Greg KH [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=2024081257-smile-moonshine-d6a5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@redhat.com \
--cc=dakr@kernel.org \
--cc=dakr@redhat.com \
--cc=stable@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 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.