All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/perf: Store shortcut to intel_uncore
Date: Thu, 10 Oct 2019 17:58:00 +0300	[thread overview]
Message-ID: <62bdbafd-6cbe-f24a-961a-1b7a61423d33@intel.com> (raw)
In-Reply-To: <20191010072752.18495-2-chris@chris-wilson.co.uk>

On 10/10/2019 10:27, Chris Wilson wrote:
> Now that we have the engine stored in i915_perf, we have a means of
> accessing intel_gt should we require it. However, we are currently only
> using the intel_gt to find the right intel_uncore, so replace our
> i915_perf.gt pointer with the more useful i915_perf.uncore.
>
> Signed-off-by: Chris Wilson<chris@chris-wilson.co.uk>
> Cc: Lionel Landwerlin<lionel.g.landwerlin@intel.com>
> ---

Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-10-10 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10  7:27 [PATCH 1/2] drm/i915/perf: store the associated engine of a stream Chris Wilson
2019-10-10  7:27 ` [PATCH 2/2] drm/i915/perf: Store shortcut to intel_uncore Chris Wilson
2019-10-10 14:58   ` Lionel Landwerlin [this message]
2019-10-10  9:11 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/perf: store the associated engine of a stream Patchwork
2019-10-10 14:57 ` [PATCH 1/2] " Lionel Landwerlin
2019-10-10 15:04   ` 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=62bdbafd-6cbe-f24a-961a-1b7a61423d33@intel.com \
    --to=lionel.g.landwerlin@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.