From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Do uncore early sanitize after domain init
Date: Wed, 28 Jan 2015 14:46:52 +0200 [thread overview]
Message-ID: <87twzb843n.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20150128112929.GB25850@nuc-i3427.alporthouse.com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> On Wed, Jan 28, 2015 at 12:59:52PM +0200, Mika Kuoppala wrote:
>> Chris Wilson <chris@chris-wilson.co.uk> writes:
>> > Also, why are we not calling fw_domain_reset() from fw_domain_init()?
>> > That would be enough to avoid the early santize required for ivb,
>> > right?
>>
>> Agreed here. That was my plan originally, doing the sanitize inside
>> in domain inits. But I wanted to fix this particular item by trying to
>> be as close as possible to the previous init/forcewake ordering on all gens.
>>
>> Reasoning is that I would like to see this stabilize a short while
>> before introducing further changes. I burned my fingers already touching
>> these, so they need to heal :)
>>
>> Ok if this is for future work?
>
> The bug is in -next, so take advantage of the guinea pigs...
v2 in:
1422449006-4028-1-git-send-email-mika.kuoppala@intel.com
-Mika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-28 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 9:45 [PATCH] drm/i915: Do uncore early sanitize after domain init Mika Kuoppala
2015-01-28 10:17 ` Chris Wilson
2015-01-28 10:45 ` Chris Wilson
2015-01-28 10:59 ` Mika Kuoppala
2015-01-28 11:29 ` Chris Wilson
2015-01-28 12:46 ` Mika Kuoppala [this message]
2015-02-01 15:36 ` shuang.he
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=87twzb843n.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@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.