Hi Herbert,
> I just tried to pinpoint the location based on my
> 2.6.38.8-vs2.3.0.37-rc17 kernel and I suspect that
> task_rq(p) is causing this (for certain p), but
> I was wondering why your task_rq_lock() is 0xa0
> bytes in size, where mine is just 0x65 bytes ...
>
> especially as the task_rq_lock function is quite
> compact ...
>
> could you upload the output of the folling commands
> for me (executed in the build directory of your
> kernel or with the vmlinux object file)
>
> # objdump -t vmlinux | grep task_rq_lock
gives me only on line:
/usr/src/linux-2.6.38.8 # objdump -t vmlinux | grep task_rq_lock
ffffffff8104ec60 l F .text 000000000000009c task_rq_lock
> # objdump -d vmlinux --start-address=0x`objdump -t vmlinux | sed -n '/task_rq_lock/ {s/ .*//; p}'` | sed '/task>:/ Q'
more lines :-)
You can download it at http://www.enas.net/objdump.txt
thanks,
Urban
Received on Sat Aug 6 13:14:00 2011