public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org,
	Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH 2/4] drm/i915: Convert sandybridge_pcode_*() to use intel_wait_for_register()
Date: Thu, 30 Jun 2016 14:39:25 +0100	[thread overview]
Message-ID: <5775210D.1070000@linux.intel.com> (raw)
In-Reply-To: <20160630131930.GZ28577@nuc-i3427.alporthouse.com>


On 30/06/16 14:19, Chris Wilson wrote:
> On Thu, Jun 30, 2016 at 02:04:43PM +0100, Tvrtko Ursulin wrote:
>>
>> On 30/06/16 12:30, Chris Wilson wrote:
>>> +	if (intel_wait_for_register(dev_priv,
>>> +				    GEN6_PCODE_MAILBOX, GEN6_PCODE_READY, 0,
>>> +				    500)) {
>>
>> Why not the _fw version?
>
> No reason, just added the read half of this patch after doing the mass
> conversion so I had intel_wait_for_register() on my fingers.

Will you make it consistent then? R-b if you do. :)

>> Actually brings me to the point I glanced over in the previous patch
>> - why would intel_wait_for_register_fw be not suitable for long
>> waits? It looks like a concern for the calling code grabbing the fw
>> outside it for a long period and not for the function itself. This
>> call site being a case in point for that.
>
> The code here doesn't take a wakeref for its register reads (as they are
> through the MCHBAR and not our GT powerwell). My concern is that I don't
> want to encourage people to hold the wakeref for tens, even hundreds of
> milliseconds, waiting for random changes in the hardware. Another
> concern is that there are some instability issues in overusing the
> unlocked mmio accessors (due to bad hw) and there we need to be
> judicious in when we use them. (I keep wondering if we have sufficient
> contention issue to justify a hashed spinlock per mmio-cacheline.)

Hm, ok, don't know about those issues. Either way it is not too bad if 
kerneldoc is overly cautious.

Regards,

Tvrtko

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-06-30 13:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 11:30 [PATCH 1/4] drm/i915: Use a hybrid scheme for fast register waits Chris Wilson
2016-06-30 11:30 ` [PATCH 2/4] drm/i915: Convert sandybridge_pcode_*() to use intel_wait_for_register() Chris Wilson
2016-06-30 13:04   ` Tvrtko Ursulin
2016-06-30 13:19     ` Chris Wilson
2016-06-30 13:39       ` Tvrtko Ursulin [this message]
2016-06-30 19:21   ` Matt Turner
2016-06-30 11:30 ` [PATCH 3/4] drm/i915: Convert wait_for(I915_READ(reg)) to intel_wait_for_register() Chris Wilson
2016-06-30 13:27   ` Tvrtko Ursulin
2016-06-30 13:34     ` Chris Wilson
2016-06-30 13:42       ` Tvrtko Ursulin
2016-06-30 11:30 ` [PATCH 4/4] drm/i915: Perform Sandybridge BSD tail write under the forcewake Chris Wilson
2016-06-30 13:32   ` Tvrtko Ursulin
2016-06-30 12:05 ` ✗ Ro.CI.BAT: warning for series starting with [1/4] drm/i915: Use a hybrid scheme for fast register waits Patchwork
2016-06-30 12:58 ` [PATCH 1/4] " Tvrtko Ursulin

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=5775210D.1070000@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@intel.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