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, Rodrigo Vivi <rodrigo.vivi@intel.com>, Sean Paul <sean@poorly.run>, intel-gfx@lists.freedesktop.org Subject: [PULL] drm-intel-next-fixes Date: Wed, 20 Nov 2019 22:40:35 +0200 [thread overview] Message-ID: <20191120204035.GA14908@jlahtine-desk.ger.corp.intel.com> (raw) Hi Dave & Daniel, NOTE: CI shard results are delayed, bu I'm sending this already because I'll travel tomorrow. I'll let you know if the results look OK or not. Or you can look up CI_DINF_162 results check at: https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html This was rebased on top of drm-next to avoid conflicts with the security fixes. We have multiple user reported Bugzillas closed, broken plymouth splash, RC6 lost when enabling HuC and one dmesg splat. OA/perf coherency fix, a GVT dmesg splat and then CI found corner case fixes. Regards, Joonas *** drm-intel-next-fixes-2019-11-20: - Includes gvt-next-fixes-2019-11-12 - Fix Bugzilla #112051: Fix detection for a CMP-V PCH - Fix Bugzilla #112256: Corrupted page table at address on plymouth splash - Fix Bugzilla #111594: Avoid losing RC6 when HuC authentication is used - Fix for OA/perf metric coherency, restore GT coarse power gating workaround - Avoid atomic context on error capture - Avoid MST bitmask overflowing to EDP/DPI input select - Fixes to CI found dmesg splats The following changes since commit 17cc51390c141662748dbbc2fe98f3ed10f2e13e: Merge branch 'vmwgfx-next' of git://people.freedesktop.org/~thomash/linux into drm-next (2019-11-15 12:34:45 +1000) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2019-11-20 for you to fetch changes up to 0122baaa93cc681faace064ec25d16bb5c9825ab: Merge tag 'gvt-next-fixes-2019-11-12' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2019-11-20 13:21:38 +0200) ---------------------------------------------------------------- - Includes gvt-next-fixes-2019-11-12 - Fix Bugzilla #112256: Corrupted page table at address on plymouth splash - Fix Bugzilla #111594: Avoid losing RC6 when HuC authentication is used - Fix Bugzilla #112051: Fix detection for a CMP-V PCH - Fix for OA/perf metric coherency, restore GT coarse power gating workaround - Avoid atomic context on error capture - Avoid MST bitmask overflowing to EDP/DPI input select - Fixes to CI found dmesg splats ---------------------------------------------------------------- Bruce Chang (1): drm/i915: Avoid atomic context for error capture Chris Wilson (4): drm/i915: Flush context free work on cleanup drm/i915/fbdev: Restore physical addresses for fb_mmap() drm/i915/gt: Wait for new requests in intel_gt_retire_requests() drm/i915: Split i915_active.mutex into an irq-safe spinlock for the rbtree Don Hiatt (1): drm/i915/guc: Skip suspend/resume GuC action on platforms w/o GuC submission Imre Deak (2): drm/i915: Fix detection for a CMP-V PCH drm/i915: Restore GT coarse power gating workaround Jani Nikula (1): drm/i915: fix accidental static variable use Joonas Lahtinen (1): Merge tag 'gvt-next-fixes-2019-11-12' of https://github.com/intel/gvt-linux into drm-intel-next-fixes José Roberto de Souza (1): drm/i915/display: Fix TRANS_DDI_MST_TRANSPORT_SELECT definition Lionel Landwerlin (1): drm/i915/perf: don't forget noa wait after oa config Tina Zhang (1): drm/i915/gvt: Stop initializing pvinfo through reading mmio drivers/gpu/drm/i915/display/intel_fbdev.c | 9 +++-- drivers/gpu/drm/i915/display/intel_sprite.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_context.c | 1 + drivers/gpu/drm/i915/gt/intel_gt_requests.c | 11 ++---- drivers/gpu/drm/i915/gt/intel_rc6.c | 9 ++++- drivers/gpu/drm/i915/gt/uc/intel_guc.c | 15 ++++++++ drivers/gpu/drm/i915/gvt/handlers.c | 4 ++ drivers/gpu/drm/i915/i915_active.c | 57 ++++++++++++++--------------- drivers/gpu/drm/i915/i915_active_types.h | 1 + drivers/gpu/drm/i915/i915_drv.h | 6 +++ drivers/gpu/drm/i915/i915_gpu_error.c | 8 ++-- drivers/gpu/drm/i915/i915_perf.c | 9 ++++- drivers/gpu/drm/i915/i915_reg.h | 2 +- drivers/gpu/drm/i915/intel_pch.c | 6 ++- drivers/gpu/drm/i915/intel_pch.h | 2 +- 15 files changed, 89 insertions(+), 53 deletions(-) _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
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>, intel-gfx@lists.freedesktop.org Subject: [Intel-gfx] [PULL] drm-intel-next-fixes Date: Wed, 20 Nov 2019 22:40:35 +0200 [thread overview] Message-ID: <20191120204035.GA14908@jlahtine-desk.ger.corp.intel.com> (raw) Message-ID: <20191120204035.Rrt9YhjiSzcJ2Zw4_tDwkTk4PknVp4a6wOr7k6u6I6A@z> (raw) Hi Dave & Daniel, NOTE: CI shard results are delayed, bu I'm sending this already because I'll travel tomorrow. I'll let you know if the results look OK or not. Or you can look up CI_DINF_162 results check at: https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html This was rebased on top of drm-next to avoid conflicts with the security fixes. We have multiple user reported Bugzillas closed, broken plymouth splash, RC6 lost when enabling HuC and one dmesg splat. OA/perf coherency fix, a GVT dmesg splat and then CI found corner case fixes. Regards, Joonas *** drm-intel-next-fixes-2019-11-20: - Includes gvt-next-fixes-2019-11-12 - Fix Bugzilla #112051: Fix detection for a CMP-V PCH - Fix Bugzilla #112256: Corrupted page table at address on plymouth splash - Fix Bugzilla #111594: Avoid losing RC6 when HuC authentication is used - Fix for OA/perf metric coherency, restore GT coarse power gating workaround - Avoid atomic context on error capture - Avoid MST bitmask overflowing to EDP/DPI input select - Fixes to CI found dmesg splats The following changes since commit 17cc51390c141662748dbbc2fe98f3ed10f2e13e: Merge branch 'vmwgfx-next' of git://people.freedesktop.org/~thomash/linux into drm-next (2019-11-15 12:34:45 +1000) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-fixes-2019-11-20 for you to fetch changes up to 0122baaa93cc681faace064ec25d16bb5c9825ab: Merge tag 'gvt-next-fixes-2019-11-12' of https://github.com/intel/gvt-linux into drm-intel-next-fixes (2019-11-20 13:21:38 +0200) ---------------------------------------------------------------- - Includes gvt-next-fixes-2019-11-12 - Fix Bugzilla #112256: Corrupted page table at address on plymouth splash - Fix Bugzilla #111594: Avoid losing RC6 when HuC authentication is used - Fix Bugzilla #112051: Fix detection for a CMP-V PCH - Fix for OA/perf metric coherency, restore GT coarse power gating workaround - Avoid atomic context on error capture - Avoid MST bitmask overflowing to EDP/DPI input select - Fixes to CI found dmesg splats ---------------------------------------------------------------- Bruce Chang (1): drm/i915: Avoid atomic context for error capture Chris Wilson (4): drm/i915: Flush context free work on cleanup drm/i915/fbdev: Restore physical addresses for fb_mmap() drm/i915/gt: Wait for new requests in intel_gt_retire_requests() drm/i915: Split i915_active.mutex into an irq-safe spinlock for the rbtree Don Hiatt (1): drm/i915/guc: Skip suspend/resume GuC action on platforms w/o GuC submission Imre Deak (2): drm/i915: Fix detection for a CMP-V PCH drm/i915: Restore GT coarse power gating workaround Jani Nikula (1): drm/i915: fix accidental static variable use Joonas Lahtinen (1): Merge tag 'gvt-next-fixes-2019-11-12' of https://github.com/intel/gvt-linux into drm-intel-next-fixes José Roberto de Souza (1): drm/i915/display: Fix TRANS_DDI_MST_TRANSPORT_SELECT definition Lionel Landwerlin (1): drm/i915/perf: don't forget noa wait after oa config Tina Zhang (1): drm/i915/gvt: Stop initializing pvinfo through reading mmio drivers/gpu/drm/i915/display/intel_fbdev.c | 9 +++-- drivers/gpu/drm/i915/display/intel_sprite.c | 2 +- drivers/gpu/drm/i915/gem/i915_gem_context.c | 1 + drivers/gpu/drm/i915/gt/intel_gt_requests.c | 11 ++---- drivers/gpu/drm/i915/gt/intel_rc6.c | 9 ++++- drivers/gpu/drm/i915/gt/uc/intel_guc.c | 15 ++++++++ drivers/gpu/drm/i915/gvt/handlers.c | 4 ++ drivers/gpu/drm/i915/i915_active.c | 57 ++++++++++++++--------------- drivers/gpu/drm/i915/i915_active_types.h | 1 + drivers/gpu/drm/i915/i915_drv.h | 6 +++ drivers/gpu/drm/i915/i915_gpu_error.c | 8 ++-- drivers/gpu/drm/i915/i915_perf.c | 9 ++++- drivers/gpu/drm/i915/i915_reg.h | 2 +- drivers/gpu/drm/i915/intel_pch.c | 6 ++- drivers/gpu/drm/i915/intel_pch.h | 2 +- 15 files changed, 89 insertions(+), 53 deletions(-) _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-11-20 20:40 UTC|newest] Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-20 20:40 Joonas Lahtinen [this message] 2019-11-20 20:40 ` [Intel-gfx] [PULL] drm-intel-next-fixes Joonas Lahtinen 2019-11-22 12:08 ` Joonas Lahtinen 2019-11-22 12:08 ` [Intel-gfx] " Joonas Lahtinen -- strict thread matches above, loose matches on Subject: below -- 2024-01-19 8:30 Joonas Lahtinen 2024-01-19 8:30 ` Joonas Lahtinen 2024-01-11 10:51 Joonas Lahtinen 2024-01-11 10:51 ` Joonas Lahtinen 2023-11-08 14:04 Jani Nikula 2023-11-10 15:48 ` Daniel Vetter 2023-08-31 21:28 Rodrigo Vivi 2023-08-24 12:34 Rodrigo Vivi 2023-07-06 8:24 Tvrtko Ursulin 2023-06-29 10:02 Tvrtko Ursulin 2023-06-21 9:54 Tvrtko Ursulin 2023-05-04 13:01 Joonas Lahtinen 2023-04-27 11:23 Joonas Lahtinen 2023-04-20 8:12 Joonas Lahtinen 2023-04-13 12:12 Joonas Lahtinen 2023-04-13 18:47 ` Daniel Vetter 2023-02-27 10:17 Jani Nikula 2023-02-17 12:24 Jani Nikula 2022-12-15 20:36 Rodrigo Vivi 2022-12-01 16:40 Rodrigo Vivi 2022-10-13 12:56 Tvrtko Ursulin 2022-10-06 10:18 Tvrtko Ursulin 2022-09-29 14:26 Tvrtko Ursulin 2022-08-11 21:03 Rodrigo Vivi 2022-08-04 17:33 Rodrigo Vivi 2022-05-24 13:59 Jani Nikula 2022-03-24 8:44 Tvrtko Ursulin 2022-03-17 7:47 Joonas Lahtinen 2022-03-10 7:58 Joonas Lahtinen 2022-01-20 10:13 Tvrtko Ursulin 2022-01-13 9:33 Tvrtko Ursulin 2022-01-14 13:23 ` Daniel Vetter 2021-11-09 23:17 Rodrigo Vivi 2021-08-26 9:03 Jani Nikula 2021-07-07 15:09 Rodrigo Vivi 2021-06-29 18:54 Rodrigo Vivi 2021-06-30 10:05 ` Jani Nikula 2021-06-30 19:04 ` Rodrigo Vivi 2021-07-01 8:57 ` Jani Nikula 2021-02-25 14:43 Rodrigo Vivi 2021-02-18 22:46 Rodrigo Vivi 2020-12-18 15:04 Jani Nikula 2020-12-18 15:42 ` Daniel Vetter 2020-10-22 20:56 Rodrigo Vivi 2020-10-15 18:14 Rodrigo Vivi 2020-10-02 18:26 Rodrigo Vivi 2020-07-30 16:26 Joonas Lahtinen 2020-08-10 7:31 ` Dave Airlie 2020-08-12 12:49 ` Jani Nikula 2020-06-10 9:37 Joonas Lahtinen 2020-06-10 11:19 ` Joonas Lahtinen 2020-06-04 15:04 Joonas Lahtinen 2020-05-28 14:40 Joonas Lahtinen 2020-05-20 12:32 Joonas Lahtinen 2020-04-08 21:59 Rodrigo Vivi 2020-04-02 21:30 Rodrigo Vivi 2020-03-27 8:16 Rodrigo Vivi 2019-12-05 9:24 Joonas Lahtinen 2019-11-28 14:15 Joonas Lahtinen 2019-11-22 15:55 Joonas Lahtinen 2019-11-14 8:52 Joonas Lahtinen 2019-11-07 14:50 Joonas Lahtinen 2019-09-27 19:49 Rodrigo Vivi 2019-09-19 14:16 Rodrigo Vivi 2019-09-11 23:33 Rodrigo Vivi 2019-05-15 7:48 Joonas Lahtinen 2019-05-09 10:01 Joonas Lahtinen 2019-05-02 13:40 Joonas Lahtinen 2019-04-30 7:08 Joonas Lahtinen 2019-04-25 6:13 Joonas Lahtinen 2019-03-12 20:55 Rodrigo Vivi 2018-12-27 7:40 Jani Nikula 2018-10-25 13:18 Joonas Lahtinen 2018-10-19 10:37 Joonas Lahtinen 2018-10-19 12:34 ` Daniel Vetter 2018-10-18 16:57 Joonas Lahtinen 2018-10-18 19:32 ` Daniel Vetter 2018-10-19 6:59 ` Joonas Lahtinen 2018-10-19 7:05 ` Daniel Vetter 2018-10-19 9:41 ` Joonas Lahtinen 2018-10-04 13:37 Joonas Lahtinen 2018-08-24 21:48 Rodrigo Vivi 2018-08-16 19:03 Rodrigo Vivi 2018-08-06 23:30 Rodrigo Vivi 2018-04-19 9:30 Joonas Lahtinen 2018-03-27 14:58 Joonas Lahtinen 2018-03-22 14:35 Joonas Lahtinen 2018-02-07 20:44 Rodrigo Vivi 2018-02-02 0:45 Rodrigo Vivi 2017-11-23 9:34 Jani Nikula 2017-11-10 13:21 Jani Nikula 2017-07-11 13:07 Jani Nikula 2017-06-27 8:28 Daniel Vetter 2017-02-17 9:46 Jani Nikula 2017-02-15 14:06 Jani Nikula 2016-12-22 10:22 Jani Nikula 2016-12-07 19:45 Jani Nikula 2016-10-11 14:09 Jani Nikula 2016-08-05 13:27 Jani Nikula 2016-07-25 6:41 Daniel Vetter 2016-05-25 8:57 Jani Nikula 2016-03-16 11:04 Jani Nikula 2016-01-14 20:06 Jani Nikula 2015-11-06 13:43 Jani Nikula 2015-10-22 8:28 Daniel Vetter 2015-09-02 11:49 Jani Nikula 2015-08-28 12:44 Jani Nikula 2015-08-16 18:13 Daniel Vetter 2015-07-02 11:26 Jani Nikula 2015-06-22 10:33 Jani Nikula 2015-06-18 6:04 Jani Nikula 2015-06-19 3:48 ` Dave Airlie 2015-06-19 15:24 ` Daniel Vetter 2015-06-22 7:59 ` Ander Conselvan De Oliveira 2015-06-22 8:12 ` Jani Nikula 2015-06-22 8:13 ` Dave Airlie 2015-06-11 8:40 Jani Nikula 2015-05-29 17:39 Daniel Vetter 2015-04-24 21:46 Jani Nikula 2015-04-15 12:21 Jani Nikula 2015-02-11 11:09 Jani Nikula 2015-02-11 11:48 ` Daniel Vetter 2014-12-30 12:47 Jani Nikula 2014-12-17 12:16 Jani Nikula 2014-12-11 13:43 Jani Nikula 2014-12-04 9:56 Daniel Vetter
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=20191120204035.GA14908@jlahtine-desk.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=rodrigo.vivi@intel.com \ --cc=sean@poorly.run \ /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.