From: Jani Nikula <jani.nikula@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-fixes
Date: Thu, 28 Jan 2021 15:37:34 +0200 [thread overview]
Message-ID: <87y2gdi3mp.fsf@intel.com> (raw)
Hi Dave & Daniel -
Apparently there's a regression in -rc5 that affects a large portion of
the platforms in CI. See [1].
The issue showed up in -rc5 i.e. *before* the changes in this pull,
however the issue prevents getting full coverage [2]. It does not look
like this pull makes matters worse, but this does not make them better
either.
BR,
Jani.
[1] http://lore.kernel.org/r/871re5jiu3.fsf@intel.com
[2] https://intel-gfx-ci.01.org/tree/drm-intel-fixes/index.html?
drm-intel-fixes-2021-01-28:
drm/i915 fixes for v5.11-rc6:
- Fix ICL MG PHY vswing
- Fix subplatform handling
- Fix selftest memleak
- Clear CACHE_MODE prior to clearing residuals
- Always flush the active worker before returning from the wait
- Always try to reserve GGTT address 0x0
The following changes since commit 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04:
Linux 5.11-rc5 (2021-01-24 16:47:14 -0800)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-fixes-2021-01-28
for you to fetch changes up to 489140b5ba2e7cc4b853c29e0591895ddb462a82:
drm/i915/gt: Always try to reserve GGTT address 0x0 (2021-01-26 15:45:54 +0200)
----------------------------------------------------------------
drm/i915 fixes for v5.11-rc6:
- Fix ICL MG PHY vswing
- Fix subplatform handling
- Fix selftest memleak
- Clear CACHE_MODE prior to clearing residuals
- Always flush the active worker before returning from the wait
- Always try to reserve GGTT address 0x0
----------------------------------------------------------------
Chris Wilson (3):
drm/i915/gt: Clear CACHE_MODE prior to clearing residuals
drm/i915: Always flush the active worker before returning from the wait
drm/i915/gt: Always try to reserve GGTT address 0x0
Pan Bian (1):
drm/i915/selftest: Fix potential memory leak
Umesh Nerlige Ramappa (1):
drm/i915: Check for all subplatform bits
Ville Syrjälä (1):
drm/i915: Fix ICL MG PHY vswing handling
drivers/gpu/drm/i915/display/intel_ddi.c | 7 ++--
drivers/gpu/drm/i915/gt/gen7_renderclear.c | 12 +++++++
drivers/gpu/drm/i915/gt/intel_ggtt.c | 47 ++++++++++++++++++++-------
drivers/gpu/drm/i915/i915_active.c | 28 ++++++++--------
drivers/gpu/drm/i915/i915_drv.h | 2 +-
drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 2 +-
6 files changed, 67 insertions(+), 31 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@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-fixes
Date: Thu, 28 Jan 2021 15:37:34 +0200 [thread overview]
Message-ID: <87y2gdi3mp.fsf@intel.com> (raw)
Hi Dave & Daniel -
Apparently there's a regression in -rc5 that affects a large portion of
the platforms in CI. See [1].
The issue showed up in -rc5 i.e. *before* the changes in this pull,
however the issue prevents getting full coverage [2]. It does not look
like this pull makes matters worse, but this does not make them better
either.
BR,
Jani.
[1] http://lore.kernel.org/r/871re5jiu3.fsf@intel.com
[2] https://intel-gfx-ci.01.org/tree/drm-intel-fixes/index.html?
drm-intel-fixes-2021-01-28:
drm/i915 fixes for v5.11-rc6:
- Fix ICL MG PHY vswing
- Fix subplatform handling
- Fix selftest memleak
- Clear CACHE_MODE prior to clearing residuals
- Always flush the active worker before returning from the wait
- Always try to reserve GGTT address 0x0
The following changes since commit 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04:
Linux 5.11-rc5 (2021-01-24 16:47:14 -0800)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-fixes-2021-01-28
for you to fetch changes up to 489140b5ba2e7cc4b853c29e0591895ddb462a82:
drm/i915/gt: Always try to reserve GGTT address 0x0 (2021-01-26 15:45:54 +0200)
----------------------------------------------------------------
drm/i915 fixes for v5.11-rc6:
- Fix ICL MG PHY vswing
- Fix subplatform handling
- Fix selftest memleak
- Clear CACHE_MODE prior to clearing residuals
- Always flush the active worker before returning from the wait
- Always try to reserve GGTT address 0x0
----------------------------------------------------------------
Chris Wilson (3):
drm/i915/gt: Clear CACHE_MODE prior to clearing residuals
drm/i915: Always flush the active worker before returning from the wait
drm/i915/gt: Always try to reserve GGTT address 0x0
Pan Bian (1):
drm/i915/selftest: Fix potential memory leak
Umesh Nerlige Ramappa (1):
drm/i915: Check for all subplatform bits
Ville Syrjälä (1):
drm/i915: Fix ICL MG PHY vswing handling
drivers/gpu/drm/i915/display/intel_ddi.c | 7 ++--
drivers/gpu/drm/i915/gt/gen7_renderclear.c | 12 +++++++
drivers/gpu/drm/i915/gt/intel_ggtt.c | 47 ++++++++++++++++++++-------
drivers/gpu/drm/i915/i915_active.c | 28 ++++++++--------
drivers/gpu/drm/i915/i915_drv.h | 2 +-
drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 2 +-
6 files changed, 67 insertions(+), 31 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2021-01-28 13:37 UTC|newest]
Thread overview: 169+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 13:37 Jani Nikula [this message]
2021-01-28 13:37 ` [PULL] drm-intel-fixes Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 9:28 [Intel-gfx] " Jani Nikula
2023-11-30 14:58 Jani Nikula
2023-11-30 19:41 ` Ville Syrjälä
2023-11-23 16:34 Jani Nikula
2023-10-26 14:48 Rodrigo Vivi
2023-10-19 16:21 Rodrigo Vivi
2023-10-05 14:14 Rodrigo Vivi
2023-09-28 14:22 Rodrigo Vivi
2023-09-21 15:23 Rodrigo Vivi
2023-09-14 12:36 Rodrigo Vivi
2023-08-24 12:38 Rodrigo Vivi
2023-08-17 14:45 Rodrigo Vivi
2023-08-03 8:26 Tvrtko Ursulin
2023-07-27 9:26 Tvrtko Ursulin
2023-07-20 8:22 Tvrtko Ursulin
2023-07-13 7:26 Tvrtko Ursulin
2023-06-08 8:44 Maarten Lankhorst
2023-06-08 8:41 Joonas Lahtinen
2023-06-01 14:09 Joonas Lahtinen
2023-05-25 12:53 Joonas Lahtinen
2023-05-25 13:00 ` Jani Nikula
2023-05-24 11:40 Maarten Lankhorst
2023-05-24 12:57 ` Rodrigo Vivi
2023-05-17 18:44 Joonas Lahtinen
2023-05-11 12:19 Joonas Lahtinen
2023-04-19 9:19 Jani Nikula
2023-04-13 7:13 Jani Nikula
2023-04-13 13:08 ` Daniel Vetter
2023-04-05 9:04 Jani Nikula
2023-04-05 9:39 ` Daniel Vetter
2023-03-30 11:30 Jani Nikula
2023-03-30 16:26 ` Daniel Vetter
2023-03-23 10:46 Jani Nikula
2023-03-24 9:23 ` Daniel Vetter
2023-03-15 10:05 Jani Nikula
2023-02-16 14:19 Rodrigo Vivi
2023-02-09 16:05 Rodrigo Vivi
2023-02-02 13:24 Rodrigo Vivi
2023-01-26 18:44 Rodrigo Vivi
2023-01-19 19:54 Rodrigo Vivi
2023-01-12 14:37 Rodrigo Vivi
2023-01-05 20:02 Rodrigo Vivi
2023-01-06 17:30 ` Daniel Vetter
2022-12-30 9:59 Rodrigo Vivi
2023-01-01 11:01 ` Daniel Vetter
2022-12-01 8:46 Tvrtko Ursulin
2022-11-24 8:44 Tvrtko Ursulin
2022-11-17 8:54 Tvrtko Ursulin
2022-11-10 9:22 Tvrtko Ursulin
2022-11-03 9:03 Tvrtko Ursulin
2022-10-27 8:17 Tvrtko Ursulin
2022-09-29 15:58 Rodrigo Vivi
2022-09-21 20:33 Rodrigo Vivi
2022-09-15 13:50 Rodrigo Vivi
2022-09-08 13:59 Rodrigo Vivi
2022-09-11 17:22 ` Jason A. Donenfeld
2022-09-12 14:03 ` Vivi, Rodrigo
2022-09-01 13:49 Rodrigo Vivi
2022-08-26 12:53 Rodrigo Vivi
2022-07-28 8:27 Tvrtko Ursulin
2022-07-20 15:35 Rodrigo Vivi
2022-07-17 18:59 Rodrigo Vivi
2022-07-17 20:30 ` pr-tracker-bot
2022-07-13 21:40 Rodrigo Vivi
2022-07-07 13:11 Rodrigo Vivi
2022-06-29 10:46 Jani Nikula
2022-06-22 11:50 Jani Nikula
2022-06-16 7:49 Jani Nikula
2022-05-20 5:44 Joonas Lahtinen
2022-05-19 5:51 Joonas Lahtinen
2022-05-12 6:08 Joonas Lahtinen
2022-04-28 6:01 Joonas Lahtinen
2022-04-20 13:29 Joonas Lahtinen
2022-04-13 5:58 Joonas Lahtinen
2022-03-10 10:30 Tvrtko Ursulin
2022-03-03 10:23 Tvrtko Ursulin
2022-02-24 11:55 Tvrtko Ursulin
2022-02-17 10:35 Tvrtko Ursulin
2022-02-10 10:52 Tvrtko Ursulin
2022-02-03 9:37 Joonas Lahtinen
2021-12-29 11:30 Jani Nikula
2021-12-22 13:29 Jani Nikula
2021-12-15 10:43 Rodrigo Vivi
2021-12-09 19:13 Rodrigo Vivi
2021-12-02 19:35 Rodrigo Vivi
2021-11-24 22:15 Rodrigo Vivi
2021-11-18 22:31 Rodrigo Vivi
2021-10-28 10:29 Jani Nikula
2021-10-28 13:20 ` Ville Syrjälä
2021-10-28 14:33 ` Jani Nikula
2021-10-14 14:14 Jani Nikula
2021-10-07 10:08 Jani Nikula
2021-09-30 8:50 Jani Nikula
2021-10-01 14:59 ` Daniel Vetter
2021-09-23 11:35 Jani Nikula
2021-09-16 13:30 Jani Nikula
2021-08-26 17:42 Rodrigo Vivi
2021-08-18 21:13 Rodrigo Vivi
2021-08-12 15:34 Rodrigo Vivi
2021-08-04 18:31 Rodrigo Vivi
2021-07-28 15:42 Rodrigo Vivi
2021-07-22 13:42 Rodrigo Vivi
2021-07-15 13:48 Rodrigo Vivi
2021-06-24 8:17 Jani Nikula
2021-06-03 8:37 Jani Nikula
2021-05-27 8:13 Jani Nikula
2021-05-20 11:57 Jani Nikula
2021-05-14 6:19 Jani Nikula
2021-04-22 15:44 Rodrigo Vivi
2021-04-15 12:59 Rodrigo Vivi
2021-04-15 13:24 ` Daniel Vetter
2021-04-09 8:57 Rodrigo Vivi
2021-03-25 9:31 Rodrigo Vivi
2021-03-18 12:05 Jani Nikula
2021-03-11 11:28 Rodrigo Vivi
2021-03-12 1:36 ` Dave Airlie
2021-03-12 2:57 ` Rodrigo Vivi
2021-02-11 8:56 Jani Nikula
2021-02-04 12:06 Jani Nikula
2021-01-21 16:49 Jani Nikula
2021-01-14 10:54 Jani Nikula
2021-01-07 7:50 Jani Nikula
2021-01-07 9:28 ` Daniel Vetter
2020-12-09 23:50 Rodrigo Vivi
2020-12-03 0:36 Rodrigo Vivi
2020-12-03 1:07 ` Rodrigo Vivi
2020-11-26 1:06 Rodrigo Vivi
2020-11-19 20:34 Rodrigo Vivi
2020-11-13 5:25 Rodrigo Vivi
2020-11-12 23:09 Rodrigo Vivi
2020-11-13 0:32 ` Dave Airlie
2020-11-13 0:47 ` Vivi, Rodrigo
2020-11-05 17:30 Rodrigo Vivi
2020-10-30 0:44 Rodrigo Vivi
2020-09-24 9:12 Jani Nikula
2020-09-17 8:45 Jani Nikula
2020-09-10 7:48 Jani Nikula
2020-09-03 9:08 Jani Nikula
2020-08-27 9:06 Jani Nikula
2020-08-20 9:25 Jani Nikula
2020-07-15 13:08 Jani Nikula
2020-07-08 19:06 Rodrigo Vivi
2020-07-01 13:19 Jani Nikula
2020-06-18 12:46 Joonas Lahtinen
2020-05-28 18:59 Rodrigo Vivi
2020-05-14 4:02 Rodrigo Vivi
2020-05-08 5:24 Rodrigo Vivi
2020-04-30 14:00 Rodrigo Vivi
2020-04-23 19:02 Rodrigo Vivi
2020-04-15 20:03 Rodrigo Vivi
2020-03-19 7:59 Jani Nikula
2020-03-12 6:08 Jani Nikula
2020-03-05 10:35 Jani Nikula
2020-02-27 6:04 Jani Nikula
2020-02-20 11:14 Jani Nikula
2020-01-23 13:50 Joonas Lahtinen
2020-01-16 16:14 Joonas Lahtinen
2020-01-09 13:34 Joonas Lahtinen
2020-01-09 13:39 ` Joonas Lahtinen
2019-12-23 16:55 Jani Nikula
2019-12-19 12:46 Joonas Lahtinen
2019-12-23 15:06 ` Chris Wilson
2019-12-12 10:07 Joonas Lahtinen
2019-11-21 16:53 Rodrigo Vivi
2019-11-21 16:53 ` Rodrigo Vivi
2019-11-14 5:53 Rodrigo Vivi
2019-11-14 5:53 ` Rodrigo Vivi
2019-11-06 21:39 Rodrigo Vivi
2019-11-06 21:39 ` Rodrigo Vivi
2019-10-31 17:12 Rodrigo Vivi
2019-10-31 17:12 ` Rodrigo Vivi
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=87y2gdi3mp.fsf@intel.com \
--to=jani.nikula@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 \
/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: link
Be 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.