1. 13 3月, 2007 1 次提交
  2. 10 3月, 2007 1 次提交
  3. 09 3月, 2007 1 次提交
  4. 06 3月, 2007 1 次提交
  5. 03 3月, 2007 2 次提交
  6. 01 3月, 2007 1 次提交
  7. 13 2月, 2007 1 次提交
  8. 12 2月, 2007 1 次提交
    • T
      [PATCH] consolidate line discipline number definitions · 4564f9e5
      Tilman Schmidt 提交于
      The line discipline numbers N_* are currently defined for each architecture
      individually, but (except for a seeming mistake) identically, in
      asm/termios.h.  There is no obvious reason why these numbers should be
      architecture specific, nor any apparent relationship with the termios
      structure.  The total number of these, NR_LDISCS, is defined in linux/tty.h
      anyway.  So I propose the following patch which moves the definitions of
      the individual line disciplines to linux/tty.h too.
      
      Three of these numbers (N_MASC, N_PROFIBUS_FDL, and N_SMSBLOCK) are unused
      in the current kernel, but the patch still keeps the complete set in case
      there are plans to use them yet.
      Signed-off-by: NTilman Schmidt <tilman@imap.cc>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      4564f9e5
  9. 11 2月, 2007 1 次提交
    • D
      [SPARC64]: Add PCI MSI support on Niagara. · 35a17eb6
      David S. Miller 提交于
      This is kind of hokey, we could use the hardware provided facilities
      much better.
      
      MSIs are assosciated with MSI Queues.  MSI Queues generate interrupts
      when any MSI assosciated with it is signalled.  This suggests a
      two-tiered IRQ dispatch scheme:
      
      	MSI Queue interrupt --> queue interrupt handler
      		MSI dispatch --> driver interrupt handler
      
      But we just get one-level under Linux currently.  What I'd like to do
      is possibly stick the IRQ actions into a per-MSI-Queue data structure,
      and dispatch them form there, but the generic IRQ layer doesn't
      provide a way to do that right now.
      
      So, the current kludge is to "ACK" the interrupt by processing the
      MSI Queue data structures and ACK'ing them, then we run the actual
      handler like normal.
      
      We are wasting a lot of useful information, for example the MSI data
      and address are provided with ever MSI, as well as a system tick if
      available.  If we could pass this into the IRQ handler it could help
      with certain things, in particular for PCI-Express error messages.
      
      The MSI entries on sparc64 also tell you exactly which bus/device/fn
      sent the MSI, which would be great for error handling when no
      registered IRQ handler can service the interrupt.
      
      We override the disable/enable IRQ chip methods in sun4v_msi, so we
      have to call {mask,unmask}_msi_irq() directly from there.  This is
      another ugly wart.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      35a17eb6
  10. 01 1月, 2007 1 次提交
  11. 18 12月, 2006 2 次提交
  12. 14 12月, 2006 1 次提交
  13. 10 12月, 2006 3 次提交
    • D
      [SPARC64]: Fix several kprobes bugs. · f0882589
      David S. Miller 提交于
      - relbranch_fixup(), for non-branches, would end up setting
        regs->tnpc incorrectly, in fact it would set it equal to
        regs->tpc which would cause that instruction to execute twice
      
        Also, if this is not a PC-relative branch, we should just
        leave regs->tnpc as-is.  This covers cases like 'jmpl' which
        branch to absolute values.
      
      - To be absolutely %100 safe, we need to flush the instruction
        cache for all assignments to kprobe->ainsn.insn[], including
        cases like add_aggr_kprobe()
      
      - prev_kprobe's status field needs to be 'unsigned long' to match
        the type of the value it is saving
      
      - jprobes were totally broken:
        = jprobe_return() can run in the stack frame of the jprobe handler,
          or in an even deeper stack frame, thus we'll be in the wrong
          register window than the one from the original probe state.
      
          So unwind using 'restore' instructions, if necessary, right
          before we do the jprobe_return() breakpoint trap.
      
        = There is no reason to save/restore the register window saved
          at %sp at jprobe trigger time.  Those registers cannot be
          modified by the jprobe handler.  Also, this code was saving
          and restoring "sizeof (struct sparc_stackf)" bytes.  Depending
          upon the caller, this could clobber unrelated stack frame
          pieces if there is only a basic 128-byte register window
          stored on the stack, without the argument save area.
      
          So just saving and restoring struct pt_regs is sufficient.
      
        = Kill the "jprobe_saved_esp", totally unused.
      
          Also, delete "jprobe_saved_regs_location", with the stack frame
          unwind now done explicitly by jprobe_return(), this check is
          superfluous.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f0882589
    • M
      5ff42459
    • D
      10e26723
  14. 09 12月, 2006 1 次提交
    • A
      [PATCH] tty: preparatory structures for termios revamp · be90038a
      Alan Cox 提交于
      In order to sort out our struct termios and add proper speed control we need
      to separate the kernel and user termios structures.  Glibc is fine but the
      other libraries rely on the kernel exported struct termios and we need to
      extend this without breaking the ABI/API
      
      To do so we add a struct ktermios which is the kernel view of a termios
      structure and overlaps the struct termios with extra fields on the end for
      now.  (That limitation will go away in later patches).  Some platforms (eg
      alpha) planned ahead and thus use the same struct for both, others did not.
      
      This just adds the structures but does not use them, it seems a sensible
      splitting point for bisect if there are compile failures (not that I expect
      them)
      Signed-off-by: NAlan Cox <alan@redhat.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      be90038a
  15. 08 12月, 2006 5 次提交
  16. 03 12月, 2006 1 次提交
  17. 02 12月, 2006 2 次提交
  18. 06 11月, 2006 1 次提交
    • D
      [SPARC]: Fix robust futex syscalls and wire up migrate_pages. · 59359ff8
      David S. Miller 提交于
      When I added the entries for the robust futex syscall entries, I
      forgot to bump NR_SYSCALLS.  The current situation is error-prone
      because NR_SYSCALLS lives in entry.S where the system call limit
      checks are enforced.  Move the definition to asm/unistd.h in order to
      make this mistake much more difficult to make.
      
      And wire up sys_migrate_pages since the powerpc folks implemented the
      compat wrapper for us.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      59359ff8
  19. 02 11月, 2006 1 次提交
  20. 23 10月, 2006 1 次提交
  21. 12 10月, 2006 1 次提交
  22. 09 10月, 2006 1 次提交
  23. 04 10月, 2006 1 次提交
  24. 03 10月, 2006 2 次提交
  25. 02 10月, 2006 1 次提交
    • A
      [PATCH] remove remaining errno and __KERNEL_SYSCALLS__ references · 135ab6ec
      Arnd Bergmann 提交于
      The last in-kernel user of errno is gone, so we should remove the definition
      and everything referring to it.  This also removes the now-unused lib/execve.c
      file that was introduced earlier.
      
      Also remove every trace of __KERNEL_SYSCALLS__ that still remained in the
      kernel.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: Andi Kleen <ak@muc.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Ian Molton <spyro@f2s.com>
      Cc: Mikael Starvik <starvik@axis.com>
      Cc: David Howells <dhowells@redhat.com>
      Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
      Cc: Hirokazu Takata <takata.hirokazu@renesas.com>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Kyle McMartin <kyle@mcmartin.ca>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Kazumoto Kojima <kkojima@rr.iij4u.or.jp>
      Cc: Richard Curnow <rc@rc0.org.uk>
      Cc: William Lee Irwin III <wli@holomorphy.com>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jeff Dike <jdike@addtoit.com>
      Cc: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
      Cc: Miles Bader <uclinux-v850@lsi.nec.co.jp>
      Cc: Chris Zankel <chris@zankel.net>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      135ab6ec
  26. 01 10月, 2006 1 次提交
    • M
      [PATCH] Directed yield: cpu_relax variants for spinlocks and rw-locks · ef6edc97
      Martin Schwidefsky 提交于
      On systems running with virtual cpus there is optimization potential in
      regard to spinlocks and rw-locks.  If the virtual cpu that has taken a lock
      is known to a cpu that wants to acquire the same lock it is beneficial to
      yield the timeslice of the virtual cpu in favour of the cpu that has the
      lock (directed yield).
      
      With CONFIG_PREEMPT="n" this can be implemented by the architecture without
      common code changes.  Powerpc already does this.
      
      With CONFIG_PREEMPT="y" the lock loops are coded with _raw_spin_trylock,
      _raw_read_trylock and _raw_write_trylock in kernel/spinlock.c.  If the lock
      could not be taken cpu_relax is called.  A directed yield is not possible
      because cpu_relax doesn't know anything about the lock.  To be able to
      yield the lock in favour of the current lock holder variants of cpu_relax
      for spinlocks and rw-locks are needed.  The new _raw_spin_relax,
      _raw_read_relax and _raw_write_relax primitives differ from cpu_relax
      insofar that they have an argument: a pointer to the lock structure.
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      ef6edc97
  27. 26 9月, 2006 2 次提交
    • D
      [PATCH] Standardize pxx_page macros · 46a82b2d
      Dave McCracken 提交于
      One of the changes necessary for shared page tables is to standardize the
      pxx_page macros.  pte_page and pmd_page have always returned the struct
      page associated with their entry, while pte_page_kernel and pmd_page_kernel
      have returned the kernel virtual address.  pud_page and pgd_page, on the
      other hand, return the kernel virtual address.
      
      Shared page tables needs pud_page and pgd_page to return the actual page
      structures.  There are very few actual users of these functions, so it is
      simple to standardize their usage.
      
      Since this is basic cleanup, I am submitting these changes as a standalone
      patch.  Per Hugh Dickins' comments about it, I am also changing the
      pxx_page_kernel macros to pxx_page_vaddr to clarify their meaning.
      Signed-off-by: NDave McCracken <dmccr@us.ibm.com>
      Cc: Hugh Dickins <hugh@veritas.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      46a82b2d
    • J
      [libata] No need for all those arch libata-portmap.h headers · a6d967a4
      Jeff Garzik 提交于
      They all contain the same thing.  Instead, have a single generic one in
      include/asm-generic, and permit an arch to override as needed.
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      a6d967a4
  28. 21 9月, 2006 1 次提交
  29. 19 9月, 2006 1 次提交