From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: enable semaphores on gen6 if dmar is not active
Date: Wed, 9 May 2012 16:03:57 -0700 [thread overview]
Message-ID: <20120509160357.05e038e7@bwidawsk.net> (raw)
In-Reply-To: <1336603220-24531-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, 10 May 2012 00:40:20 +0200
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Inspired by the recent ppgtt regression report, where switching of
> dmar only for the gpu seems to fix things completely, I've looked
> again at the semaphores+vt-d situation.
>
> Contrary to my earlier testing a few months back my system is now
> stable with dmar disabled for the igd, and not only when disabling
> dmar completely.
>
> So I'm rather hopeful that all our recent fixes for snb have changed
> things for code and it's time to try enabling semaphores again. We've
> also had issues with enabling semaphores which are not vt-d related,
> but I guess these are all fixed by the autoreport-disabling and lazy
> request fix. And there's only one way to find out whether there are
> still other issues ...
>
> When I've tried to apply this patch I've noticed that semaphores on
> gen6 have already silently been added in
>
> commit 2911a35b2e4eb87ec48d03aeb11f019e51ae3c0d
> Author: Ben Widawsky <ben@bwidawsk.net>
> Date: Thu Apr 5 14:47:36 2012 -0700
>
> drm/i915: use semaphores for the display plane
>
> Fix this up by only checking whether dmar is enabled on the gfx (not
> on the entire system).
Heh. It wasn't on purpose! I want to blame this on git, but I honestly
don't know what happened.
>
> Cc: Ben Widawsky <ben@bwidawsk.net>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-Off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Reviewed-by: Ben Widawsky <ben@bwidawsk.net>
> ---
> drivers/gpu/drm/i915/i915_drv.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 77b7a50..1ccfc23 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -407,9 +407,11 @@ bool i915_semaphore_is_enabled(struct drm_device *dev)
> if (i915_semaphores >= 0)
> return i915_semaphores;
>
> +#ifdef CONFIG_INTEL_IOMMU
> /* Enable semaphores on SNB when IO remapping is off */
> - if (INTEL_INFO(dev)->gen == 6)
> - return !intel_iommu_enabled;
> + if (INTEL_INFO(dev)->gen == 6 && intel_iommu_gfx_mapped)
> + return false;
> +#endif
>
> return 1;
> }
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-05-09 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 22:40 [PATCH] drm/i915: enable semaphores on gen6 if dmar is not active Daniel Vetter
2012-05-09 23:03 ` Ben Widawsky [this message]
2012-05-10 8:35 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2012-04-02 18:48 Daniel Vetter
2012-04-02 20:45 ` [Intel-gfx] " Andrew Lutomirski
2012-04-02 20:52 ` Daniel Vetter
2012-04-02 21:44 ` Andrew Lutomirski
2012-04-02 22:32 ` [Intel-gfx] " Daniel Vetter
2012-04-17 9:31 ` Daniel Vetter
2012-04-27 17:54 ` Daniel Vetter
2012-05-05 12:55 ` Daniel Vetter
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=20120509160357.05e038e7@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox