From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Mark up obj->mm.lock for shrinker
Date: Tue, 01 Nov 2016 11:19:22 +0200 [thread overview]
Message-ID: <1477991962.3103.8.camel@linux.intel.com> (raw)
In-Reply-To: <20161101091528.GM30109@nuc-i3427.alporthouse.com>
On ti, 2016-11-01 at 09:15 +0000, Chris Wilson wrote:
> On Tue, Nov 01, 2016 at 11:10:31AM +0200, Joonas Lahtinen wrote:
> >
> > On ma, 2016-10-31 at 12:40 +0000, Chris Wilson wrote:
> > As discussed in IRC, I think we rather should add a lock class to
> > obj->mm, to avoid chasing these in the future.
>
> All ears :) The complicated one isn't obj->mm, but the timeline->lock.
> That we may do engine1->tl->lock, engine2->tl->lock, request->tl->lock,
> so far.
Just realized we would have to properly reboot the kernel after each
test not to run out of locking classes...
For timeline->lock, the same thing. Just assign each timeline its own
lock class. But no bonus until we reboot enough.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-11-01 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 12:40 [PATCH] drm/i915: Mark up obj->mm.lock for shrinker Chris Wilson
2016-10-31 13:01 ` Tvrtko Ursulin
2016-10-31 13:32 ` Chris Wilson
2016-10-31 13:16 ` ✗ Fi.CI.BAT: warning for " Patchwork
2016-11-01 9:10 ` [PATCH] " Joonas Lahtinen
2016-11-01 9:15 ` Chris Wilson
2016-11-01 9:19 ` Joonas Lahtinen [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=1477991962.3103.8.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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 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.