All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.william.auld@gmail.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/i915: fix comment referencing imaginary functions
Date: Tue, 25 Oct 2016 12:29:41 +0100	[thread overview]
Message-ID: <CAM0jSHPjsVhutiEqzZz1nEyskS_+dNp_4KwSk2xgjb-C6ywWoQ@mail.gmail.com> (raw)
In-Reply-To: <20161024112314.GA4358@ahiler-desk.igk.intel.com>

> These are untraced mmio-accessors that are only valid to be used inside
> critical sections inside IRQ handlers where forcewake is explicitly
> controlled.
>
> Think twice, and think again, before using these.
>
> Those possibly should be used between:
>
> spin_lock_irq(&dev_priv->uncore.lock);
> intel_uncore_forcewake_get();
>
> and
>
> intel_uncore_forcewake_put();
> spin_unlock_irq(&dev_priv->uncore.lock);
>
>
> Note: some registers may not need forcewake held, so
> intel_uncore_forcewake_{get,put} can be omitted.
>
> Code may be serialised by different lock, so immediate
> spin_{lock,unlock}_irq() may not be necessary.
Maybe roll that up into a new patch? Assuming Chris is happy...
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-10-25 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 16:03 [PATCH] drm/i915: fix comment referencing imaginary functions Matthew Auld
2016-08-24 16:50 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-10-21 12:16 ` [PATCH] " Arkadiusz Hiler
2016-10-21 12:28   ` Chris Wilson
2016-10-21 13:00     ` Mika Kuoppala
2016-10-21 13:57       ` Chris Wilson
2016-10-24 11:23         ` Arkadiusz Hiler
2016-10-25 11:29           ` Matthew Auld [this message]
2016-10-25 11:39             ` Chris Wilson

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=CAM0jSHPjsVhutiEqzZz1nEyskS_+dNp_4KwSk2xgjb-C6ywWoQ@mail.gmail.com \
    --to=matthew.william.auld@gmail.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@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.