From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: mika.kuoppala@intel.com
Subject: Re: [PATCH v2 5/5] drm/i915: Drop uncore spinlock for reading forcewake counters
Date: Wed, 22 Mar 2017 16:37:46 +0200 [thread overview]
Message-ID: <1490193466.2802.65.camel@linux.intel.com> (raw)
In-Reply-To: <20170322123727.9564-5-chris@chris-wilson.co.uk>
On ke, 2017-03-22 at 12:37 +0000, Chris Wilson wrote:
> The set of available structs is not protected by the spinlock, and for
> the single read we can use READ_ONCE instead.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
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
next prev parent reply other threads:[~2017-03-22 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:37 [PATCH v2 1/5] drm/i915: Eliminate per-fw_domain i915 backpointer Chris Wilson
2017-03-22 12:37 ` [PATCH v2 2/5] drm/i915: Skip unused fw_domains Chris Wilson
2017-03-23 9:36 ` Mika Kuoppala
2017-03-23 10:09 ` Chris Wilson
2017-03-22 12:37 ` [PATCH v2 3/5] drm/i915: Remove posting-read for forcewake put Chris Wilson
2017-03-22 12:37 ` [PATCH v2 4/5] drm/i915: All fw_domains share the same set/clear/reset values Chris Wilson
2017-03-22 12:37 ` [PATCH v2 5/5] drm/i915: Drop uncore spinlock for reading forcewake counters Chris Wilson
2017-03-22 14:37 ` Joonas Lahtinen [this message]
2017-03-22 15:05 ` ✗ Fi.CI.BAT: warning for series starting with [v2,1/5] drm/i915: Eliminate per-fw_domain i915 backpointer 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=1490193466.2802.65.camel@linux.intel.com \
--to=joonas.lahtinen@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 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.