db: move caller_info as close as possible to raw SQL
authorDan Carpenter <dan.carpenter@oracle.com>
Wed, 13 Feb 2013 23:31:30 +0000 (02:31 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Thu, 14 Feb 2013 12:03:13 +0000 (15:03 +0300)
commit993cf15fbfd835dbb7b7f1c3cb1135d08b60d358
tree5e28c2162b99e2f960223b880a27af394d6fa0d6
parentdffc3d51a3c9a5ca3c1b894e89c8a9d1f4666159
db: move caller_info as close as possible to raw SQL

I can't move caller_info to use raw SQL because I want each call to have
a unique call id.  That lets us group the records for one call together.
The other thing which is a bit tricky is that I want to ignore the
functions which are called over 200 times.  Both of those are easier to
do after we have processed the whole kernel.

But I still want to move it to something closer to SQL because it will
make future work a bit easier.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
check_list.h
check_user_data.c
smatch.h
smatch_buf_size.c
smatch_capped.c
smatch_db.c
smatch_extra.c
smatch_scripts/db/fill_db_caller_info.pl