From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>, dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org Subject: [PULL] drm-intel-gt-next Date: Fri, 11 Aug 2023 13:47:57 +0300 [thread overview] Message-ID: <ZNYR3bKFquGc7u9w@jlahtine-mobl.ger.corp.intel.com> (raw) Hi Dave & Daniel, Here's the final drm-intel-gt-next PR for v6.6. Not too many patches as the previous PR was later than usual. Just one more workaround fix for MTL, some object coherency refactoring and selftest fix. Note that there is a backmerge of drm-next[1], too. Regards, Joonas [1] As prep for https://patchwork.freedesktop.org/series/121735/ but the series started failing CI after rebasing and continues to be investigated so not landing here yet. *** drm-intel-gt-next-2023-08-11: Cross-subsystem Changes: - Backmerge of drm-next Driver Changes: - Apply workaround 22016122933 correctly (Jonathan, Matt R) - Simplify shmem_create_from_object map_type selection (Jonathan, Tvrtko) - Make i915_coherent_map_type GT-centric (Jonathan, Matt R) - Selftest improvements (John) The following changes since commit d9aa1da9a8cfb0387eb5703c15bd1f54421460ac: Merge tag 'drm-intel-gt-next-2023-08-04' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2023-08-07 13:49:25 +1000) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-gt-next-2023-08-11 for you to fetch changes up to 788568fad4015406fa84fc86cefbef7c470c7c1f: drm/i915/guc: Fix potential null pointer deref in GuC 'steal id' test (2023-08-10 16:02:01 -0700) ---------------------------------------------------------------- Cross-subsystem Changes: - Backmerge of drm-next Driver Changes: - Apply workaround 22016122933 correctly (Jonathan, Matt R) - Simplify shmem_create_from_object map_type selection (Jonathan, Tvrtko) - Make i915_coherent_map_type GT-centric (Jonathan, Matt R) - Selftest improvements (John) ---------------------------------------------------------------- John Harrison (1): drm/i915/guc: Fix potential null pointer deref in GuC 'steal id' test Jonathan Cavitt (3): drm/i915/gt: Simplify shmem_create_from_object map_type selection drm/i915: Make i915_coherent_map_type GT-centric drm/i915/gt: Apply workaround 22016122933 correctly Joonas Lahtinen (1): Merge drm/drm-next into drm-intel-gt-next drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 3 ++- drivers/gpu/drm/i915/gem/i915_gem_object.h | 4 ---- drivers/gpu/drm/i915/gem/i915_gem_pages.c | 15 --------------- drivers/gpu/drm/i915/gem/selftests/i915_gem_migrate.c | 12 ++++++------ drivers/gpu/drm/i915/gt/intel_engine_pm.c | 2 +- drivers/gpu/drm/i915/gt/intel_gt.c | 16 ++++++++++++++++ drivers/gpu/drm/i915/gt/intel_gt.h | 10 ++++++++++ drivers/gpu/drm/i915/gt/intel_gtt.c | 4 ++-- drivers/gpu/drm/i915/gt/intel_lrc.c | 13 +++++++------ drivers/gpu/drm/i915/gt/intel_ring.c | 3 ++- drivers/gpu/drm/i915/gt/selftest_context.c | 5 +++-- drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 4 ++-- drivers/gpu/drm/i915/gt/selftest_lrc.c | 6 +++--- drivers/gpu/drm/i915/gt/shmem_utils.c | 3 +-- drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.c | 7 +------ drivers/gpu/drm/i915/gt/uc/intel_guc.c | 11 ++++++----- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 4 ---- drivers/gpu/drm/i915/gt/uc/intel_huc_fw.c | 3 +-- drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 3 ++- drivers/gpu/drm/i915/gt/uc/selftest_guc.c | 6 +++--- drivers/gpu/drm/i915/pxp/intel_pxp_gsccs.c | 3 ++- drivers/gpu/drm/i915/pxp/intel_pxp_tee.c | 5 ++++- drivers/gpu/drm/i915/selftests/igt_spinner.c | 2 +- 23 files changed, 75 insertions(+), 69 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch> Cc: dim-tools@lists.freedesktop.org, dri-devel@lists.freedesktop.org, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org Subject: [Intel-gfx] [PULL] drm-intel-gt-next Date: Fri, 11 Aug 2023 13:47:57 +0300 [thread overview] Message-ID: <ZNYR3bKFquGc7u9w@jlahtine-mobl.ger.corp.intel.com> (raw) Hi Dave & Daniel, Here's the final drm-intel-gt-next PR for v6.6. Not too many patches as the previous PR was later than usual. Just one more workaround fix for MTL, some object coherency refactoring and selftest fix. Note that there is a backmerge of drm-next[1], too. Regards, Joonas [1] As prep for https://patchwork.freedesktop.org/series/121735/ but the series started failing CI after rebasing and continues to be investigated so not landing here yet. *** drm-intel-gt-next-2023-08-11: Cross-subsystem Changes: - Backmerge of drm-next Driver Changes: - Apply workaround 22016122933 correctly (Jonathan, Matt R) - Simplify shmem_create_from_object map_type selection (Jonathan, Tvrtko) - Make i915_coherent_map_type GT-centric (Jonathan, Matt R) - Selftest improvements (John) The following changes since commit d9aa1da9a8cfb0387eb5703c15bd1f54421460ac: Merge tag 'drm-intel-gt-next-2023-08-04' of git://anongit.freedesktop.org/drm/drm-intel into drm-next (2023-08-07 13:49:25 +1000) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-gt-next-2023-08-11 for you to fetch changes up to 788568fad4015406fa84fc86cefbef7c470c7c1f: drm/i915/guc: Fix potential null pointer deref in GuC 'steal id' test (2023-08-10 16:02:01 -0700) ---------------------------------------------------------------- Cross-subsystem Changes: - Backmerge of drm-next Driver Changes: - Apply workaround 22016122933 correctly (Jonathan, Matt R) - Simplify shmem_create_from_object map_type selection (Jonathan, Tvrtko) - Make i915_coherent_map_type GT-centric (Jonathan, Matt R) - Selftest improvements (John) ---------------------------------------------------------------- John Harrison (1): drm/i915/guc: Fix potential null pointer deref in GuC 'steal id' test Jonathan Cavitt (3): drm/i915/gt: Simplify shmem_create_from_object map_type selection drm/i915: Make i915_coherent_map_type GT-centric drm/i915/gt: Apply workaround 22016122933 correctly Joonas Lahtinen (1): Merge drm/drm-next into drm-intel-gt-next drivers/gpu/drm/i915/display/intel_hdcp_gsc.c | 3 ++- drivers/gpu/drm/i915/gem/i915_gem_object.h | 4 ---- drivers/gpu/drm/i915/gem/i915_gem_pages.c | 15 --------------- drivers/gpu/drm/i915/gem/selftests/i915_gem_migrate.c | 12 ++++++------ drivers/gpu/drm/i915/gt/intel_engine_pm.c | 2 +- drivers/gpu/drm/i915/gt/intel_gt.c | 16 ++++++++++++++++ drivers/gpu/drm/i915/gt/intel_gt.h | 10 ++++++++++ drivers/gpu/drm/i915/gt/intel_gtt.c | 4 ++-- drivers/gpu/drm/i915/gt/intel_lrc.c | 13 +++++++------ drivers/gpu/drm/i915/gt/intel_ring.c | 3 ++- drivers/gpu/drm/i915/gt/selftest_context.c | 5 +++-- drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 4 ++-- drivers/gpu/drm/i915/gt/selftest_lrc.c | 6 +++--- drivers/gpu/drm/i915/gt/shmem_utils.c | 3 +-- drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.c | 7 +------ drivers/gpu/drm/i915/gt/uc/intel_guc.c | 11 ++++++----- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 4 ---- drivers/gpu/drm/i915/gt/uc/intel_huc_fw.c | 3 +-- drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 3 ++- drivers/gpu/drm/i915/gt/uc/selftest_guc.c | 6 +++--- drivers/gpu/drm/i915/pxp/intel_pxp_gsccs.c | 3 ++- drivers/gpu/drm/i915/pxp/intel_pxp_tee.c | 5 ++++- drivers/gpu/drm/i915/selftests/igt_spinner.c | 2 +- 23 files changed, 75 insertions(+), 69 deletions(-)
next reply other threads:[~2023-08-11 10:50 UTC|newest] Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-11 10:47 Joonas Lahtinen [this message] 2023-08-11 10:47 ` [Intel-gfx] [PULL] drm-intel-gt-next Joonas Lahtinen -- strict thread matches above, loose matches on Subject: below -- 2024-04-26 7:17 Joonas Lahtinen 2024-02-28 14:02 Tvrtko Ursulin 2024-02-15 10:06 Tvrtko Ursulin 2024-02-16 2:58 ` Dave Airlie 2024-02-16 9:31 ` Thomas Hellström 2024-02-16 9:33 ` Thomas Hellström 2024-02-16 9:41 ` Joonas Lahtinen 2024-02-20 15:14 ` Joonas Lahtinen 2023-12-15 12:11 Joonas Lahtinen 2023-12-15 12:11 ` Joonas Lahtinen 2023-12-08 16:18 Joonas Lahtinen 2023-12-08 16:18 ` Joonas Lahtinen 2023-10-19 14:54 Tvrtko Ursulin 2023-10-12 10:30 Tvrtko Ursulin 2023-09-28 12:36 Tvrtko Ursulin 2023-08-04 8:45 Joonas Lahtinen 2023-06-08 15:34 Tvrtko Ursulin 2023-05-24 18:09 Tvrtko Ursulin 2023-04-06 11:41 Maarten Lankhorst 2023-04-06 12:34 ` Jani Nikula 2023-04-06 13:00 ` Daniel Vetter 2023-04-06 8:18 Joonas Lahtinen 2023-04-06 12:38 ` Daniel Vetter 2023-03-16 12:58 Joonas Lahtinen 2023-02-01 11:36 Tvrtko Ursulin 2023-01-18 11:24 Tvrtko Ursulin 2023-01-24 15:32 ` Daniel Vetter 2022-11-18 9:12 Joonas Lahtinen 2022-11-03 8:03 Joonas Lahtinen 2022-10-31 11:07 Joonas Lahtinen 2022-11-01 19:33 ` Dave Airlie 2022-09-16 8:47 Joonas Lahtinen 2022-09-09 11:20 Joonas Lahtinen 2022-08-24 12:01 Joonas Lahtinen 2022-07-13 21:31 Rodrigo Vivi 2022-07-21 15:06 ` Vivi, Rodrigo 2022-06-29 10:45 Tvrtko Ursulin 2022-05-05 6:39 Tvrtko Ursulin 2022-04-27 10:49 Tvrtko Ursulin 2022-03-03 7:50 Joonas Lahtinen 2022-02-17 10:26 Joonas Lahtinen 2022-02-20 23:30 ` Dave Airlie 2022-02-21 9:21 ` Jani Nikula 2022-02-22 19:44 ` Lucas De Marchi 2022-02-23 20:35 ` Vivi, Rodrigo 2021-12-23 12:47 Tvrtko Ursulin 2021-12-09 13:14 Tvrtko Ursulin 2021-10-21 13:07 Joonas Lahtinen 2021-10-08 9:27 Joonas Lahtinen 2021-08-06 10:06 Joonas Lahtinen 2021-08-06 10:10 ` Joonas Lahtinen 2021-06-10 9:40 Joonas Lahtinen 2021-05-28 7:25 Joonas Lahtinen 2021-05-28 7:27 ` Joonas Lahtinen 2021-06-02 0:28 ` Dave Airlie 2021-06-02 4:17 ` Dave Airlie 2021-06-02 4:30 ` Dave Airlie 2021-04-06 13:40 Joonas Lahtinen 2021-01-21 15:07 Joonas Lahtinen 2021-01-14 15:22 Joonas Lahtinen 2020-11-12 16:34 Joonas Lahtinen 2020-09-07 13:00 Joonas Lahtinen 2020-09-04 13:39 Joonas Lahtinen
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=ZNYR3bKFquGc7u9w@jlahtine-mobl.ger.corp.intel.com \ --to=joonas.lahtinen@linux.intel.com \ --cc=airlied@gmail.com \ --cc=daniel.vetter@ffwll.ch \ --cc=dim-tools@lists.freedesktop.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=mripard@kernel.org \ --cc=rodrigo.vivi@intel.com \ --cc=tvrtko.ursulin@linux.intel.com \ --cc=tzimmermann@suse.de \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.