1. 23 11月, 2016 1 次提交
    • R
      Revert "arm: move exports to definitions" · 8478132a
      Russell King 提交于
      This reverts commit 4dd1837d.
      
      Moving the exports for assembly code into the assembly files breaks
      KSYM trimming, but also breaks modversions.
      
      While fixing the KSYM trimming is trivial, fixing modversions brings
      us to a technically worse position that we had prior to the above
      change:
      
      - We end up with the prototype definitions divorsed from everything
        else, which means that adding or removing assembly level ksyms
        become more fragile:
        * if adding a new assembly ksyms export, a missed prototype in
          asm-prototypes.h results in a successful build if no module in
          the selected configuration makes use of the symbol.
        * when removing a ksyms export, asm-prototypes.h will get forgotten,
          with armksyms.c, you'll get a build error if you forget to touch
          the file.
      
      - We end up with the same amount of include files and prototypes,
        they're just in a header file instead of a .c file with their
        exports.
      
      As for lines of code, we don't get much of a size reduction:
       (original commit)
       47 files changed, 131 insertions(+), 208 deletions(-)
       (fix for ksyms trimming)
       7 files changed, 18 insertions(+), 5 deletions(-)
       (two fixes for modversions)
       1 file changed, 34 insertions(+)
       3 files changed, 7 insertions(+), 2 deletions(-)
      which results in a net total of only 25 lines deleted.
      
      As there does not seem to be much benefit from this change of approach,
      revert the change.
      Signed-off-by: NRussell King <rmk+kernel@armlinux.org.uk>
      8478132a
  2. 08 8月, 2016 1 次提交
  3. 25 8月, 2015 1 次提交
  4. 30 3月, 2015 1 次提交
  5. 28 11月, 2014 1 次提交
    • L
      ARM: 8225/1: Add unwinding support for memory copy functions · 279f487e
      Lin Yongting 提交于
      The memory copy functions(memcpy, __copy_from_user, __copy_to_user)
      never had unwinding annotations added. Currently, when accessing
      invalid pointer by these functions occurs the backtrace shown will
      stop at these functions or some completely unrelated function.
      Add unwinding annotations in hopes of getting a more useful backtrace
      in following cases:
      1. die on accessing invalid pointer by these functions
      2. kprobe trapped at any instruction within these functions
      3. interrupted at any instruction within these functions
      Signed-off-by: NLin Yongting <linyongting@gmail.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      279f487e
  6. 08 5月, 2010 1 次提交
  7. 21 4月, 2010 1 次提交
    • R
      ARM: fix build error in arch/arm/kernel/process.c · 4260415f
      Russell King 提交于
      /tmp/ccJ3ssZW.s: Assembler messages:
      /tmp/ccJ3ssZW.s:1952: Error: can't resolve `.text' {.text section} - `.LFB1077'
      
      This is caused because:
      
      	.section .data
      	.section .text
      	.section .text
      	.previous
      
      does not return us to the .text section, but the .data section; this
      makes use of .previous dangerous if the ordering of previous sections
      is not known.
      
      Fix up the other users of .previous; .pushsection and .popsection are
      a safer pairing to use than .section and .previous.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      4260415f
  8. 24 7月, 2009 1 次提交
  9. 30 5月, 2009 1 次提交
    • N
      [ARM] allow for alternative __copy_to_user/__clear_user implementations · a1f98849
      Nicolas Pitre 提交于
      This allows for optional alternative implementations of __copy_to_user
      and __clear_user, with a possible runtime fallback to the standard
      version when the alternative provides no gain over that standard
      version. This is done by making the standard __copy_to_user into a weak
      alias for the symbol __copy_to_user_std.  Same thing for __clear_user.
      
      Those two functions are particularly good candidates to have alternative
      implementations for, since they rely on the STRT instruction which has
      lower performances than STM instructions on some CPU cores such as
      the ARM1176 and Marvell Feroceon.
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      a1f98849
  10. 01 9月, 2008 1 次提交
  11. 29 6月, 2006 1 次提交
  12. 02 11月, 2005 1 次提交