From: "Christian König" <deathsimple@vodafone.de>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: VM lockdep warning
Date: Sat, 21 Apr 2012 16:16:23 +0200 [thread overview]
Message-ID: <4F92C137.6050403@vodafone.de> (raw)
In-Reply-To: <CAH3drwYXR1JFzie+oc5YQLRPJF+Yhe8TYQ1RLy_YXgLgdj34qA@mail.gmail.com>
On 21.04.2012 16:08, Jerome Glisse wrote:
> 2012/4/21 Christian König<deathsimple@vodafone.de>:
>> Interesting, I'm pretty sure that I haven't touched the locking order of the
>> cs_mutex vs. vm_mutex.
>>
>> Maybe it is just some kind of side effect, going to locking into it anyway.
>>
>> Christian.
>>
> It's the using, init path take lock in different order than cs path
Well, could you explain to me why the vm code takes cs mutex in the
first place?
It clearly has it's own mutex and it doesn't looks like that it deals
with any cs related data anyway.
Christian.
next prev parent reply other threads:[~2012-04-21 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:39 VM lockdep warning Dave Airlie
2012-04-21 12:35 ` Christian König
2012-04-21 14:08 ` Jerome Glisse
2012-04-21 14:16 ` Christian König [this message]
2012-04-21 14:50 ` Jerome Glisse
2012-04-21 15:57 ` Dave Airlie
2012-04-21 16:32 ` Christian König
2012-04-21 17:30 ` Jerome Glisse
2012-04-21 19:26 ` Christian König
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=4F92C137.6050403@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 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.