Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] RFC drm/i915: Emulate 64bit registers for residency counters
Date: Thu, 7 Apr 2016 17:17:52 +0300	[thread overview]
Message-ID: <20160407141752.GL4329@intel.com> (raw)
In-Reply-To: <20160407135801.GD18061@nuc-i3427.alporthouse.com>

On Thu, Apr 07, 2016 at 02:58:01PM +0100, Chris Wilson wrote:
> On Thu, Apr 07, 2016 at 04:18:16PM +0300, Ville Syrjälä wrote:
> > On Thu, Apr 07, 2016 at 01:59:44PM +0100, Chris Wilson wrote:
> > > Can we set that bit ourselves? That puts the overflow into the 1 hour
> > > mark. Thanks,
> > 
> > I don't know if it's safe to frob the bit. I worry that something
> > outside our control might depend on it staying put.
> 
> A quick frob of the bit says that it is RO. When I try to set it, it
> doesn't stick. :(

Same here on my VLV. I was able to toggle it on my BSW. Perhaps
something can lock it down, and my BSW BIOS just doesn't do that.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-04-07 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 11:24 [PATCH] RFC drm/i915: Emulate 64bit registers for residency counters Chris Wilson
2016-04-07 12:13 ` Ville Syrjälä
2016-04-07 12:37   ` Chris Wilson
2016-04-07 12:49     ` Ville Syrjälä
2016-04-07 12:59       ` Chris Wilson
2016-04-07 13:18         ` Ville Syrjälä
2016-04-07 13:58           ` Chris Wilson
2016-04-07 14:17             ` Ville Syrjälä [this message]
2016-04-07 15:29 ` ✗ Fi.CI.BAT: failure for " Patchwork

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=20160407141752.GL4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lenb@kernel.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