From: Thomas Hellstrom <thellstrom@vmware.com>
To: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/5][-next] TTM bo reservation and fencing improvements
Date: Wed, 17 Nov 2010 18:44:51 +0100 [thread overview]
Message-ID: <4CE41493.7010906@vmware.com> (raw)
In-Reply-To: <AANLkTimJKG8c-D7=yuTQZOmO-9o+j03WPzsTTh=V6c3a@mail.gmail.com>
On 11/17/2010 05:40 PM, Sedat Dilek wrote:
> Against which GIT tree is this patchset, against latest drm-next GIT they fail?
> Missing a patch or patchset?
>
On top of drm-next you first need to apply
drm/ttm: Fix up a theoretical deadlock.
drm/ttm: Add a bo list reserve fastpath (need v2 which was recently posted)
kref: Add a kref_sub function
drm/ttm: Use kref_sub instead of repeatedly...
/Thomas
> - Sedat -
>
> $ cd /mnt/sdb5/linux-kernel/drm-2.6
>
> $ git branch
> * drm-next
> master
>
> $ git describe
> v2.6.34-rc5-32040-g01d5a1f
>
> $ cat patches/series
> drm-ttm-next/1-5-drm-ttm-Optimize-ttm_eu_backoff_reservation.patch
> drm-ttm-next/2-5-drm-ttm-Don-t-deadlock-on-recursive-multi-bo-reservations.patch
> drm-ttm-next/3-5-drm-ttm-radeon-nouveau-Kill-the-bo-lock-in-favour-of-a-bo-device-fence_lock.patch
> drm-ttm-next/4-5-drm-ttm-Improved-fencing-of-buffer-object-lists.patch
> drm-ttm-next/5-5-drm-ttm-vmwgfx-Have-TTM-manage-the-validation-sequence..patch
> drm-ttm-next/1-1-drm-radeon-Use-the-ttm-execbuf-utilities.patch
>
> $ quilt -f push
> Wende Patch drm-ttm-next/1-5-drm-ttm-Optimize-ttm_eu_backoff_reservation.patch
> an
> patching file drivers/gpu/drm/ttm/ttm_execbuf_util.c
> Hunk #1 succeeded at 35 (offset -64 lines).
>
> Jetzt in Patch drm-ttm-next/1-5-drm-ttm-Optimize-ttm_eu_backoff_reservation.patch
> $ quilt -f push
> Wende Patch drm-ttm-next/2-5-drm-ttm-Don-t-deadlock-on-recursive-multi-bo-reservations.patch
> an
> patching file drivers/gpu/drm/ttm/ttm_bo.c
> Hunk #1 FAILED at 223.
> 1 out of 1 hunk FAILED -- saving rejects to file
> drivers/gpu/drm/ttm/ttm_bo.c.rej
> patching file include/drm/ttm/ttm_bo_driver.h
> Hunk #2 FAILED at 871.
> 1 out of 2 hunks FAILED -- saving rejects to file
> include/drm/ttm/ttm_bo_driver.h.rej
> Patch drm-ttm-next/2-5-drm-ttm-Don-t-deadlock-on-recursive-multi-bo-reservations.patch
> angewandt (erzwungen, muss aktualisiert werden (Refresh))
>
next prev parent reply other threads:[~2010-11-17 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:40 [PATCH 0/5][-next] TTM bo reservation and fencing improvements Sedat Dilek
2010-11-17 17:44 ` Thomas Hellstrom [this message]
2010-11-17 20:17 ` Sedat Dilek
2010-11-17 22:42 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2010-11-17 12:28 Thomas Hellstrom
2010-11-17 19:07 ` 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=4CE41493.7010906@vmware.com \
--to=thellstrom@vmware.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.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 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.