1. 26 6月, 2005 2 次提交
    • R
      [PATCH] ppc64: kexec support for ppc64 · fce0d574
      R Sharada 提交于
      This patch implements the kexec support for ppc64 platforms.
      
      A couple of notes:
      
      1)  We copy the pages in virtual mode, using the full base kernel
          and a statically allocated stack.   At kexec_prepare time we
          scan the pages and if any overlap our (0, _end[]) range we
          return -ETXTBSY.
      
          On PowerPC 64 systems running in LPAR (logical partitioning)
          mode, only a small region of memory, referred to as the RMO,
          can be accessed in real mode.  Since Linux runs with only one
          zone of memory in the memory allocator, and it can be orders of
          magnitude more memory than the RMO, looping until we allocate
          pages in the source region is not feasible.  Copying in virtual
          means we don't have to write a hash table generation and call
          hypervisor to insert translations, instead we rely on the pinned
          kernel linear mapping.  The kernel already has move to linked
          location built in, so there is no requirement to load it at 0.
      
          If we want to load something other than a kernel, then a stub
          can be written to copy a linear chunk in real mode.
      
      2)  The start entry point gets passed parameters from the kernel.
          Slaves are started at a fixed address after copying code from
          the entry point.
      
          All CPUs get passed their firmware assigned physical id in r3
          (most calling conventions use this register for the first
          argument).
      
          This is used to distinguish each CPU from all other CPUs.
          Since firmware is not around, there is no other way to obtain
          this information other than to pass it somewhere.
      
          A single CPU, referred to here as the master and the one executing
          the kexec call, branches to start with the address of start in r4.
          While this can be calculated, we have to load it through a gpr to
          branch to this point so defining the register this is contained
          in is free.  A stack of unspecified size is available at r1
          (also common calling convention).
      
          All remaining running CPUs are sent to start at absolute address
          0x60 after copying the first 0x100 bytes from start to address 0.
          This convention was chosen because it matches what the kernel
          has been doing itself.  (only gpr3 is defined).
      
          Note: This is not quite the convention of the kexec bootblock v2
          in the kernel.  A stub has been written to convert between them,
          and we may adjust the kernel in the future to allow this directly
          without any stub.
      
      3)  Destination pages can be placed anywhere, even where they
          would not be accessible in real mode.  This will allow us to
          place ram disks above the RMO if we choose.
      Signed-off-by: NMilton Miller <miltonm@bga.com>
      Signed-off-by: NR Sharada <sharada@in.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      fce0d574
    • I
      [PATCH] consolidate PREEMPT options into kernel/Kconfig.preempt · cc19ca86
      Ingo Molnar 提交于
      This patch consolidates the CONFIG_PREEMPT and CONFIG_PREEMPT_BKL
      preemption options into kernel/Kconfig.preempt.  This, besides reducing
      source-code, also enables more centralized tweaking of preemption related
      options.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      cc19ca86
  2. 24 6月, 2005 6 次提交
  3. 23 6月, 2005 2 次提交
    • A
      [PATCH] ppc64: Add driver for BPA interrupt controllers · cebf589c
      Arnd Bergmann 提交于
      Add support for the integrated interrupt controller on BPA
      CPUs. There is one of those for each SMT thread.
      
      The mapping of interrupt numbers to HW interrupt sources
      is described in arch/ppc64/kernel/bpa_iic.h.
      
      This version hardcodes the 'Spider' chip as the secondary
      interrupt controller. That is not really generic for the
      architecture, but at the moment it is the only secondary
      PIC that exists.
      
      A little more work will be needed on this as soon as
      we have boards with multiple external interrupt controllers.
      Signed-off-by: NArnd Bergmann <arndb@de.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      cebf589c
    • A
      [PATCH] ppc64: add BPA platform type · fef1c772
      Arnd Bergmann 提交于
      This adds the basic support for running on BPA machines.
      So far, this is only the IBM workstation, and it will
      not run on others without a little more generalization.
      
      It should be possible to configure a kernel for any
      combination of CONFIG_PPC_BPA with any of the other
      multiplatform targets.
      Signed-off-by: NArnd Bergmann <arndb@de.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      fef1c772
  4. 22 6月, 2005 1 次提交
  5. 07 5月, 2005 1 次提交
  6. 06 5月, 2005 1 次提交
  7. 04 5月, 2005 1 次提交
    • A
      [PATCH] ISA DMA Kconfig fixes - part 1 · 5cae841b
      Al Viro 提交于
      A bunch of drivers use ISA DMA helpers or their equivalents for
      platforms that have ISA with different DMA controller (a lot of ARM
      boxen).  Currently there is no way to put such dependency in Kconfig -
      CONFIG_ISA is not it (e.g.  it is not set on platforms that have no ISA
      slots, but have on-board devices that pretend to be ISA ones).
      
      New symbol added - ISA_DMA_API.  Set when we have functional
      enable_dma()/set_dma_mode()/etc.  set of helpers.  Next patches in the
      series will add missing dependencies for drivers that need them.
      
      I'm very carefully staying the hell out of the recurring flamefest on
      what exactly CONFIG_ISA would mean in ideal world - added symbol has a
      well-defined meaning and for now I really want to treat it as completely
      independent from the mess around CONFIG_ISA.
      Signed-off-by: NAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      5cae841b
  8. 17 4月, 2005 2 次提交
    • A
      [PATCH] ppc64: remove -fno-omit-frame-pointer · 89e09f5e
      Anton Blanchard 提交于
      During some code inspection using gcc 4.0 I noticed a stack frame was being
      created for a number of functions that didnt require it.  For example:
      
      c0000000000df944 <._spin_unlock>:
      c0000000000df944:       fb e1 ff f0     std     r31,-16(r1)
      c0000000000df948:       f8 21 ff c1     stdu    r1,-64(r1)
      c0000000000df94c:       7c 3f 0b 78     mr      r31,r1
      c0000000000df950:       7c 20 04 ac     lwsync
      c0000000000df954:       e8 21 00 00     ld      r1,0(r1)
      c0000000000df958:       38 00 00 00     li      r0,0
      c0000000000df95c:       90 03 00 00     stw     r0,0(r3)
      c0000000000df960:       eb e1 ff f0     ld      r31,-16(r1)
      c0000000000df964:       4e 80 00 20     blr
      
      It turns out we are adding -fno-omit-frame-pointer to ppc64 which is
      causing the above behaviour.  Removing that flag results in much better
      code:
      
      c0000000000d5b30 <._spin_unlock>:
      c0000000000d5b30:       7c 20 04 ac     lwsync
      c0000000000d5b34:       38 00 00 00     li      r0,0
      c0000000000d5b38:       90 03 00 00     stw     r0,0(r3)
      c0000000000d5b3c:       4e 80 00 20     blr
      
      We dont require a frame pointer to debug on ppc64, so remove it.
      Signed-off-by: NAnton Blanchard <anton@samba.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      89e09f5e
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4