public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Zhi Wang <zhi.a.wang@intel.com>,
	intel-gfx@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH v17 1/4] drm/i915: Introduce private PAT management
Date: Thu, 14 Sep 2017 16:48:09 +0300	[thread overview]
Message-ID: <1505396889.12825.0.camel@linux.intel.com> (raw)
In-Reply-To: <1505392783-4084-1-git-send-email-zhi.a.wang@intel.com>

On Thu, 2017-09-14 at 20:39 +0800, Zhi Wang wrote:
> The private PAT management is to support PPAT entry manipulation. Two
> APIs are introduced for dynamically managing PPAT entries: intel_ppat_get
> and intel_ppat_put.
> 
> intel_ppat_get will search for an existing PPAT entry which perfectly
> matches the required PPAT value. If not, it will try to allocate a new
> entry if there is any available PPAT indexs, or return a partially
> matched PPAT entry if there is no available PPAT indexes.
> 
> intel_ppat_put will put back the PPAT entry which comes from
> intel_ppat_get. If it's dynamically allocated, the reference count will
> be decreased. If the reference count turns into zero, the PPAT index is
> freed again.
> 
> Besides, another two callbacks are introduced to support the private PAT
> management framework. One is ppat->update_hw(), which writes the PPAT
> configurations in ppat->entries into HW. Another one is ppat->match, which
> will return a score to show how two PPAT values match with each other.
> 

I manually fixed the enum to use BIT() and merged the first two patches
of the series. The third should go in with the kselftests.

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

  parent reply	other threads:[~2017-09-14 13:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 12:39 [PATCH v17 1/4] drm/i915: Introduce private PAT management Zhi Wang
2017-09-14 12:39 ` [PATCH v17 2/4] drm/i915: Remove the "INDEX" suffix from PPAT marcos Zhi Wang
2017-09-14 12:39 ` [PATCH v17 3/4] drm/i915: Do not allocate unused PPAT entries Zhi Wang
2017-09-14 12:39 ` [PATCH v17 4/4] drm/i915/selftests: Introduce live tests of private PAT management Zhi Wang
2017-09-14 13:42   ` Chris Wilson
2017-09-14 16:37     ` Wang, Zhi A
2017-09-14 13:06 ` ✓ Fi.CI.BAT: success for series starting with [v17,1/4] drm/i915: Introduce " Patchwork
2017-09-14 13:48 ` Joonas Lahtinen [this message]
2017-09-14 16:36   ` [PATCH v17 1/4] " Wang, Zhi A
2017-09-14 16:46   ` Wang, Zhi A
2017-09-14 15:26 ` ✗ Fi.CI.IGT: failure for series starting with [v17,1/4] " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2017-09-14 17:21 [PATCH 1/2] drm/i915: Fix a typo in i915_ppat_get() Zhi Wang
2017-09-14 17:21 ` [PATCH v17 1/4] drm/i915: Introduce private PAT management Zhi Wang

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=1505396889.12825.0.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=benjamin.widawsky@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=zhi.a.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox