From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
j.glisse@gmail.com, bskeggs@redhat.com, thellstrom@vmware.co,
airlied@linux.ie
Subject: [PATCH] fixes to drm-next - ttm code (v2) found when using nouveau.
Date: Wed, 4 Jan 2012 16:35:13 -0500 [thread overview]
Message-ID: <1325712916-27962-1-git-send-email-konrad.wilk@oracle.com> (raw)
When I was debugging some DMA API accounting error (which were found to be
with the DMA API debug code), I encountered a couple of issues:
1). Doing "unbind" on the PCI device would crash the kernel _only_ with the
nouveau driver. The readon worked fine. This was due to:
"drm/ttm: callback move_notify any time bo.." and reverting that fixed it.
2). Extreme slowness when moving the cursor madly around. This was due to the
nouveau driver calling the unpopulate (now that unbind + unpopulate are squashed)
quite a lot (this is using Gnome Shell - I think GNOME2 did not have those issues
but I can't recall). Radeon did not have these issues.
Anyhow these patches fix the 50% perf regression I saw on nouveau and also some minor bugs
that I noticed. Please apply.
Thomas asked me to also do some perf results on AGP hardware (both nouveau and radeon)
and I am going to do that this week - any pointers of what is a good game/OpenGL
application to run a time-based benchmark?
next reply other threads:[~2012-01-04 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 21:35 Konrad Rzeszutek Wilk [this message]
2012-01-04 21:35 ` [PATCH 1/3] drm/ttm/dma: Only call set_pages_array_wb when the page is not in WB pool Konrad Rzeszutek Wilk
2012-01-05 15:55 ` Jerome Glisse
2012-01-04 21:35 ` [PATCH 2/3] drm/ttm/dma: Fix accounting error when calling ttm_mem_global_free_page and don't try to free freed pages Konrad Rzeszutek Wilk
2012-01-04 21:35 ` [PATCH 3/3] Revert "drm/ttm: callback move_notify any time bo placement change v4" Konrad Rzeszutek Wilk
2012-01-05 18:29 ` Jerome Glisse
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=1325712916-27962-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thellstrom@vmware.co \
/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
all inboxes | Powered by JetHome®