1. 07 2月, 2007 21 次提交
  2. 30 1月, 2007 3 次提交
  3. 25 1月, 2007 5 次提交
  4. 24 1月, 2007 2 次提交
  5. 19 1月, 2007 2 次提交
  6. 12 1月, 2007 1 次提交
    • G
      [PATCH] Change cpu_up and co from __devinit to __cpuinit · b282b6f8
      Gautham R Shenoy 提交于
      Compiling the kernel with CONFIG_HOTPLUG = y and CONFIG_HOTPLUG_CPU = n
      with CONFIG_RELOCATABLE = y generates the following modpost warnings
      
      WARNING: vmlinux - Section mismatch: reference to .init.data: from
      .text between '_cpu_up' (at offset 0xc0141b7d) and 'cpu_up'
      WARNING: vmlinux - Section mismatch: reference to .init.data: from
      .text between '_cpu_up' (at offset 0xc0141b9c) and 'cpu_up'
      WARNING: vmlinux - Section mismatch: reference to .init.text:__cpu_up
      from .text between '_cpu_up' (at offset 0xc0141bd8) and 'cpu_up'
      WARNING: vmlinux - Section mismatch: reference to .init.data: from
      .text between '_cpu_up' (at offset 0xc0141c05) and 'cpu_up'
      WARNING: vmlinux - Section mismatch: reference to .init.data: from
      .text between '_cpu_up' (at offset 0xc0141c26) and 'cpu_up'
      WARNING: vmlinux - Section mismatch: reference to .init.data: from
      .text between '_cpu_up' (at offset 0xc0141c37) and 'cpu_up'
      
      This is because cpu_up, _cpu_up and __cpu_up (in some architectures) are
      defined as __devinit
      AND
      __cpu_up calls some __cpuinit functions.
      
      Since __cpuinit would map to __init with this kind of a configuration,
      we get a .text refering .init.data warning.
      
      This patch solves the problem by converting all of __cpu_up, _cpu_up
      and cpu_up from __devinit to __cpuinit. The approach is justified since
      the callers of cpu_up are either dependent on CONFIG_HOTPLUG_CPU or
      are of __init type.
      
      Thus when CONFIG_HOTPLUG_CPU=y, all these cpu up functions would land up
      in .text section, and when CONFIG_HOTPLUG_CPU=n, all these functions would
      land up in .init section.
      
      Tested on a i386 SMP machine running linux-2.6.20-rc3-mm1.
      Signed-off-by: NGautham R Shenoy <ego@in.ibm.com>
      Cc: Vivek Goyal <vgoyal@in.ibm.com>
      Cc: Mikael Starvik <starvik@axis.com>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Kyle McMartin <kyle@mcmartin.ca>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b282b6f8
  7. 11 1月, 2007 3 次提交
    • A
      [MIPS] Alchemy: Fix PCI-memory access · 8a93c496
      Alexander Bigga 提交于
          
          The problem was introduced in 2.6.18.3 with the casting of some
          36bit-defines (PCI memory) in au1000.h to resource_size_t which may be
          u32 or u64 depending on the experimental CONFIG_RESOURCES_64BIT.
          
          With unset CONFIG_RESOURCES_64BIT, the pci-memory cannot be accessed
          because the ioremap in arch/mips/au1000/common/pci.c already used the
          truncated addresses.
          With set CONFIG_RESOURCES_64BIT, things get even worse, because PCI-scan
          aborts, due to resource conflict: request_resource() in arch/mips/pci/pci.c
          fails because the maximum iomem-address is 0xffffffff (32bit) but the
          pci-memory-start-address is 0x440000000 (36bit).
          
          To get pci working again, I propose the following patch:
          
          1. remove the resource_size_t-casting from au1000.h again
          2. make the casting in arch/mips/au1000/common/pci.c (it's allowed and
          necessary here. The 36bit-handling will be done in __fixup_bigphys_addr).
          
          With this patch pci works again like in 2.6.18.2, the gcc-compile warnings
          in pci.c are gone and it doesn't depend on CONFIG_EXPERIMENTAL.
      Signed-off-by: NAlexander Bigga <ab@mycable.de>
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      
      ---
      8a93c496
    • A
      [MIPS] Fix N32 SysV IPC routines · e16d8df0
      Atsushi Nemoto 提交于
      Add wrappers for N32 msg{snd,rcv}.  compat_sys_msg{snd,rcv} can not not be
      used as system call entries as is.  This fix is based on Kaz Kylheku's
      patch.
      
      Also change a type of last argument of sysn32_semctl to match its true
      size.
      Signed-off-by: NAtsushi Nemoto <anemo@mba.ocn.ne.jp>
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      e16d8df0
    • A
      6b4cd275
  8. 09 1月, 2007 3 次提交