[ BACKGROUND ]
Due to different guests will have different PPAT configuration under
virtualization environment, for example, Windows guest vs Linux guest, a
possible idea to handle this open is
1)Letting host have the PPAT entries needed by guest
2)Mapping PPAT indexes in guest page table to the corresponding host
PPAT entries during building the shadow page table.
To achieve 1), one approach which has been used before is statically
adding the collection of guest PPAT configuration into host i915. So
when performing 2) GVT-g will always find an available PPAT entry to map.
Another possible approach is GVT-g could dynamically find/add/delete the
PPAT configuration for different guests. To prevent regression of host
i915 due to this changes, it’s better to have two types of PPAT entry:
one is “static PPAT entry”, which is to keep current host i915 PPAT
configuration unchanged, e.g. the mapping between i915 cache level and
PPAT index, etc… just keep everything used by host i915 unchanged and a
*static* PPAT entry will not be modified.
Another type is “dynamic PPAT entry”, which will be managed by GVT-g.
[ EXPECTED CHANGE OF HOST i915 ]
Since i915 doesn’t need dynamic PPAT allocation, one idea is putting all
the dynamic PPAT entry management in GVT-g, i915 shows a bitmap of
available PPAT indexes to GVT-g after initializing host PPAT entries, so
GVT-g could manage them on-demand.
Thanks,
Zhi.
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
