[Intel-gfx] [RFCv2 2/3] drm/i915: Introduce private PAT management

[Wang, Zhi A]

The "reserved" PPAT indexes is for keeping current i915 logics unchanged since I don't want to cause regression. I can remove "reserved" PPAT indexes actually.

-----Original Message-----
From: intel-gvt-dev [mailto:intel-gvt-dev-bounces at lists.freedesktop.org] On Behalf Of Chris Wilson
Sent: Tuesday, August 22, 2017 9:01 PM
To: Wang, Zhi A <zhi.a.wang at intel.com>; intel-gfx at lists.freedesktop.org; intel-gvt-dev at lists.freedesktop.org
Cc: joonas.lahtinen at linux.intel.com; Wang, Zhi A <zhi.a.wang at intel.com>; zhenyuw at linux.intel.com
Subject: Re: [RFCv2 2/3] drm/i915: Introduce private PAT management

Quoting Zhi Wang (2017-08-23 02:44:12)
> The private PAT management is to support both static and dynamic PPAT 
> entry manipulation. During the initialization, the PPAT indexes with 
> specific PPAT values could be reserved and set by intel_ppat_reserve.
> The unused PPAT entries can be allocated/freed later at runtime. Two 
> APIs are introduced for dynamically managing PPAT entries: 
> intel_ppat_get and intel_ppat_set.

What's the use case for reserved? Once assigned, a new allocation doesn't evict, so reservation is just another form of assignment.
-Chris
_______________________________________________
intel-gvt-dev mailing list
intel-gvt-dev at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev