From: Chris Wilson <chris@chris-wilson.co.uk>
To: Christian König <ckoenig.leichtzumerken@gmail.com>,
andi.shyti@intel.com, dri-devel@lists.freedesktop.org,
joonas.lahtinen@linux.intel.com, zbigniew.kempczynski@intel.com
Subject: Re: [PATCH] drm/mm: revert "Break long searches in fragmented address spaces"
Date: Mon, 30 Mar 2020 13:40:42 +0100 [thread overview]
Message-ID: <158557204261.3228.10264756093485370990@build.alporthouse.com> (raw)
In-Reply-To: <20200330123425.3944-1-christian.koenig@amd.com>
Quoting Christian König (2020-03-30 13:34:25)
> 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.
https://patchwork.freedesktop.org/patch/358535/?series=74984&rev=1
(Though I do question the wisdom in searching, rather than just doing a
cursory check, from an atomic context :)
-Chris
_______________________________________________
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-30 12:40 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 [this message]
2020-03-31 8:59 ` Christian König
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=158557204261.3228.10264756093485370990@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=andi.shyti@intel.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--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 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.