1. 06 Jun, 2003 6 commits
    • Andrew Morton's avatar
      [PATCH] IRQs: fix up irq_desc initialisation for non-ia32 · 792fb4b7
      Andrew Morton authored
      The addition of more fields to irq_desc_t may have broken compilation of
      other architectures.  Go through and C99ify them (was needed anyway).
      792fb4b7
    • Andrew Morton's avatar
      [PATCH] IRQs: handle bad return values from handlers · 13c01fe7
      Andrew Morton authored
      Attempt to do something intelligent with IRQ handlers which don't return
      IRQ_HANDLED.
      
      - If they return neither IRQ_HANDLED nor IRQ_NONE, complain.
      
      - If they return IRQ_NONE more than 99900 times in 100000 interrupts, complain
        and disable the IRQ.
      
        I did have it at 750-in-1000, but someone had an otherwise-functioning
        system which triggered it.
      
        The 99.9% ratio is designed to address the problem wherein the babbling
        device shares an IRQ with a good device.  We don't want the good device's
        trickle of IRQ_HANDLED callouts to defeat the lockup detector.  (fat chance
        os this working right).
      
      - Add a kernel boot parameter `noirqdebug' to turn the whole thing off.
      13c01fe7
    • Andrew Morton's avatar
      [PATCH] per-cpu support inside modules (minimal) · 21af2f02
      Andrew Morton authored
      From: Rusty Russell <rusty@rustcorp.com.au>
      
      OK, this does the *minimum* required to support DEFINE_PER_CPU inside
      modules.  If we decide to change kmalloc_percpu later, great, we can turf
      this out.
      
      Basically, overallocates the amount of per-cpu data at boot to at least
      PERCPU_ENOUGH_ROOM if CONFIG_MODULES=y (arch-specific by default 32k: I have
      only 7744 bytes of percpu data in my kernel here, so makes sense), and a
      special allocator in module.c dishes it out.
      21af2f02
    • Andrew Morton's avatar
      [PATCH] kmalloc_percpu: interface change · 32028c70
      Andrew Morton authored
      From: Rusty Russell <rusty@rustcorp.com.au>
      
      Several tweaks to the kmalloc_percpu()/kfree_percpu() interface, to
      allow future implementations to be more flexible, and make easier to
      use now we can see how it's actually being used.
      
      1) No flags argument: GFP_ATOMIC doesn't make much sense,
      
      2) Explicit alignment argument, so we don't have to give SMP_CACHE_BYTES
         alignment always,
      
      3) Zeros memory, since most callers want that and it's not entirely
         trivial,
      
      4) Convenient type-safe wrapper which takes a typename, and
      
      5) Rename to alloc_percpu/__alloc_percpu, since usage no longer matches
         kmalloc.
      32028c70
    • Roman Zippel's avatar
      [PATCH] ignore attempts to change unchangable symbols · 6b206194
      Roman Zippel authored
      This fixes a problem which can show up with the new select facility, e.g.
      a symbol is forced to 'y', so we should never even try to change such
      symbols.
      6b206194
    • Roman Zippel's avatar
      [PATCH] boolean symbol state fix · cffbe99e
      Roman Zippel authored
      This is an important fix to allow changing boolean symbols, whose
      dependency is 'm'. All internal symbol states must be converted from
      the tristate into boolean the state.
      
      I missed this change while adding expression support for defaults,
      please apply.
      cffbe99e
  2. 05 Jun, 2003 34 commits