From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: Remove early exit on i915_gpu_idle
Date: Sat, 15 Oct 2011 22:59:14 +0200 [thread overview]
Message-ID: <20111015205914.GC2819@phenom.ffwll.local> (raw)
In-Reply-To: <1318711636-30109-4-git-send-email-ben@bwidawsk.net>
On Sat, Oct 15, 2011 at 01:47:15PM -0700, Ben Widawsky wrote:
> [Description from: Daniel Vetter]
> I've just discussed this quickly with Chris on irc and it's probably
> best to just kill the list_empty early bailout. gpu_idle isn't a
> fastpath, so who cares. One candidate where we emit commands to the ring
> without adding anything onto these lists is e.g. pageflip. There are
> probably more.
>
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch> (for the commitmsg)
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-10-15 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-15 20:47 [PATCH v4 0/4] ILK VT-d fix Ben Widawsky
2011-10-15 20:47 ` [PATCH 1/4] intel-iommu: Workaround IOTLB hang on Ironlake GPU Ben Widawsky
2011-10-15 20:47 ` [PATCH 2/4] intel-iommu: Export a flag indicating that the IOMMU is used for iGFX Ben Widawsky
2011-10-15 20:47 ` [PATCH 3/4] drm/i915: Remove early exit on i915_gpu_idle Ben Widawsky
2011-10-15 20:59 ` Daniel Vetter [this message]
2011-10-15 22:10 ` Chris Wilson
2011-10-15 20:47 ` [PATCH 4/4] drm/i915: ILK + VT-d workaround Ben Widawsky
2011-10-15 21:15 ` Daniel Vetter
2011-10-15 22:09 ` Chris Wilson
[not found] ` <1319443974.13738.85.camel@shinybook.infradead.org>
2011-10-24 15:37 ` [PATCH v4 0/4] ILK VT-d fix Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2011-10-17 22:51 [PATCH 0/4] v5: ILK vt-d fix, more like v3 now Ben Widawsky
2011-10-17 22:51 ` [PATCH 3/4] drm/i915: Remove early exit on i915_gpu_idle Ben Widawsky
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=20111015205914.GC2819@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.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.