From: Alex Deucher <alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
Cc: amd-gfx list <amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH xf86-video-ati] glamor: Invalidate cached GEM handle in radeon_set_pixmap_bo
Date: Tue, 17 Jul 2018 11:43:25 -0400 [thread overview]
Message-ID: <CADnq5_PDTjV3bfNE4u23h6JTY+YOBjCtymLm_F3PdonbhB-PBQ@mail.gmail.com> (raw)
In-Reply-To: <20180717094346.14109-1-michel-otUistvHUpPR7s880joybQ@public.gmane.org>
On Tue, Jul 17, 2018 at 5:43 AM, Michel Dänzer <michel@daenzer.net> wrote:
> From: Michel Dänzer <michel.daenzer@amd.com>
>
> We continued using the stale cached handle, causing issues e.g. when
> resizing the screen via RandR.
>
> Reported-by: iive on IRC
> Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
Acked-by: Alex Deucher <alexander.deucher@amd.com>
> ---
> src/radeon.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/radeon.h b/src/radeon.h
> index 450c69aa8..1a1edb1ba 100644
> --- a/src/radeon.h
> +++ b/src/radeon.h
> @@ -735,6 +735,7 @@ static inline Bool radeon_set_pixmap_bo(PixmapPtr pPix, struct radeon_buffer *bo
> return TRUE;
>
> radeon_buffer_unref(&priv->bo);
> + priv->handle_valid = FALSE;
> }
>
> drmmode_fb_reference(pRADEONEnt->fd, &priv->fb, NULL);
> --
> 2.18.0
>
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-07-17 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 9:43 [PATCH xf86-video-ati] glamor: Invalidate cached GEM handle in radeon_set_pixmap_bo Michel Dänzer
[not found] ` <20180717094346.14109-1-michel-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-07-17 15:43 ` Alex Deucher [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=CADnq5_PDTjV3bfNE4u23h6JTY+YOBjCtymLm_F3PdonbhB-PBQ@mail.gmail.com \
--to=alexdeucher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=michel-otUistvHUpPR7s880joybQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).