From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
daniel.vetter@ffwll.ch, airlied@gmail.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/5] drm/vmwgfx: unbind in vmw_ttm_unpopulate
Date: Mon, 23 Aug 2021 13:15:20 +0200 [thread overview]
Message-ID: <3ad5188659ce362087db1980880ac47af60e639f.camel@linux.intel.com> (raw)
In-Reply-To: <eebf6fc4-c299-6aa7-f91c-16029c5c3444@gmail.com>
On Mon, 2021-08-23 at 13:05 +0200, Christian König wrote:
> Adding Thomas on CC as well.
>
> Just a gentle ping. I think the patch set makes sense now.
>
> Regards,
> Christian.
>
> Am 28.07.21 um 15:05 schrieb Christian König:
> > Doing this in vmw_ttm_destroy() is to late.
> >
> > It turned out that this is not a good idea at all because it leaves
> > pointers
> > to freed up system memory pages in the GART tables of the drivers.
> >
> > Signed-off-by: Christian König <christian.koenig@amd.com>
> > ---
> > drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c | 9 +++------
> > 1 file changed, 3 insertions(+), 6 deletions(-)
> >
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
next prev parent reply other threads:[~2021-08-23 11:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 13:05 [PATCH 1/5] drm/vmwgfx: unbind in vmw_ttm_unpopulate Christian König
2021-07-28 13:05 ` [PATCH 2/5] drm/amdgpu: unbind in amdgpu_ttm_tt_unpopulate Christian König
2021-07-28 13:05 ` [PATCH 3/5] drm/nouveau: unbind in nouveau_ttm_tt_unpopulate Christian König
2021-07-28 13:05 ` [PATCH 4/5] drm/radeon: unbind in radeon_ttm_tt_unpopulate() Christian König
2021-07-28 13:05 ` [PATCH 5/5] drm/ttm: remove ttm_tt_destroy_common v2 Christian König
2021-08-23 11:05 ` [PATCH 1/5] drm/vmwgfx: unbind in vmw_ttm_unpopulate Christian König
2021-08-23 11:15 ` Thomas Hellström [this message]
2021-08-26 8:49 ` Daniel Vetter
2021-08-26 10:11 ` Christian König
2021-08-26 12:50 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2021-07-22 12:41 Christian König
2021-07-23 8:47 ` Daniel Vetter
2021-07-23 9:13 ` Christian König
2021-07-23 9:21 ` Daniel Vetter
2021-07-23 9:40 ` Christian König
2021-07-26 0:03 ` Dave Airlie
2021-07-26 19:35 ` Christian König
2021-07-26 20:03 ` Dave Airlie
2021-07-27 9:28 ` Daniel Vetter
2021-07-28 11:18 ` Christian König
2021-07-22 8:55 Christian König
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=3ad5188659ce362087db1980880ac47af60e639f.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@gmail.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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).