From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: chris@chris-wilson.co.uk, zbigniew.kempczynski@intel.com,
andi.shyti@intel.com, joonas.lahtinen@linux.intel.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/mm: revert "Break long searches in fragmented address spaces"
Date: Tue, 31 Mar 2020 10:59:45 +0200 [thread overview]
Message-ID: <c124b5d1-efc6-e826-2387-9f9ad06d1df0@gmail.com> (raw)
In-Reply-To: <20200330123425.3944-1-christian.koenig@amd.com>
A not so gentle ping, since this pretty much broke all TTM based drivers.
Could we revert this for now?
Thanks,
Christian.
Am 30.03.20 um 14:34 schrieb Christian König:
> This reverts commit 7be1b9b8e9d1e9ef0342d2e001f44eec4030aa4d.
>
> The drm_mm is supposed to work in atomic context, so calling schedule()
> or in this case cond_resched() is illegal.
>
> Signed-off-by: Christian König <christian.koenig@amd.com>
> ---
> drivers/gpu/drm/drm_mm.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c
> index bc6e208949e8..8981abe8b7c9 100644
> --- a/drivers/gpu/drm/drm_mm.c
> +++ b/drivers/gpu/drm/drm_mm.c
> @@ -45,7 +45,6 @@
> #include <linux/export.h>
> #include <linux/interval_tree_generic.h>
> #include <linux/seq_file.h>
> -#include <linux/sched/signal.h>
> #include <linux/slab.h>
> #include <linux/stacktrace.h>
>
> @@ -367,11 +366,6 @@ next_hole(struct drm_mm *mm,
> struct drm_mm_node *node,
> enum drm_mm_insert_mode mode)
> {
> - /* Searching is slow; check if we ran out of time/patience */
> - cond_resched();
> - if (fatal_signal_pending(current))
> - return NULL;
> -
> switch (mode) {
> default:
> case DRM_MM_INSERT_BEST:
> @@ -563,7 +557,7 @@ int drm_mm_insert_node_in_range(struct drm_mm * const mm,
> return 0;
> }
>
> - return signal_pending(current) ? -ERESTARTSYS : -ENOSPC;
> + return -ENOSPC;
> }
> EXPORT_SYMBOL(drm_mm_insert_node_in_range);
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-31 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 12:34 [PATCH] drm/mm: revert "Break long searches in fragmented address spaces" Christian König
2020-03-30 12:40 ` Chris Wilson
2020-03-31 8:59 ` Christian König [this message]
2020-03-31 9:16 ` Daniel Vetter
2020-03-31 9:20 ` Chris Wilson
2020-03-31 10:38 ` Daniel Vetter
2020-03-31 12:44 ` Christian König
2020-03-31 13:19 ` Chris Wilson
2020-04-01 7:29 ` Christian König
2020-04-01 8:53 ` Chris Wilson
2020-04-01 9:17 ` Christian König
2020-04-06 8:25 ` Christian König
2020-03-31 9:19 ` Chris Wilson
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=c124b5d1-efc6-e826-2387-9f9ad06d1df0@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=andi.shyti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=zbigniew.kempczynski@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).