All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
	Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH 2/2] drm/i915: l3 parity sysfs interface
Date: Fri, 13 Apr 2012 18:39:24 -0700	[thread overview]
Message-ID: <20120413183924.3dbc8304@bwidawsk.net> (raw)
In-Reply-To: <1334359471_417726@CP5-2952>

On Sat, 14 Apr 2012 00:24:03 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> On Fri, 13 Apr 2012 16:05:14 -0700, Ben Widawsky <ben@bwidawsk.net>
> wrote:
> > Dumb binary interfaces which allow root-only updates of our cache
> > remapping registers.  See intel-gpu-tools for how this can/should be
> > used.
> 
> Initial comments: don't bother posting a read just before a read, and
> do return errors from the sysfs read/write functions (the return
> value is signed for that purpose). A lesser issue is that if you are
> worried about necessity of posting-reads, you should also worry about
> the effect of the weak ordering of writes.
> -Chris
> 

Thanks for the advice on the sysfs return values. Some of the code I
was referring from just returns 0, but this seems to be not the right
thing to do after looking further into it.

As for the POSTING_READ it was intentional. Unless reads are always in
order??? I have to make sure the clock gating disable propogates before
I can read the L3 registers.

Ben

  reply	other threads:[~2012-04-14  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 23:05 [PATCH 0/2] [RFC] Dynamic parity detection Ben Widawsky
2012-04-13 23:05 ` [PATCH 1/2] drm/i915: Dynamic Parity Detection handling Ben Widawsky
2012-04-13 23:05 ` [PATCH 2/2] drm/i915: l3 parity sysfs interface Ben Widawsky
2012-04-13 23:24   ` Chris Wilson
2012-04-14  1:39     ` Ben Widawsky [this message]
2012-04-14  1:42       ` Ben Widawsky

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=20120413183924.3dbc8304@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=benjamin.widawsky@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.