From: Chris Wilson <chris@chris-wilson.co.uk>
To: Keith Packard <keithp@keithp.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Busy-spin wait_for condition in atomic contexts
Date: Fri, 25 Mar 2011 08:34:46 +0000 [thread overview]
Message-ID: <b7da2f$qrtah2@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <yunlj04rq47.fsf@aiko.keithp.com>
On Thu, 24 Mar 2011 17:38:32 -0700, Keith Packard <keithp@keithp.com> wrote:
> On Thu, 24 Mar 2011 19:55:59 +0000, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> > - if (W && !in_dbg_master()) msleep(W); \
> > + if (W && !(in_dbg_master() || in_atomic())) msleep(W); \
>
> If the MSLEEP macro were ever used, would it need the same fix?
Not yet. There are places where we should be using it though I think, It
just requires inspecting each of the callpaths and seeing if we might be
called from an atomic modeswitch.
> wait_for_atomic is never used, so perhaps the _wait_for macro should
> just be renamed wait_for and the W hard-coded to 1.
A bit of over-engineering. I want to propose these as part of the core
kernel interface and so tried to cover all the bases. But I'm not sure if
they are actually clean enough to pass muster nor if anybody else is
interested in them.
> As a simple fix though,
>
> Reviewed-by: Keith Packard <keithp@keithp.com>
Indeed, a fix should limit itself to the bug described. Every else is an
enhancement...
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-25 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 19:55 [PATCH] drm/i915: Busy-spin wait_for condition in atomic contexts Chris Wilson
2011-03-25 0:38 ` Keith Packard
2011-03-25 8:34 ` Chris Wilson [this message]
2011-03-25 18:30 ` Jesse Barnes
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='b7da2f$qrtah2@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.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.