Re: Interrupt context

From: Octavian Purdila <tavi@cs.pub.ro>
To: Christopher Li <sparse@chrisli.org>
Cc: Codrin Alexandru Grajdeanu <grcodal@gmail.com>,
	linux-sparse@vger.kernel.org
Subject: Re: Interrupt context
Date: Wed, 26 Mar 2008 14:43:18 +0200	[thread overview]
Message-ID: <200803261443.18529.tavi@cs.pub.ro> (raw)
In-Reply-To: <70318cbf0803241957l6b211d34t3cad51d587192501@mail.gmail.com>

On Tuesday 25 March 2008, Christopher Li wrote:
>
> BTW, besides linking what else do the ELF format buys you?
>

You don't need to change the build system, you got all the information you 
need in the final deliverable of the build (vmlinux or the kernel module).

>
> >  For this second try, we were thinking about replacing the serializer
> > with a thiner layer which would just save the call graph information
> > together with the associated interrupt context function / sleeping
> > function attributes in the object files.
>
> I would like to see some thing more general. For each file, it saves
> the information:
>
> 1) What symbol does it provide as extern.
> 2) What symbol does it accessed.
> 3) The linearized byte code for each function emits. (serialized of
> the entrypoint
>     for each function).
>
> And then, you would be able to perform a lot of checking on this.
>

OK, so you think that the serializer approach is still the way to go then? 

Thanks,
tavi