From: Chris Wilson <chris@chris-wilson.co.uk>
To: John Harrigan <jfharrigan@fedex.com>, intel-gfx@lists.freedesktop.org
Subject: Re: slow graphics after Suspend to RAM
Date: Thu, 17 Mar 2011 07:51:38 +0000 [thread overview]
Message-ID: <1bdc18$jt7ta9@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <20110316235920.GA392@ink.rmtc.fedex.com>
On Wed, 16 Mar 2011 17:59:20 -0600, John Harrigan <jfharrigan@fedex.com> wrote:
> I have a Lenovo X201 laptop with an i7-620M processor. After I resume
> from a Suspend to RAM the graphics are very slow. Suspend to Disk does
> not cause the same problem and doing a Suspend to Disk after a Suspend
> to RAM fixes the problem.
Known problem. The PAT lose the WC bits for the GTT aperture on resume.
There is a workaround that we can do: recreate the ioremapping upon
resume. (But the root cause is not a gfx driver bug.)
> I see the same slow-down regardless of whether X11 is running or not.
> I'm not doing 3D, I notice the slow-down in regular 2D stuff like
> scrolling a lot of text through a terminal window.
That's not regular 2D stuff, that's CPU fallback! You will only see a
slight performance difference (an order of magnitude and more, with
comparable decrease in power consumption whilst drawing) by switching to
the XRender paths in your terminal.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-17 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 23:59 slow graphics after Suspend to RAM John Harrigan
2011-03-17 7:51 ` Chris Wilson [this message]
2011-03-17 15:32 ` John Harrigan
2011-04-13 13:11 ` John Harrigan
2011-03-18 18:44 ` Tino Keitel
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='1bdc18$jt7ta9@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jfharrigan@fedex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).