From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: merge window closed
Date: Thu, 5 Jan 2012 21:24:05 -0500 [thread overview]
Message-ID: <20120106022405.GC3120@phenom.dumpdata.com> (raw)
In-Reply-To: <CAPM=9tyH3twQ8xNLySjgYxP1+oyxR0r6o-9LP+b=Gj5v+nx0Vw@mail.gmail.com>
On Thu, Jan 05, 2012 at 10:48:10AM +0000, Dave Airlie wrote:
> Hi
>
> So Linus has released, so really whats in -next is really it
>
> I've two things outstanding,
> the TTM/AGP fixes, from Jerome/Konrad, guys please cross-review asap,
OK, so the two I posted:
drm/ttm/dma: Fix accounting error when calling ttm_mem_global_free_page and don't try to free freed pages.
drm/ttm/dma: Only call set_pages_array_wb when the page is not in WB pool
Should go in. Jerome took a look at both of them and Reviewed them.
He has also posted:
ttm: fix agp since ttm tt rework
which looks OK to me and should have the Reviewed-by me flag stuck on. Let
me respond to Jerome's email on that.
Now on the move_notify work, that still does not work properly with nouveau.
Ben did some work with ""drm/nouveau/ttm: fix crash as a result of a recent ttm change"
but I can still get the machine to crash so will have to dig on this a bit more.
> I'm not sure there isn't some speed regressions in there, hopefully
> some more digging can be done.
The "drm/ttm/dma: Only call set_pages_array_wb when the page is not in WB pool"
fixes it in the TTM DMA code. The older TTM (non-DMA) did not have those issues
so that is good.
I did not see any perf regression in the AGP case using radeon. Haven't yet
run the nouveau AGP one yet. Will do that tomorrow barring the move_notify bugs..
next prev parent reply other threads:[~2012-01-06 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 10:48 merge window closed Dave Airlie
2012-01-06 2:24 ` Konrad Rzeszutek Wilk [this message]
2012-01-06 10:10 ` Dave Airlie
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=20120106022405.GC3120@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=airlied@gmail.com \
--cc=dri-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.