1. 22 9月, 2009 4 次提交
  2. 21 9月, 2009 4 次提交
  3. 18 8月, 2009 5 次提交
  4. 06 8月, 2009 2 次提交
    • J
      net: implement a SO_DOMAIN getsockoption · 0d6038ee
      Jan Engelhardt 提交于
      This sockopt goes in line with SO_TYPE and SO_PROTOCOL. It makes it
      possible for userspace programs to pass around file descriptors — I
      am referring to arguments-to-functions, but it may even work for the
      fd passing over UNIX sockets — without needing to also pass the
      auxiliary information (PF_INET6/IPPROTO_TCP).
      Signed-off-by: NJan Engelhardt <jengelh@medozas.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0d6038ee
    • J
      net: implement a SO_PROTOCOL getsockoption · 49c794e9
      Jan Engelhardt 提交于
      Similar to SO_TYPE returning the socket type, SO_PROTOCOL allows to
      retrieve the protocol used with a given socket.
      
      I am not quite sure why we have that-many copies of socket.h, and why
      the values are not the same on all arches either, but for where hex
      numbers dominate, I use 0x1029 for SO_PROTOCOL as that seems to be
      the next free unused number across a bunch of operating systems, or
      so Google results make me want to believe. SO_PROTOCOL for others
      just uses the next free Linux number, 38.
      Signed-off-by: NJan Engelhardt <jengelh@medozas.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      49c794e9
  5. 28 7月, 2009 1 次提交
    • B
      mm: Pass virtual address to [__]p{te,ud,md}_free_tlb() · 9e1b32ca
      Benjamin Herrenschmidt 提交于
      mm: Pass virtual address to [__]p{te,ud,md}_free_tlb()
      
      Upcoming paches to support the new 64-bit "BookE" powerpc architecture
      will need to have the virtual address corresponding to PTE page when
      freeing it, due to the way the HW table walker works.
      
      Basically, the TLB can be loaded with "large" pages that cover the whole
      virtual space (well, sort-of, half of it actually) represented by a PTE
      page, and which contain an "indirect" bit indicating that this TLB entry
      RPN points to an array of PTEs from which the TLB can then create direct
      entries. Thus, in order to invalidate those when PTE pages are deleted,
      we need the virtual address to pass to tlbilx or tlbivax instructions.
      
      The old trick of sticking it somewhere in the PTE page struct page sucks
      too much, the address is almost readily available in all call sites and
      almost everybody implemets these as macros, so we may as well add the
      argument everywhere. I added it to the pmd and pud variants for consistency.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Acked-by: David Howells <dhowells@redhat.com> [MN10300 & FRV]
      Acked-by: NNick Piggin <npiggin@suse.de>
      Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com> [s390]
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9e1b32ca
  6. 27 7月, 2009 16 次提交
  7. 22 7月, 2009 1 次提交
    • M
      Driver Core: Add platform device arch data V3 · d7aacadd
      Magnus Damm 提交于
      Allow architecture specific data in struct platform_device V3.
      
      With this patch struct pdev_archdata is added to struct
      platform_device, similar to struct dev_archdata in found in
      struct device. Useful for architecture code that needs to
      keep extra data associated with each platform device.
      
      Struct pdev_archdata is different from dev.platform_data, the
      convention is that dev.platform_data points to driver-specific
      data. It may or may not be required by the driver. The format
      of this depends on driver but is the same across architectures.
      
      The structure pdev_archdata is a place for architecture specific
      data. This data is handled by architecture specific code (for
      example runtime PM), and since it is architecture specific it
      should _never_ be touched by device driver code. Exactly like
      struct dev_archdata but for platform devices.
      
      [rjw: This change is for power management mostly and that's why it
       goes through the suspend tree.]
      Signed-off-by: NMagnus Damm <damm@igel.co.jp>
      Acked-by: NKevin Hilman <khilman@deeprootsystems.com>
      Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      d7aacadd
  8. 13 7月, 2009 1 次提交
  9. 11 7月, 2009 1 次提交
  10. 09 7月, 2009 2 次提交
    • T
      linker script: unify usage of discard definition · 023bf6f1
      Tejun Heo 提交于
      Discarded sections in different archs share some commonality but have
      considerable differences.  This led to linker script for each arch
      implementing its own /DISCARD/ definition, which makes maintaining
      tedious and adding new entries error-prone.
      
      This patch makes all linker scripts to move discard definitions to the
      end of the linker script and use the common DISCARDS macro.  As ld
      uses the first matching section definition, archs can include default
      discarded sections by including them earlier in the linker script.
      
      ia64 is notable because it first throws away some ia64 specific
      subsections and then include the rest of the sections into the final
      image, so those sections must be discarded before the inclusion.
      
      defconfig compile tested for x86, x86-64, powerpc, powerpc64, ia64,
      alpha, sparc, sparc64 and s390.  Michal Simek tested microblaze.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Acked-by: NPaul Mundt <lethal@linux-sh.org>
      Acked-by: NMike Frysinger <vapier@gentoo.org>
      Tested-by: NMichal Simek <monstr@monstr.eu>
      Cc: linux-arch@vger.kernel.org
      Cc: Michal Simek <monstr@monstr.eu>
      Cc: microblaze-uclinux@itee.uq.edu.au
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Tony Luck <tony.luck@intel.com>
      023bf6f1
    • M
      microblaze: include EXIT_TEXT to _stext · 1dcdd091
      Michal Simek 提交于
      Microblaze wants to throw out EXIT_TEXT during runtime too.  This
      hasn't caused trouble till now because the linker script didn't
      discard EXIT_TEXT and it ended up in its default output section.  As
      discard definition is about to be unified, include EXIT_TEXT into
      _stext explicitly and while at it replace explicit exitcall definition
      to EXIT_CALL.
      Signed-off-by: NMichal Simek <monstr@monstr.eu>
      Signed-off-by: NTejun Heo <tj@kernel.org>
      1dcdd091
  11. 06 7月, 2009 3 次提交