1. 31 3月, 2006 2 次提交
  2. 29 3月, 2006 8 次提交
  3. 28 3月, 2006 17 次提交
    • B
      [PATCH] powerpc: Kill _machine and hard-coded platform numbers · e8222502
      Benjamin Herrenschmidt 提交于
      This removes statically assigned platform numbers and reworks the
      powerpc platform probe code to use a better mechanism.  With this,
      board support files can simply declare a new machine type with a
      macro, and implement a probe() function that uses the flattened
      device-tree to detect if they apply for a given machine.
      
      We now have a machine_is() macro that replaces the comparisons of
      _machine with the various PLATFORM_* constants.  This commit also
      changes various drivers to use the new macro instead of looking at
      _machine.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      e8222502
    • S
    • K
      powerpc: remove OCP references · 78af9062
      Kumar Gala 提交于
      OCP isn't used in arch/powerpc and hopefully will never be.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      78af9062
    • S
      [PATCH] powerpc: make ISA floppies work again · b239cbe9
      Stephen Rothwell 提交于
      We used to assume that a DMA mapping request with a NULL dev was for
      ISA DMA.  This assumption was broken at some point.  Now we explicitly
      pass the detected ISA PCI device in the floppy setup.
      Signed-off-by: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      b239cbe9
    • A
      [PATCH] powerpc: Fix some initcall return values · 69ed3324
      Anton Blanchard 提交于
      Non zero initcalls (except for -ENODEV) have started warning at boot.
      Fix smt_setup and init_ras_IRQ.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      69ed3324
    • M
      [PATCH] powerpc: Workaround for pSeries RTAS bug · 9fe901d1
      Mike Kravetz 提交于
      A bug in the RTAS services incorrectly interprets some bits in the CR
      when called from the OS.  Specifically, bits in CR4.  The result could
      be a firmware crash that also takes down the partition.  A firmware
      fix is in the works.  We have seen this situation when performing DLPAR
      operations.  As a temporary workaround, clear the CR in enter_rtas().
      Note that enter_rtas() will not set any bits in CR4 before calling RTAS.
      
      Also note that the 32 bit version of enter_rtas() should have the same
      work around even though the chances of hitting the bug are much smaller
      due to the lack of DLPAR on 32 bit kernels.  However, my assembly skills
      are a bit rusty and the 32 bit code doesn't seem to follow the conventions
      for where things should be saved.  In addition, I don't have a system
      to test 32 bit kernels.  Help creating and at least touch testing the
      same workaround for 32 bit would be appreciated.
      Signed-off-by: NMike Kravetz <kravetz@us.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      9fe901d1
    • A
      [PATCH] spufs: fix __init/__exit annotations · e78b47a5
      Arnd Bergmann 提交于
      spufs_init and spufs_exit should be marked correctly so
      they can be removed when not needed.
      Signed-off-by: NArnd Bergmann <arnd.bergmann@de.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      e78b47a5
    • R
      [PATCH] powerpc: hvc_console updates · 45d607ed
      Ryan S. Arnold 提交于
      These are some updates from both Ryan and Arnd for the hvc_console
      driver:
      
      The main point is to enable the inclusion of a console driver
      for rtas, which is currrently needed for the cell platform.
      
      Also shuffle around some data-type declarations and moves some
      functions out of include/asm-ppc64/hvconsole.h and into a new
      drivers/char/hvc_console.h file.
      Signed-off-by: N"Ryan S. Arnold" <rsa@us.ibm.com>
      Signed-off-by: NArnd Bergmann <abergman@de.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      45d607ed
    • L
      [PATCH] powerpc: fix incorrect SA_ONSTACK behaviour for 64-bit processes · 11089f08
      Laurent MEYER 提交于
      *) When setting a sighandler using sigaction() call, if the flag
      SA_ONSTACK is set and no alternate stack is provided via sigaltstack(),
      the kernel still try to install the alternate stack. This behavior is
      the opposite of the one which is documented in Single Unix
      Specifications V3.
      
      *) Also when setting an alternate stack using sigaltstack() with the
      flag SS_DISABLE, the kernel try to install the alternate stack on
      signal delivery.
      
      These two use cases makes the process crash at signal delivery.
      
      This fixes it.
      Signed-off-by: NLaurent Meyer <meyerlau@fr.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      11089f08
    • M
      [PATCH] powerpc: Rename and export ppc64_firmware_features · d0160bf0
      Michael Ellerman 提交于
      We need to export ppc64_firmware_features for modules. Before we do that
      I think we should probably rename it to powerpc_firmware_features.
      Signed-off-by: NMichael Ellerman <michael@ellerman.id.au>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      d0160bf0
    • K
      powerpc: Make uImage default build output for MPC8540 ADS · 9cf8ca38
      Kumar Gala 提交于
      When we build for the MPC8540 ADS produce a uImage by default.
      Updated the defconfig to reflect this as well.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      9cf8ca38
    • K
      powerpc: move math-emu over to arch/powerpc · 5cd27208
      Kumar Gala 提交于
      Towards the goal of having arch/powerpc not build anything over in arch/ppc
      move math-emu over.  Also, killed some references to arch/ppc/ in the
      arch/powerpc Makefile which should belong in drivers/ when the particular
      sub-arch's move over to arch/powerpc.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      5cd27208
    • A
      [PATCH] powerpc: export validate_sp for oprofile calltrace · 2f25194d
      Anton Blanchard 提交于
      Export validate_sp so we can use it in the oprofile calltrace code.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      2f25194d
    • K
      powerpc: use memparse() for mem= command line parsing · 10d713ae
      Kumar Gala 提交于
      Use memparse() instead of our own code for handling the parsing of mem=
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      10d713ae
    • P
      powerpc: Fix goof in 6xx and POWER4 idle power-save functions · ff2e6d7e
      Paul Mackerras 提交于
      This fixes a mistake I made when editing these functions - when I
      took out the interrupt disabling code (because interrupts are now
      disabled by the caller) I left the register that is used for the MSR
      value to be used during doze/nap uninitialized.  This fixes it.
      
      Also updated some of the comments in idle_power4.S and removed some
      code that was copied over from idle_6xx.S but is no longer relevant
      (we don't ever clear the CPU_FTR_CAN_NAP bit at runtime for POWER4).
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      ff2e6d7e
    • A
      [PATCH] Notifier chain update: API changes · e041c683
      Alan Stern 提交于
      The kernel's implementation of notifier chains is unsafe.  There is no
      protection against entries being added to or removed from a chain while the
      chain is in use.  The issues were discussed in this thread:
      
          http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
      
      We noticed that notifier chains in the kernel fall into two basic usage
      classes:
      
      	"Blocking" chains are always called from a process context
      	and the callout routines are allowed to sleep;
      
      	"Atomic" chains can be called from an atomic context and
      	the callout routines are not allowed to sleep.
      
      We decided to codify this distinction and make it part of the API.  Therefore
      this set of patches introduces three new, parallel APIs: one for blocking
      notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
      really just the old API under a new name).  New kinds of data structures are
      used for the heads of the chains, and new routines are defined for
      registration, unregistration, and calling a chain.  The three APIs are
      explained in include/linux/notifier.h and their implementation is in
      kernel/sys.c.
      
      With atomic and blocking chains, the implementation guarantees that the chain
      links will not be corrupted and that chain callers will not get messed up by
      entries being added or removed.  For raw chains the implementation provides no
      guarantees at all; users of this API must provide their own protections.  (The
      idea was that situations may come up where the assumptions of the atomic and
      blocking APIs are not appropriate, so it should be possible for users to
      handle these things in their own way.)
      
      There are some limitations, which should not be too hard to live with.  For
      atomic/blocking chains, registration and unregistration must always be done in
      a process context since the chain is protected by a mutex/rwsem.  Also, a
      callout routine for a non-raw chain must not try to register or unregister
      entries on its own chain.  (This did happen in a couple of places and the code
      had to be changed to avoid it.)
      
      Since atomic chains may be called from within an NMI handler, they cannot use
      spinlocks for synchronization.  Instead we use RCU.  The overhead falls almost
      entirely in the unregister routine, which is okay since unregistration is much
      less frequent that calling a chain.
      
      Here is the list of chains that we adjusted and their classifications.  None
      of them use the raw API, so for the moment it is only a placeholder.
      
        ATOMIC CHAINS
        -------------
      arch/i386/kernel/traps.c:		i386die_chain
      arch/ia64/kernel/traps.c:		ia64die_chain
      arch/powerpc/kernel/traps.c:		powerpc_die_chain
      arch/sparc64/kernel/traps.c:		sparc64die_chain
      arch/x86_64/kernel/traps.c:		die_chain
      drivers/char/ipmi/ipmi_si_intf.c:	xaction_notifier_list
      kernel/panic.c:				panic_notifier_list
      kernel/profile.c:			task_free_notifier
      net/bluetooth/hci_core.c:		hci_notifier
      net/ipv4/netfilter/ip_conntrack_core.c:	ip_conntrack_chain
      net/ipv4/netfilter/ip_conntrack_core.c:	ip_conntrack_expect_chain
      net/ipv6/addrconf.c:			inet6addr_chain
      net/netfilter/nf_conntrack_core.c:	nf_conntrack_chain
      net/netfilter/nf_conntrack_core.c:	nf_conntrack_expect_chain
      net/netlink/af_netlink.c:		netlink_chain
      
        BLOCKING CHAINS
        ---------------
      arch/powerpc/platforms/pseries/reconfig.c:	pSeries_reconfig_chain
      arch/s390/kernel/process.c:		idle_chain
      arch/x86_64/kernel/process.c		idle_notifier
      drivers/base/memory.c:			memory_chain
      drivers/cpufreq/cpufreq.c		cpufreq_policy_notifier_list
      drivers/cpufreq/cpufreq.c		cpufreq_transition_notifier_list
      drivers/macintosh/adb.c:		adb_client_list
      drivers/macintosh/via-pmu.c		sleep_notifier_list
      drivers/macintosh/via-pmu68k.c		sleep_notifier_list
      drivers/macintosh/windfarm_core.c	wf_client_list
      drivers/usb/core/notify.c		usb_notifier_list
      drivers/video/fbmem.c			fb_notifier_list
      kernel/cpu.c				cpu_chain
      kernel/module.c				module_notify_list
      kernel/profile.c			munmap_notifier
      kernel/profile.c			task_exit_notifier
      kernel/sys.c				reboot_notifier_list
      net/core/dev.c				netdev_chain
      net/decnet/dn_dev.c:			dnaddr_chain
      net/ipv4/devinet.c:			inetaddr_chain
      
      It's possible that some of these classifications are wrong.  If they are,
      please let us know or submit a patch to fix them.  Note that any chain that
      gets called very frequently should be atomic, because the rwsem read-locking
      used for blocking chains is very likely to incur cache misses on SMP systems.
      (However, if the chain's callout routines may sleep then the chain cannot be
      atomic.)
      
      The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
      material written by Keith Owens and suggestions from Paul McKenney and Andrew
      Morton.
      
      [jes@sgi.com: restructure the notifier chain initialization macros]
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NChandra Seetharaman <sekharan@us.ibm.com>
      Signed-off-by: NJes Sorensen <jes@sgi.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e041c683
    • K
      [PATCH] for_each_online_pgdat: renaming for_each_pgdat · ec936fc5
      KAMEZAWA Hiroyuki 提交于
      Replace for_each_pgdat() with for_each_online_pgdat().
      Signed-off-by: NKAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      ec936fc5
  4. 27 3月, 2006 13 次提交