From: "Christian König" <deathsimple@vodafone.de>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: RFC: Radeon multi ring support branch
Date: Thu, 17 Nov 2011 17:24:49 +0100 [thread overview]
Message-ID: <4EC53551.8070005@vodafone.de> (raw)
In-Reply-To: <CAH3drwboczTeB7hS+pNw6ZWTa-acuXN_G_4pLZy5QK7Bgi2NgQ@mail.gmail.com>
On 16.11.2011 01:24, Jerome Glisse wrote:
> Well as we don't specify on which value semaphore should wait on, i am
> prety sure the first ring to increment the semaphore will unblock all
> waiter. So if you have ring1 that want to wait on ring2 and ring3 as
> soon as ring2 or ring3 is done ring1 will go one while either ring2 or
> ring3 might not be done. I will test that tomorrow but from doc i have
> it seems so. Thus it will be broken with more than one ring, that
> would mean you have to allocate one semaphore for each ring couple you
> want to synchronize. Note that the usual case will likely be sync btw
> 2 ring.
Good point, but I played with it a bit more today and it is just
behaving as I thought it would be. A single signal command will just
unblock a single waiter, even if there are multiple waiters currently
for this semaphore, the only thing you can't tell is which waiter will
come first.
I should also note that the current algorithm will just emit multiple
wait operations to a single ring, and spread the signal operations to
all other rings we are interested in. That isn't very efficient, but
should indeed work quite fine.
> After retesting the first patch drm/radeon: fix debugfs handling is NAK
> a complete no go.
>
> Issue is that radeon_debugfs_cleanup is call after rdev is free. This
> is why i used a static array. I forgot about that, i should have put a
> comment. I guess you built your kernel without debugfs or that you
> didn't tested to reload the module.
Mhm, I have tested it, seen the crash, and didn't thought that this is a
problem. Don't ask me why I can't understand it myself right now.
Anyway, I moved the unregistering of the files into a separate function,
which is now called from radeon_device_fini instead of
radeon_debugfs_cleanup. That seems to work fine, at least if I haven't
missed something else.
I also merged your indention fixes and the fix for the never allocated
semaphores and pushed the result into my public repository
(http://cgit.freedesktop.org/~deathsimple/linux), so please take another
look at it.
Thanks,
Christian.
next prev parent reply other threads:[~2011-11-17 16:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 13:00 RFC: Radeon multi ring support branch Christian König
2011-10-31 15:05 ` Jerome Glisse
2011-11-02 10:12 ` Christian König
2011-11-02 14:24 ` Jerome Glisse
2011-11-15 19:32 ` Jerome Glisse
2011-11-15 23:19 ` Christian König
2011-11-16 0:24 ` Jerome Glisse
2011-11-17 16:24 ` Christian König [this message]
2011-11-17 16:58 ` Jerome Glisse
2011-11-18 12:19 ` Christian König
2011-11-18 14:21 ` Jerome Glisse
2011-11-18 15:41 ` Jerome Glisse
2011-11-17 20:16 ` Alex Deucher
2011-11-18 12:44 ` Alex Deucher
2011-11-18 16:34 ` Jerome Glisse
2011-11-20 21:04 ` 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=4EC53551.8070005@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox