From: "Nicolas Kalkhof" <nkalkhof@web.de>
To: Andrew Lutomirski <luto@mit.edu>, Keith Packard <keithp@keithp.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
Eugeni Dodonov <eugeni.dodonov@intel.com>
Subject: Re: [PATCH 1/2] drm/i915: re-enable semaphores by default
Date: Wed, 16 Nov 2011 21:56:37 +0100 (CET) [thread overview]
Message-ID: <880599371.4875447.1321476997747.JavaMail.fmail@mwmweb002> (raw)
Not quite. On my i7 2620M (Lenovo T420) the gpu frequently hangs when decoding videos (vaapi) and running OpenGL apps/games at the same time. Disabling iommu makes my system relatively stable even with rc6 enabled. I haven't played with the semaphores however.
-- Nic
-----Ursprüngliche Nachricht-----
Von: "Andrew Lutomirski" <luto@mit.edu>
Gesendet: Nov 16, 2011 6:24:54 PM
An: "Keith Packard" <keithp@keithp.com>
Betreff: Re: [Intel-gfx] [PATCH 1/2] drm/i915: re-enable semaphores by default
>On Wed, Nov 16, 2011 at 9:16 AM, Keith Packard <keithp@keithp.com> wrote:
>> On Wed, 16 Nov 2011 16:49:40 +0100, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>>
>>> So we need to check whether DMAR is enabled (on the
>>> entire system, i.e. the variable exported for the ilk workaround is
>>> not good enough)
>>
>> Can you figure out what *would* be sufficient? Getting semaphores turned
>> on for the 99% who aren't enabling VT-d would be a fairly nice
>> performance improvement.
>
>AFAICT my snb laptop has always been stable with semaphores and VT-d
>enabled. Is this problem possibly restricted to just desktop
>machines? I'm happy to test, since my box that can reproduce the hang
>instantly is still around.
>
>Also, rc6-by-default would be very nice. It decreases the total power
>consumption on my laptop from over 13W to around 8W. That's huge.
>
>--Andy
>_______________________________________________
>Intel-gfx mailing list
>Intel-gfx@lists.freedesktop.org
>http://lists.freedesktop.org/mailman/listinfo/intel-gfx
___________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2011-11-16 20:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 20:56 Nicolas Kalkhof [this message]
2011-11-16 21:14 ` [PATCH 1/2] drm/i915: re-enable semaphores by default Daniel Vetter
2011-11-16 22:15 ` Keith Packard
-- strict thread matches above, loose matches on Subject: below --
2011-11-18 18:36 Nicolas Kalkhof
2011-11-17 18:31 Nicolas Kalkhof
2011-11-18 15:26 ` Daniel Vetter
2011-11-17 8:57 Nicolas Kalkhof
2011-11-17 9:22 ` Daniel Vetter
2011-11-22 5:41 ` Andrew Lutomirski
2011-11-22 11:23 ` Daniel Vetter
2011-11-29 16:39 ` Daniel Vetter
2011-11-14 20:39 Eugeni Dodonov
2011-11-14 21:23 ` Jesse Barnes
2011-11-16 15:49 ` Daniel Vetter
2011-11-16 17:16 ` Keith Packard
2011-11-16 17:24 ` Andrew Lutomirski
2011-11-16 19:05 ` Eugeni Dodonov
2011-11-16 19:23 ` Jesse Barnes
2011-11-16 20:18 ` Daniel Vetter
2011-11-16 21:37 ` Keith Packard
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=880599371.4875447.1321476997747.JavaMail.fmail@mwmweb002 \
--to=nkalkhof@web.de \
--cc=daniel.vetter@ffwll.ch \
--cc=eugeni.dodonov@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=luto@mit.edu \
/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