From: Thomas Hellstrom <thellstrom@vmware.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Jerome Glisse <jglisse@redhat.com>,
"skeggsb@gmail.com" <skeggsb@gmail.com>,
"dri-devel@lists.sf.net" <dri-devel@lists.sf.net>
Subject: Re: Unmappable VRAM patchset V4
Date: Mon, 01 Mar 2010 13:03:38 +0100 [thread overview]
Message-ID: <4B8BAD1A.7020600@vmware.com> (raw)
In-Reply-To: <21d7e9971002282144w59b0a235q75615c9fedf72af6@mail.gmail.com>
Dave Airlie wrote:
> On Fri, Feb 26, 2010 at 3:01 AM, Jerome Glisse <jglisse@redhat.com> wrote:
>
>> Updated patchset, to apply cleanly on top of TTM split no_wait argument.
>> Compile tested for nouveau+vmwgfx, test in progress for radeon.
>>
>> So with the new change radeon won't wait for bo reserving other bo
>> in fault path but will wait the GPU (hoping it doesn't lockup ;))
>> This should address concern about the wait/locking issue.
>>
>
> Thomas any time for this yet? I'd like to pull this in obviously, but
> it would be nice to know if Jerome has addressed all concerns.
>
> Dave.
>
Hi Dave!
My schedule is currently a bit tight. I think the immediate deadlock
concerns are met, but I'd to take a deeper look at some things that look
a bit suspicious, but I think the overall approach is ok.
I'll hopefully be able to do a review on wednesday.
/Thomas
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-03-01 12:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 17:01 Unmappable VRAM patchset V4 Jerome Glisse
2010-02-25 17:01 ` [PATCH 1/9] drm/ttm: ttm_fault callback to allow driver to handle bo placement V2 Jerome Glisse
2010-02-25 17:01 ` [PATCH 2/9] drm/radeon/kms: add support for new fault callback V3 Jerome Glisse
2010-02-25 17:01 ` [PATCH 3/9] drm/nouveau/kms: add support for new TTM fault callback V2 Jerome Glisse
2010-02-25 17:01 ` [PATCH 4/9] drm/vmwgfx: " Jerome Glisse
2010-02-25 17:01 ` [PATCH 5/9] drm/radeon/kms: don't initialize TTM io memory manager field Jerome Glisse
2010-02-25 17:01 ` [PATCH 6/9] drm/nouveau/kms: " Jerome Glisse
2010-02-25 17:01 ` [PATCH 7/9] drm/vmwgfx: " Jerome Glisse
2010-02-25 17:01 ` [PATCH 8/9] drm/ttm: remove io_ field from TTM V2 Jerome Glisse
2010-02-25 17:01 ` [PATCH 9/9] drm/radeon/kms: enable use of unmappable VRAM Jerome Glisse
2010-03-01 5:44 ` Unmappable VRAM patchset V4 Dave Airlie
2010-03-01 12:03 ` Thomas Hellstrom [this message]
2010-03-17 10:05 ` Jerome Glisse
2010-03-17 13:01 ` Thomas Hellstrom
2010-03-17 15:52 ` Jerome Glisse
-- strict thread matches above, loose matches on Subject: below --
2010-02-23 14:40 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=4B8BAD1A.7020600@vmware.com \
--to=thellstrom@vmware.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=jglisse@redhat.com \
--cc=skeggsb@gmail.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.