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@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Chris Wilson Sent: Tuesday, August 22, 2017 9:01 PM To: Wang, Zhi A <zhi.a.wang@xxxxxxxxx>; intel-gfx@xxxxxxxxxxxxxxxxxxxxx; intel-gvt-dev@xxxxxxxxxxxxxxxxxxxxx Cc: joonas.lahtinen@xxxxxxxxxxxxxxx; Wang, Zhi A <zhi.a.wang@xxxxxxxxx>; zhenyuw@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
