From: Daniel Vetter <daniel@ffwll.ch>
To: "Christian König" <christian.koenig@amd.com>
Cc: "Thomas Hellstrom" <thellstrom@vmware.com>,
"Michel Dänzer" <michel@daenzer.net>,
"Sinclair Yeh" <syeh@vmware.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/ttm: Make sure BOs being swapped out are cacheable
Date: Fri, 27 Jan 2017 15:12:49 +0100 [thread overview]
Message-ID: <20170127141249.4tft6eajtw35pcho@phenom.ffwll.local> (raw)
In-Reply-To: <5e8d77b2-8b71-6542-4ef5-c7a5d16f2455@amd.com>
On Fri, Jan 27, 2017 at 09:22:47AM +0100, Christian König wrote:
> Am 27.01.2017 um 08:30 schrieb Daniel Vetter:
> > On Fri, Jan 27, 2017 at 07:23:58AM +0100, Thomas Hellstrom wrote:
> > > On 01/27/2017 03:29 AM, Michel Dänzer wrote:
> > > > On 26/01/17 09:46 AM, Sinclair Yeh wrote:
> > > > > On Wed, Jan 25, 2017 at 10:49:33AM +0100, Christian König wrote:
> > > > > > Am 25.01.2017 um 10:25 schrieb Thomas Hellstrom:
> > > > > > > On 01/25/2017 09:21 AM, Michel Dänzer wrote:
> > > > > > > > From: Michel Dänzer <michel.daenzer@amd.com>
> > > > > > > >
> > > > > > > > The current caching state may not be tt_cached, even though the
> > > > > > > > placement contains TTM_PL_FLAG_CACHED, because placement can contain
> > > > > > > > multiple caching flags. Trying to swap out such a BO would trip up the
> > > > > > > >
> > > > > > > > BUG_ON(ttm->caching_state != tt_cached);
> > > > > > > >
> > > > > > > > in ttm_tt_swapout.
> > > > > > > >
> > > > > > > > Cc: stable@vger.kernel.org
> > > > > > > > Signed-off-by: Michel Dänzer <michel.daenzer@amd.com>
> > > > > > > Reviewed-by: Thomas Hellstrom <thellstrom@vmware.com>
> > > > > > Reviewed-by: Christian König <christian.koenig@amd.com>.
> > > > > Reviewed-by: Sinclair Yeh <syeh@vmware.com>
> > > > Thanks for the reviews! Via which tree should we merge this?
> > > >
> > > >
> > > I don't maintain a TTM tree any longer. Let's check with Daniel if he
> > > can merge it through drm-misc.
> > I'm trying very hard not to get volunteered for ttm maintainer :-)
>
> Yeah, ok I volunteer. Wanted to take that over for a while anyway.
I guess you didn't use the dim magic to push it? The test integration tree
isn't rebuild ... Quickstart for the tooling:
https://01.org/linuxgraphics/gfx-docs/maintainer-tools/dim.html
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2017-01-27 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 8:21 Michel Dänzer
2017-01-25 9:25 ` Thomas Hellstrom
2017-01-25 9:49 ` Christian König
2017-01-26 0:46 ` Sinclair Yeh
2017-01-27 2:29 ` Michel Dänzer
2017-01-27 6:23 ` Thomas Hellstrom
2017-01-27 7:30 ` Daniel Vetter
2017-01-27 8:22 ` Christian König
2017-01-27 14:12 ` Daniel Vetter [this message]
2017-01-27 14:43 ` Christian König
2017-01-27 14:52 ` Daniel Vetter
2017-01-27 15:03 ` Alex Deucher
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=20170127141249.4tft6eajtw35pcho@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=syeh@vmware.com \
--cc=thellstrom@vmware.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
all inboxes | Powered by JetHome®