From: Daniel Vetter <daniel@ffwll.ch> To: Maxime Ripard <maxime@cerno.tech> Cc: dim-tools@lists.freedesktop.org, Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org, Maxime Ripard <mripard@kernel.org>, Thomas Zimmermann <tzimmermann@suse.de>, Rodrigo Vivi <rodrigo.vivi@intel.com>, Dave Airlie <airlied@gmail.com>, intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] [PULL] drm-misc-next-fixes Date: Tue, 3 Jan 2023 21:03:27 +0100 [thread overview] Message-ID: <Y7SKDwg6ot78I4Bp@phenom.ffwll.local> (raw) In-Reply-To: <20230103144926.bmjjni3xnuis2jmq@houat> On Tue, Jan 03, 2023 at 03:49:26PM +0100, Maxime Ripard wrote: > Hi Daniel, Dave, > > Here's the drm-misc-next-fixes leftovers. > > Maxime > > drm-misc-next-fixes-2023-01-03: > The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler > ending up causing a lockup, and reduces the stack usage of some drm/mm > kunit tests. > The following changes since commit b02897e56b4e1fa6445be695ce5d605bb098435c: > > Revert "drm/fb-helper: Perform damage handling in deferred-I/O helper" (2022-11-23 09:11:32 +0100) > > are available in the Git repository at: > > git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-fixes-2023-01-03 Thanks, pulled. -Daniel > > for you to fetch changes up to 03dec92c4f788c54a7c01b40a018f601eb8a6c52: > > drm/scheduler: Fix lockup in drm_sched_entity_kill() (2023-01-02 17:45:18 +0300) > > ---------------------------------------------------------------- > The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler > ending up causing a lockup, and reduces the stack usage of some drm/mm > kunit tests. > > ---------------------------------------------------------------- > Arnd Bergmann (1): > drm/tests: reduce drm_mm_test stack usage > > Dmitry Osipenko (1): > drm/scheduler: Fix lockup in drm_sched_entity_kill() > > drivers/gpu/drm/scheduler/sched_entity.c | 2 +- > drivers/gpu/drm/scheduler/sched_main.c | 4 ++-- > drivers/gpu/drm/tests/Makefile | 2 ++ > drivers/gpu/drm/tests/drm_mm_test.c | 6 +++--- > 4 files changed, 8 insertions(+), 6 deletions(-) -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch> To: Maxime Ripard <maxime@cerno.tech> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>, dim-tools@lists.freedesktop.org, Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org, Thomas Zimmermann <tzimmermann@suse.de>, Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org Subject: Re: [PULL] drm-misc-next-fixes Date: Tue, 3 Jan 2023 21:03:27 +0100 [thread overview] Message-ID: <Y7SKDwg6ot78I4Bp@phenom.ffwll.local> (raw) In-Reply-To: <20230103144926.bmjjni3xnuis2jmq@houat> On Tue, Jan 03, 2023 at 03:49:26PM +0100, Maxime Ripard wrote: > Hi Daniel, Dave, > > Here's the drm-misc-next-fixes leftovers. > > Maxime > > drm-misc-next-fixes-2023-01-03: > The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler > ending up causing a lockup, and reduces the stack usage of some drm/mm > kunit tests. > The following changes since commit b02897e56b4e1fa6445be695ce5d605bb098435c: > > Revert "drm/fb-helper: Perform damage handling in deferred-I/O helper" (2022-11-23 09:11:32 +0100) > > are available in the Git repository at: > > git://anongit.freedesktop.org/drm/drm-misc tags/drm-misc-next-fixes-2023-01-03 Thanks, pulled. -Daniel > > for you to fetch changes up to 03dec92c4f788c54a7c01b40a018f601eb8a6c52: > > drm/scheduler: Fix lockup in drm_sched_entity_kill() (2023-01-02 17:45:18 +0300) > > ---------------------------------------------------------------- > The drm-misc-next-fixes leftovers. It addresses a bug in drm/scheduler > ending up causing a lockup, and reduces the stack usage of some drm/mm > kunit tests. > > ---------------------------------------------------------------- > Arnd Bergmann (1): > drm/tests: reduce drm_mm_test stack usage > > Dmitry Osipenko (1): > drm/scheduler: Fix lockup in drm_sched_entity_kill() > > drivers/gpu/drm/scheduler/sched_entity.c | 2 +- > drivers/gpu/drm/scheduler/sched_main.c | 4 ++-- > drivers/gpu/drm/tests/Makefile | 2 ++ > drivers/gpu/drm/tests/drm_mm_test.c | 6 +++--- > 4 files changed, 8 insertions(+), 6 deletions(-) -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
next prev parent reply other threads:[~2023-01-03 20:03 UTC|newest] Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-03 14:49 [PULL] drm-misc-next-fixes Maxime Ripard 2023-01-03 14:49 ` [Intel-gfx] " Maxime Ripard 2023-01-03 20:03 ` Daniel Vetter [this message] 2023-01-03 20:03 ` Daniel Vetter -- strict thread matches above, loose matches on Subject: below -- 2023-11-02 13:31 [Intel-gfx] " Maarten Lankhorst 2023-09-11 14:19 Thomas Zimmermann 2023-09-01 7:01 Thomas Zimmermann 2023-08-24 18:12 Thomas Zimmermann 2023-08-17 13:18 Thomas Zimmermann 2023-07-06 11:31 Thomas Zimmermann 2023-06-29 11:38 Thomas Zimmermann 2023-06-15 11:40 Thomas Zimmermann 2023-04-26 6:04 Maarten Lankhorst 2023-02-28 9:13 Thomas Zimmermann 2023-02-23 18:25 Maarten Lankhorst 2023-02-23 18:48 ` Maxime Ripard 2023-02-21 12:36 Thomas Zimmermann 2023-02-16 10:39 Thomas Zimmermann 2023-02-09 9:17 Thomas Zimmermann 2023-02-02 8:14 Thomas Zimmermann 2022-12-08 8:40 Maxime Ripard 2022-08-10 10:41 Thomas Zimmermann 2022-07-21 7:06 Thomas Zimmermann 2022-07-14 14:09 Thomas Zimmermann 2022-05-19 8:05 Maxime Ripard 2022-04-07 10:56 Maarten Lankhorst 2022-04-07 11:52 ` Maxime Ripard 2022-03-24 13:18 Maarten Lankhorst 2022-03-24 13:15 Maarten Lankhorst 2022-01-21 8:27 Thomas Zimmermann 2022-01-14 14:24 Thomas Zimmermann 2022-01-14 15:39 ` Daniel Vetter 2022-01-13 8:29 Thomas Zimmermann 2022-01-14 13:24 ` Daniel Vetter 2021-12-23 9:23 Thomas Zimmermann 2021-11-10 8:21 Maxime Ripard 2021-11-05 7:43 Maxime Ripard 2021-09-09 8:25 Maarten Lankhorst 2021-09-03 9:38 Maarten Lankhorst 2021-07-01 9:08 Thomas Zimmermann 2021-06-24 7:16 Thomas Zimmermann 2021-06-18 8:58 Thomas Zimmermann 2021-06-16 18:30 Thomas Zimmermann 2021-06-18 2:26 ` Dave Airlie 2021-06-18 2:30 ` Dave Airlie 2021-06-18 8:58 ` Daniel Vetter 2021-06-18 2:30 ` Lyude Paul 2021-05-06 12:27 Maxime Ripard 2021-04-29 9:03 Maxime Ripard 2021-04-22 16:33 Maxime Ripard 2021-04-22 16:40 ` Alex Deucher 2021-04-26 7:35 ` Maxime Ripard 2021-04-28 20:57 ` Alex Deucher 2021-04-29 9:32 ` Maxime Ripard 2021-02-25 9:25 Maarten Lankhorst 2021-02-11 15:44 Maarten Lankhorst 2020-12-22 19:13 Thomas Zimmermann 2021-01-04 8:05 ` Thomas Zimmermann 2020-12-15 13:04 Thomas Zimmermann 2020-12-15 16:27 ` Daniel Vetter 2020-10-20 14:14 Maxime Ripard 2020-10-13 6:57 Maxime Ripard 2020-10-09 7:53 Maxime Ripard 2020-10-02 6:52 Maxime Ripard 2020-08-05 10:00 Maarten Lankhorst 2020-06-11 7:50 Thomas Zimmermann 2020-05-27 8:01 Thomas Zimmermann 2020-04-09 9:14 Maxime Ripard 2020-04-04 9:00 Maxime Ripard 2020-03-26 13:04 Maxime Ripard 2020-02-07 9:43 Maarten Lankhorst 2019-12-12 14:04 Sean Paul 2019-12-04 21:22 Sean Paul 2019-11-20 20:49 Sean Paul 2019-11-20 20:49 ` Sean Paul 2019-11-13 21:10 Sean Paul 2019-11-13 21:10 ` Sean Paul 2019-11-06 20:27 Sean Paul 2019-11-06 20:27 ` Sean Paul
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=Y7SKDwg6ot78I4Bp@phenom.ffwll.local \ --to=daniel@ffwll.ch \ --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=maxime@cerno.tech \ --cc=mripard@kernel.org \ --cc=rodrigo.vivi@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.