dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andyqos@ukfsn.org>
To: dri-devel@lists.sourceforge.net
Subject: Re: Problem with drm-radeon-testing commit - drm/ttm: Avoid conflicting reserve_memtype during ttm_tt_set_page_caching.
Date: Tue, 09 Feb 2010 16:18:14 +0000	[thread overview]
Message-ID: <4B718AC6.7080902@ukfsn.org> (raw)
In-Reply-To: <4B6CA4C7.1070301@ukfsn.org>

Andy Furniss wrote:

> db78e27de7e29a6db6be7caf607cf803d84094aa is first bad commit

I have confirmed by running both todays and yesterdays heads with and 
without that commit reverted that it is the one causing the problem.

Another test I tried was with agpmode=-1. This does avoid the problem, 
but unfortunately it is useless as a workaround for me as game perf 
other than openarena has always been poor using pcie gart.

eg. Nexuiz timedemo demos/demo1

KMS agpmode=4

result 1910 frames 70.4830000 seconds 27.0987330 fps, one-second fps 
min/avg/max: 19 28 47

KMS agpmode=-1 (or UMS with either gart)

result 1910 frames 254.2660000 seconds 7.5118183 fps, one-second fps 
min/avg/max: 4 10 36

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--

      reply	other threads:[~2010-02-09 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 23:07 Problem with drm-radeon-testing commit - drm/ttm: Avoid conflicting reserve_memtype during ttm_tt_set_page_caching Andy Furniss
2010-02-09 16:18 ` Andy Furniss [this message]

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=4B718AC6.7080902@ukfsn.org \
    --to=andyqos@ukfsn.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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