All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: vlv: reserve the GT power context only once during driver init
Date: Tue, 1 Apr 2014 20:11:22 +0300	[thread overview]
Message-ID: <20140401171122.GJ21652@intel.com> (raw)
In-Reply-To: <1396267844-9235-1-git-send-email-imre.deak@intel.com>

On Mon, Mar 31, 2014 at 03:10:44PM +0300, Imre Deak wrote:
> Atm we reserve/allocate and free the power context during GT power
> enable/disable time. There is no need to do this, we can reserve/allocate
> the buffer once during driver loading and free it during driver cleanup.
> The re-reservation can also fail in case the driver previously manages to
> allocate something on the given fixed address.
> 
> The buffer isn't exepected to move even if allocated by the BIOS, for
> safety add an assert to check this assumption.
> 
> This also fixed a bug for Ville, where re-reserving the context failed
> during a GPU reset (I assume because something else got allocated on its
> fixed address).

I'm assuming it was the already existing pctx allocation that caused the
warning. We just call intel_enable_gt_powersave() again during GPU reset
w/o having called intel_disable_gt_powersave() anywhere. So no danger of
clobbering the pctx AFAICS, but getting a WARN on every GPU reset is
rather annoying.

> 
> Tested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>

The patch looks good to me.

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

<snip>

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-04-01 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 12:10 [PATCH] drm/i915: vlv: reserve the GT power context only once during driver init Imre Deak
2014-04-01 17:11 ` Ville Syrjälä [this message]
2014-04-01 20:31   ` Daniel Vetter

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=20140401171122.GJ21652@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=imre.deak@intel.com \
    --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.