1. 15 10月, 2012 1 次提交
  2. 02 6月, 2012 1 次提交
  3. 24 5月, 2012 1 次提交
  4. 02 9月, 2009 1 次提交
  5. 16 1月, 2009 1 次提交
    • B
      avr32: Fix out-of-range rcalls in large kernels · 8d29b7b9
      Ben Nizette 提交于
      Replace handcoded rcall instructions with the call pseudo-instruction.
      For kernels too far over 1MB the rcall instruction can't reach and
      linking will fail.  We already call the final linker with --relax which
      converts call pseudo-instructions to the right things anyway.
      
      This fixes
      
      arch/avr32/kernel/built-in.o: In function `syscall_exit_work':
      (.ex.text+0x198): relocation truncated to fit: R_AVR32_22H_PCREL against symbol `schedule' defined in .sched.text section in kernel/built-in.o
      arch/avr32/kernel/built-in.o: In function `fault_exit_work':
      (.ex.text+0x3b6): relocation truncated to fit: R_AVR32_22H_PCREL against symbol `schedule' defined in .sched.text section in kernel/built-in.o
      
      But I'm still left with
      
      arch/avr32/kernel/built-in.o:(.fixup+0x2): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+45a
      arch/avr32/kernel/built-in.o:(.fixup+0x8): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+8ea
      arch/avr32/kernel/built-in.o:(.fixup+0xe): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+abe
      arch/avr32/kernel/built-in.o:(.fixup+0x14): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+ac8
      arch/avr32/kernel/built-in.o:(.fixup+0x1a): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+ad2
      arch/avr32/kernel/built-in.o:(.fixup+0x20): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+adc
      arch/avr32/kernel/built-in.o:(.fixup+0x26): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+ae6
      arch/avr32/kernel/built-in.o:(.fixup+0x2c): relocation truncated to fit: R_AVR32_22H_PCREL against `.text'+af0
      arch/avr32/kernel/built-in.o:(.fixup+0x32): additional relocation overflows omitted from the output
      
      These are caused by a similar problem with 'rjmp' instructions.
      Unfortunately, there's no easy fix for these at the moment since we
      don't have a arbitrary-range 'jmp' instruction similar to 'call'.
      Signed-off-by: NBen Nizette <bn@niasdigital.com>
      Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      8d29b7b9
  6. 01 9月, 2008 1 次提交
  7. 02 7月, 2008 2 次提交
    • H
      avr32: Cover the kernel page tables in the user PGDs · a9a934f2
      Haavard Skinnemoen 提交于
      Expand the per-process PGDs so that they cover the kernel virtual
      memory area as well. This simplifies the TLB miss handler fastpath
      since it doesn't have to check for kernel addresses anymore.
      
      If a TLB miss happens on a kernel address and a second-level page
      table can't be found, we check swapper_pg_dir and copy the PGD entry
      into the user PGD if it can be found there.
      Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      a9a934f2
    • H
      avr32: Store virtual addresses in the PGD · cfd23e93
      Haavard Skinnemoen 提交于
      Instead of storing physical addresses along with page flags in the
      PGD, store virtual addresses and use NULL to indicate a not present
      second-level page table. A non-page-aligned page table indicates a bad
      PMD.
      
      This simplifies the TLB miss handler since it no longer has to check
      the Present bit and no longer has to convert the PGD entry from
      physical to virtual address. Instead, it has to check for a NULL
      entry, which is slightly cheaper than either.
      Signed-off-by: NHaavard Skinnemoen <haavard.skinnemoen@atmel.com>
      cfd23e93
  8. 27 6月, 2008 1 次提交
  9. 20 4月, 2008 1 次提交
  10. 07 12月, 2007 4 次提交
    • H
      [AVR32] Fix wrong pt_regs in critical exception handler · 5998a3cf
      Haavard Skinnemoen 提交于
      It's not like it really matters at this point since the system is
      dying anyway, but handle_critical pushes too few registers on the
      stack so the register dump, which makes the register dump look a bit
      strange. This patch fixes it.
      Signed-off-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      5998a3cf
    • H
      [AVR32] Follow the rules when dealing with the OCD system · 2507bc13
      Haavard Skinnemoen 提交于
      The current debug trap handling code does a number of things that are
      illegal according to the AVR32 Architecture manual. Most importantly,
      it may try to schedule from Debug Mode, thus clearing the D bit, which
      can lead to "undefined behaviour".
      
      It seems like this works in most cases, but several people have
      observed somewhat unstable behaviour when debugging programs,
      including soft lockups. So there's definitely something which is not
      right with the existing code.
      
      The new code will never schedule from Debug mode, it will always exit
      Debug mode with a "retd" instruction, and if something not running in
      Debug mode needs to do something debug-related (like doing a single
      step), it will enter debug mode through a "breakpoint" instruction.
      The monitor code will then return directly to user space, bypassing
      its own saved registers if necessary (since we don't actually care
      about the trapped context, only the one that came before.)
      
      This adds three instructions to the common exception handling code,
      including one branch. It does not touch super-hot paths like the TLB
      miss handler.
      Signed-off-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      2507bc13
    • H
      [AVR32] Clean up OCD register usage · 8dfe8f29
      Haavard Skinnemoen 提交于
      Generate a new set of OCD register definitions in asm/ocd.h and rename
      __mfdr() and __mtdr() to ocd_read() and ocd_write() respectively.
      
      The bitfield definitions are a lot more complete now, and they are
      entirely based on bit numbers, not masks. This is because OCD
      registers are frequently accessed from assembly code, where bit
      numbers are a lot more useful (can be fed directly to sbr, bfins,
      etc.)
      
      Bitfields that consist of more than one bit have two definitions:
      _START, which indicates the number of the first bit, and _SIZE, which
      indicates the number of bits. These directly correspond to the
      parameters taken by the bfextu, bfexts and bfins instructions.
      Signed-off-by: NHaavard Skinnemoen <hskinnemoen@atmel.com>
      8dfe8f29
    • H
  11. 11 10月, 2007 1 次提交
  12. 27 4月, 2007 3 次提交
  13. 26 9月, 2006 1 次提交