1. 21 4月, 2022 5 次提交
  2. 20 4月, 2022 6 次提交
  3. 16 4月, 2022 3 次提交
  4. 15 4月, 2022 2 次提交
    • M
      drm/i915/uapi: Add DRM_I915_QUERY_GEOMETRY_SUBSLICES · c94fde8f
      Matt Atwood 提交于
      Newer platforms have DSS that aren't necessarily available for both
      geometry and compute, two queries will need to exist. This introduces
      the first, when passing a valid engine class and engine instance in the
      flags returns a topology describing geometry.
      
      Based on past discussion, we currently only support this new query item
      on Xe_HP and beyond; earlier platforms do not need to worry about
      geometry and compute pipelines having access to different topology and
      should continue to use the existing topology query.
      
      v2: fix white space errors
      v3: change flags from hosting 2 8 bit numbers to holding a
      i915_engine_class_instance struct
      v4: add error if non rcs engine passed.
      v5 (by MattR):
       - Improve kerneldoc and cross references to related structs/enums.
         (Daniel)
       - Clarify that geometry query is only supported on render engines
         (Francisco)
       - Clarify that the new query is only supported on Xe_HP+.
       - Fix checkpatch warnings.
      
      Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
      Cc: Matt Roper <matthew.d.roper@intel.com>
      Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Cc: Francisco Jerez <currojerez@riseup.net>
      UMD (mesa): https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14143
      Testcase: igt@i915_query@test-query-geometry-subslices
      Signed-off-by: NMatt Atwood <matthew.s.atwood@intel.com>
      Signed-off-by: NMatt Roper <matthew.d.roper@intel.com>
      Reviewed-by: NFrancisco Jerez <currojerez@riseup.net>
      Link: https://patchwork.freedesktop.org/patch/msgid/20220414192230.749771-4-matthew.d.roper@intel.com
      c94fde8f
    • J
      drm/i915/guc: Update to GuC version 70.1.1 · 2584b354
      John Harrison 提交于
      The latest GuC firmware drops the context descriptor pool in favour of
      passing all creation data in the create H2G. It also greatly simplifies
      the work queue and removes the process descriptor used for multi-LRC
      submission. So, remove all mention of LRC and process descriptors and
      update the registration code accordingly.
      
      Unfortunately, the new API also removes the ability to set default
      values for the scheduling policies at context registration time.
      Instead, a follow up H2G must be sent. The individual scheduling
      policy update H2G commands are also dropped in favour of a single KLV
      based H2G. So, change the update wrappers accordingly and call this
      during context registration..
      
      Of course, this second H2G per registration might fail due to being
      backed up. The registration code has a complicated state machine to
      cope with the actual registration call failing. However, if that works
      then there is no support for unwinding if a further call should fail.
      Unwinding would require sending a H2G to de-register - but that can't
      be done because the CTB is already backed up.
      
      So instead, add a new flag to say whether the context has a pending
      policy update. This is set if the policy H2G fails at registration
      time. The submission code checks for this flag and retries the policy
      update if set. If that call fails, the submission path early exists
      with a retry error. This is something that is already supported for
      other reasons.
      Signed-off-by: NJohn Harrison <John.C.Harrison@Intel.com>
      Reviewed-by: NDaniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
      Signed-off-by: NMatt Roper <matthew.d.roper@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20220412225955.1802543-2-John.C.Harrison@Intel.com
      2584b354
  5. 14 4月, 2022 9 次提交
  6. 13 4月, 2022 8 次提交
  7. 12 4月, 2022 7 次提交