On Mon, Jan 14, 2013 at 6:02 AM, horseriver <horserivers@xxxxxxxxx> wrote:
Thank you On Mon, Jan 14, 2013 at 02:44:11PM +0000, Anuz Pratap Singh Tomar wrote:
> On Mon, Jan 14, 2013 at 4:50 AM, horseriver <horserivers@xxxxxxxxx> wrote:
>
> > On Sun, Jan 13, 2013 at 09:27:45PM -0800, Dave Hylands wrote:
> > > Hi,
> > >
> > > On Sun, Jan 13, 2013 at 11:29 AM, horseriver <horserivers@xxxxxxxxx>
> > wrote:
> > > >
> > > > hi:
> > > >
> > > > In kernel code . some function is defined by
> > > __attribute__((__section__(".initcall" level ".init")))
> > > >
> > > > what does this do ?
> > >
> > > It puts the address of the function in a linker section named
> > > .initcallX.init where X is replaced by the level.
> > >
> > > These functions are called in order to initialize various subsystems and
> > > drivers during kernel bootup.
> >
> > Thanks!
> >
> > Another question:
> >
> > __attribute__((regparm(3))) ; what does this do ?
> >
> >
> >
> > A simple google search should have answered this
> http://ohse.de/uwe/articles/gcc-attributes.html
>
> Synopsis
>
> regparm (NUMBER) Found in versions: 2.7-3.4 Description:
>
> Functions that take a variable number of> what does this mean?
> arguments will continue to be passed all of their arguments on the
> stack.
>
>
May be you should really read more.
I would suggest reading some i386 assembly.
I would suggest reading some i386 assembly.
Warm Regards
Anuz
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies