intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris.p.wilson@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/4] Allow privileged user to map the OA buffer
Date: Thu, 24 Sep 2020 09:29:30 -0700	[thread overview]
Message-ID: <20200924162930.GA31813@orsosgc001.ra.intel.com> (raw)
In-Reply-To: <20200820180200.68355-1-umesh.nerlige.ramappa@intel.com>

Hi Chris,

Okay to push this series?

Thanks,
Umesh

On Thu, Aug 20, 2020 at 11:01:56AM -0700, Umesh Nerlige Ramappa wrote:
>Allow user to map the OA buffer and also trigger reports into it.
>
>CI fixes:
>v1: Fixes a memory corruption due to addition of OA whitelist on demand.
>v2: Spinlock when applying whitelist
>v3: Use uncore->lock. Do not check for wal->count when applying whitelist.
>
>v4: Refresh and rerun with newly added test (forked access).
>
>Tests: https://patchwork.freedesktop.org/series/80761/
>Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>Test-with: 20200818203547.24461-1-umesh.nerlige.ramappa@intel.com
>
>Piotr Maciejewski (1):
>  drm/i915/perf: Ensure observation logic is not clock gated
>
>Umesh Nerlige Ramappa (3):
>  drm/i915/perf: Whitelist OA report trigger registers
>  drm/i915/perf: Whitelist OA counter and buffer registers
>  drm/i915/perf: Map OA buffer to user space for gen12 performance query
>
> drivers/gpu/drm/i915/gem/i915_gem_mman.c      |   2 +-
> drivers/gpu/drm/i915/gem/i915_gem_mman.h      |   2 +
> drivers/gpu/drm/i915/gt/intel_workarounds.c   | 153 +++++++++---
> drivers/gpu/drm/i915/gt/intel_workarounds.h   |   7 +
> .../gpu/drm/i915/gt/intel_workarounds_types.h |   5 +
> drivers/gpu/drm/i915/i915_perf.c              | 225 +++++++++++++++++-
> drivers/gpu/drm/i915/i915_perf_types.h        |   5 +
> drivers/gpu/drm/i915/i915_reg.h               |  10 +
> include/uapi/drm/i915_drm.h                   |  33 +++
> 9 files changed, 402 insertions(+), 40 deletions(-)
>
>-- 
>2.20.1
>
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx@lists.freedesktop.org
>https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-09-24 16:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20 18:01 [Intel-gfx] [PATCH 0/4] Allow privileged user to map the OA buffer Umesh Nerlige Ramappa
2020-08-20 18:01 ` [Intel-gfx] [PATCH 1/4] drm/i915/perf: Ensure observation logic is not clock gated Umesh Nerlige Ramappa
2020-08-20 18:01 ` [Intel-gfx] [PATCH 2/4] drm/i915/perf: Whitelist OA report trigger registers Umesh Nerlige Ramappa
2020-08-20 18:01 ` [Intel-gfx] [PATCH 3/4] drm/i915/perf: Whitelist OA counter and buffer registers Umesh Nerlige Ramappa
2020-08-20 18:02 ` [Intel-gfx] [PATCH 4/4] drm/i915/perf: Map OA buffer to user space for gen12 performance query Umesh Nerlige Ramappa
2020-08-20 18:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Allow privileged user to map the OA buffer Patchwork
2020-08-21  3:20 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-09-24 16:29 ` Umesh Nerlige Ramappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-04 17:11 [Intel-gfx] [PATCH 0/4] " Umesh Nerlige Ramappa
2020-07-31 23:58 Umesh Nerlige Ramappa
2020-07-31 14:46 Umesh Nerlige Ramappa
2020-07-31  6:07 Umesh Nerlige Ramappa
2020-07-30 23:02 Umesh Nerlige Ramappa
2020-07-24  0:18 Umesh Nerlige Ramappa
2020-07-22  5:55 Umesh Nerlige Ramappa
2020-07-21  2:00 Umesh Nerlige Ramappa
2020-07-18  0:04 Umesh Nerlige Ramappa

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=20200924162930.GA31813@orsosgc001.ra.intel.com \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=chris.p.wilson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).