Re: [PATCH v7 3/7] ftrace: Add arm64 support to recordmcount

2014-04-16 Thread Will Deacon
On Sat, Mar 15, 2014 at 05:40:44AM +, AKASHI Takahiro wrote: > Recordmcount utility under scripts is run, after compiling each object, > to find out all the locations of calling _mcount() and put them into > specific seciton named __mcount_loc. > Then linker collects all such information into

Re: [PATCH v7 3/7] ftrace: Add arm64 support to recordmcount

2014-04-16 Thread Will Deacon
On Sat, Mar 15, 2014 at 05:40:44AM +, AKASHI Takahiro wrote: Recordmcount utility under scripts is run, after compiling each object, to find out all the locations of calling _mcount() and put them into specific seciton named __mcount_loc. Then linker collects all such information into a

[PATCH v7 3/7] ftrace: Add arm64 support to recordmcount

2014-03-14 Thread AKASHI Takahiro
Recordmcount utility under scripts is run, after compiling each object, to find out all the locations of calling _mcount() and put them into specific seciton named __mcount_loc. Then linker collects all such information into a table in the kernel image (between __start_mcount_loc and

[PATCH v7 3/7] ftrace: Add arm64 support to recordmcount

2014-03-14 Thread AKASHI Takahiro
Recordmcount utility under scripts is run, after compiling each object, to find out all the locations of calling _mcount() and put them into specific seciton named __mcount_loc. Then linker collects all such information into a table in the kernel image (between __start_mcount_loc and