Eric Lee / smarc-fsl-linux-kernel

13 Dec, 2006

1 commit

  • 45a98fc62   [IA64] CONFIG_KEXEC/CONFIG_CRASH_DUMP permutations ... Browse Code »

    Actually, on reflection I think that there is a good case for
    keeping the options separate. I am thinking particularly of people
    who want a very small crashdump kernel and thus don't want to compile
    in kexec.

    The patch below should fix things up so that all valid combinations of
    KEXEC, CRASH_DUMP and VMCORE compile cleanly - VMCORE depends on
    CRASH_DUMP which is why I said valid combinations. In a nutshell
    it just untangles unrelated code and switches around a few defines.

    Please note that it creats a new file, arch/ia64/kernel/crash_dump.c
    This is in keeping with the i386 implementation.

    Signed-off-by: Simon Horman
    Signed-off-by: Tony Luck

    Horms
     

08 Dec, 2006

1 commit

  • a79561134   [IA64] IA64 Kexec/kdump ... Browse Code »

    Changes and updates.

    1. Remove fake rendz path and related code according to discuss with Khalid Aziz.
    2. fc.i offset fix in relocate_kernel.S.
    3. iospic shutdown code eoi and mask race fix from Fujitsu.
    4. Warm boot hook in machine_kexec to SN SAL code from Jack Steiner.
    5. Send slave to SAL slave loop patch from Jay Lan.
    6. Kdump on non-recoverable MCA event patch from Jay Lan
    7. Use CTL_UNNUMBERED in kdump_on_init sysctl.

    Signed-off-by: Zou Nan hai
    Signed-off-by: Tony Luck

    Zou Nan hai
     

06 Dec, 2006

1 commit

05 Oct, 2006

1 commit

  • 7d12e780e   IRQ: Maintain regs pointer globally rather than passing to IRQ handlers ... Browse Code »

    Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
    of passing regs around manually through all ~1800 interrupt handlers in the
    Linux kernel.

    The regs pointer is used in few places, but it potentially costs both stack
    space and code to pass it around. On the FRV arch, removing the regs parameter
    from all the genirq function results in a 20% speed up of the IRQ exit path
    (ie: from leaving timer_interrupt() to leaving do_IRQ()).

    Where appropriate, an arch may override the generic storage facility and do
    something different with the variable. On FRV, for instance, the address is
    maintained in GR28 at all times inside the kernel as part of general exception
    handling.

    Having looked over the code, it appears that the parameter may be handed down
    through up to twenty or so layers of functions. Consider a USB character
    device attached to a USB hub, attached to a USB controller that posts its
    interrupts through a cascaded auxiliary interrupt controller. A character
    device driver may want to pass regs to the sysrq handler through the input
    layer which adds another few layers of parameter passing.

    I've build this code with allyesconfig for x86_64 and i386. I've runtested the
    main part of the code on FRV and i386, though I can't test most of the drivers.
    I've also done partial conversion for powerpc and MIPS - these at least compile
    with minimal configurations.

    This will affect all archs. Mostly the changes should be relatively easy.
    Take do_IRQ(), store the regs pointer at the beginning, saving the old one:

    struct pt_regs *old_regs = set_irq_regs(regs);

    And put the old one back at the end:

    set_irq_regs(old_regs);

    Don't pass regs through to generic_handle_irq() or __do_IRQ().

    In timer_interrupt(), this sort of change will be necessary:

    - update_process_times(user_mode(regs));
    - profile_tick(CPU_PROFILING, regs);
    + update_process_times(user_mode(get_irq_regs()));
    + profile_tick(CPU_PROFILING);

    I'd like to move update_process_times()'s use of get_irq_regs() into itself,
    except that i386, alone of the archs, uses something other than user_mode().

    Some notes on the interrupt handling in the drivers:

    (*) input_dev() is now gone entirely. The regs pointer is no longer stored in
    the input_dev struct.

    (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
    something different depending on whether it's been supplied with a regs
    pointer or not.

    (*) Various IRQ handler function pointers have been moved to type
    irq_handler_t.

    Signed-Off-By: David Howells
    (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)

    David Howells
     

01 Oct, 2006

1 commit

27 Sep, 2006

2 commits

  • ddb4f0df0   [IA64] CMC/CPE: Reverse the order of fetching log and checking poll threshold ... Browse Code »

    This patch reverses the order of fetching log from SAL and
    checking poll threshold. This will fix following trivial issues:

    - If SAL_GET_SATE_INFO is unbelievably slow (due to huge system
    or just its silly implementation) and if it takes more than
    1/5 sec, CMCI/CPEI will never switch to CMCP/CPEP.
    - Assuming terrible flood of interrupt (continuous corrected
    errors let all CPUs enter to handler at once and bind them
    in it), CPUs will be serialized by IA64_LOG_LOCK(*).
    Now we check the poll threshold after the lock and log fetch,
    so we need to call SAL_GET_STATE_INFO (num_online_cpus() + 4)
    times in the worst case.
    if we can check the threshold before the lock, we can shut up
    interrupts quickly without waiting preceding log fetches, and
    the number of times will be reduced to (num_online_cpus()) in
    the same situation.

    Signed-off-by: Hidetoshi Seto
    Signed-off-by: Tony Luck

    Hidetoshi Seto
     
  • 43ed3baf6   [IA64] printing support for MCA/INIT ... Browse Code »

    Printing message to console from MCA/INIT handler is useful,
    however doing oops_in_progress = 1 in them exactly makes
    something in kernel wrong. Especially it sounds ugly if
    system goes wrong after returning from recoverable MCA.

    This patch adds ia64_mca_printk() function that collects
    messages into temporary-not-so-large message buffer during
    in MCA/INIT environment and print them out later, after
    returning to normal context or when handlers determine to
    down the system.

    Also this print function is exported for use in extensional
    MCA handler. It would be useful to describe detail about
    recovery.

    NOTE:
    I don't think it is sane thing if temporary message buffer
    is enlarged enough to hold whole stack dumps from INIT, so
    buffering is disabled during stack dump from INIT-monarch
    (= default_monarch_init_process). please fix it in future.

    Signed-off-by: Hidetoshi Seto
    Acked-by: Russ Anderson
    Signed-off-by: Tony Luck

    Hidetoshi Seto
     

04 Jul, 2006

1 commit

03 Jul, 2006

1 commit

01 Jul, 2006

1 commit

30 Jun, 2006

1 commit

14 Apr, 2006

1 commit

  • 356a5c1c6   [IA64] ia64_wait_for_slaves() incorrectly reports MCA ... Browse Code »

    ia64_wait_for_slaves() was changed in 2.6.17-rc1 to report the slave
    state. It incorrectly assumes that all slaves are for MCA, but
    ia64_wait_for_slaves() is also called from the INIT monarch handler.
    The existing message is very misleading, so correct it.

    Signed-off-by: Keith Owens
    Signed-off-by: Tony Luck

    Keith Owens
     

08 Apr, 2006

1 commit

  • 958b166c0   [IA64] Pass more data to the MCA/INIT notify_die hooks ... Browse Code »

    The MCA/INIT handlers maintain important state in the SAL to OS (sos)
    area and in the monarch_cpu flag. Kernel debuggers (such as KDB) need
    this data, and may need to adjust the monarch_cpu field so make the
    data available to the notify_die hooks. Define two more events for
    calling the functions on the notify_die chain.

    Signed-off-by: Keith Owens
    Signed-off-by: Tony Luck

    Keith Owens
     

27 Mar, 2006

1 commit

25 Mar, 2006

1 commit

  • d2a28ad9f   [IA64] MCA recovery: kernel context recovery table ... Browse Code »

    Memory errors encountered by user applications may surface
    when the CPU is running in kernel context. The current code
    will not attempt recovery if the MCA surfaces in kernel
    context (privilage mode 0). This patch adds a check for cases
    where the user initiated the load that surfaces in kernel
    interrupt code.

    An example is a user process lauching a load from memory
    and the data in memory had bad ECC. Before the bad data
    gets to the CPU register, and interrupt comes in. The
    code jumps to the IVT interrupt entry point and begins
    execution in kernel context. The process of saving the
    user registers (SAVE_REST) causes the bad data to be loaded
    into a CPU register, triggering the MCA. The MCA surfaces in
    kernel context, even though the load was initiated from
    user context.

    As suggested by David and Tony, this patch uses an exception
    table like approach, puting the tagged recovery addresses in
    a searchable table. One difference from the exception table
    is that MCAs do not surface in precise places (such as with
    a TLB miss), so instead of tagging specific instructions,
    address ranges are registers. A single macro is used to do
    the tagging, with the input parameter being the label
    of the starting address and the macro being the ending
    address. This limits clutter in the code.

    This patch only tags one spot, the interrupt ivt entry.
    Testing showed that spot to be a "heavy hitter" with
    MCAs surfacing while saving user registers. Other spots
    can be added as needed by adding a single macro.

    Signed-off-by: Russ Anderson (rja@sgi.com)
    Signed-off-by: Tony Luck

    Russ Anderson
     

23 Mar, 2006

1 commit

22 Mar, 2006

2 commits

09 Feb, 2006

3 commits

13 Jan, 2006

1 commit

  • ab03591db   [PATCH] ia64: task_thread_info() ... Browse Code »

    on ia64 thread_info is at the constant offset from task_struct and stack
    is embedded into the same beast. Set __HAVE_THREAD_FUNCTIONS, made
    task_thread_info() just add a constant.

    Signed-off-by: Al Viro
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Al Viro
     

06 Jan, 2006

1 commit

  • ff741906a   [IA64] support for cpu0 removal ... Browse Code »

    here is the BSP removal support for IA64. Its pretty much the same thing that
    was released a while back, but has your feedback incorporated.

    - Removed CONFIG_BSP_REMOVE_WORKAROUND and associated cmdline param
    - Fixed compile issue with sn2/zx1 due to a undefined fix_b0_for_bsp
    - some formatting nits (whitespace etc)

    This has been tested on tiger and long back by alex on hp systems as well.

    Signed-off-by: Ashok Raj
    Signed-off-by: Tony Luck

    Ashok Raj
     

08 Nov, 2005

1 commit

  • 9138d581b   [IA64] Extend notify_die() hooks for IA64 ... Browse Code »

    notify_die() added for MCA_{MONARCH,SLAVE,RENDEZVOUS}_{ENTER,PROCESS,LEAVE} and
    INIT_{MONARCH,SLAVE}_{ENTER,PROCESS,LEAVE}. We need multiple
    notification points for these events because they can take many seconds
    to run which has nasty effects on the behaviour of the rest of the
    system.

    DIE_SS replaced by a generic DIE_FAULT which checks the vector number,
    to allow interception of faults other than SS.

    DIE_MACHINE_{HALT,RESTART} added to allow last minute close down
    processing, especially when the halt/restart routines are called from
    error handlers.

    DIE_OOPS added.

    The check for kprobe's break numbers has been moved from traps.c to
    kprobes.c, allowing DIE_BREAK to be used for any additional break
    numbers, i.e. it is no longer kprobes specific.

    Hooks for kernel debuggers and kernel dumpers added, ENTER and LEAVE.
    Both of these disable the system for long periods which impact on
    watchdogs and heartbeat systems in general. More patches to come that
    use these events to reset watchdogs and heartbeats.

    unregister_die_notifier() added and both routines exported. Requested
    by Dean Nelson.

    Lock removed from {un,}register_die_notifier. notifier_chain_register()
    already takes a lock. Also the generic notifier chain locking is being
    reworked to distinguish between callbacks that can block and those that
    cannot, the lock in {un,}register_die_notifier would interfere with
    that change. http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2

    Leading white space removed from arch/ia64/kernel/kprobes.c.

    Typo in mca.c in original version of this patch found & fixed by Dean
    Nelson.

    Signed-off-by: Keith Owens
    Acked-by: Dean Nelson
    Acked-by: Anil Keshavamurthy
    Signed-off-by: Tony Luck

    Keith Owens
     

26 Oct, 2005

1 commit

  • ddf6d0a00   [IA64] another place to use for_each_cpu_mask() in arch/ia64 ... Browse Code »

    In arch/ia64 change the explicit use of a for-loop using NR_CPUS into the
    general for_each_online_cpu() construct. This widens the scope of potential
    future optimizations of the general constructs, as well as takes advantage
    of the existing optimizations of first_cpu() and next_cpu(), which is
    advantageous when the true CPU count is much smaller than NR_CPUS.

    Signed-off-by: John Hawkes
    Signed-off-by: Tony Luck

    hawkes@sgi.com
     

07 Oct, 2005

1 commit

  • 76e677e25   [IA64] Avoid kernel hang during CMC interrupt storm ... Browse Code »

    I've noticed a kernel hang during a storm of CMC interrupts, which was
    tracked down to the continual execution of the interrupt handler.

    There's code in the CMC handler that's supposed to disable CMC
    interrupts and switch to polling mode when it sees a bunch of CMCs.
    Because disabling CMCs across all CPUs isn't safe in interrupt context,
    the disable is done with a schedule_work(). But with continual CMC
    interrupts, the schedule_work() never gets executed.

    The following patch immediately disables CMC interrupts for the current
    CPU. This then allows (at least) one CPU to ignore CMC interrupts,
    execute the schedule_work() code, and disable CMC interrupts on the rest
    of the CPUs.

    Acked-by: Keith Owens
    Signed-off-by: Bryan Sutula
    Signed-off-by: Tony Luck

    Bryan Sutula
     

12 Sep, 2005

1 commit

  • 7f613c7d2   [PATCH] MCA/INIT: use per cpu stacks ... Browse Code »

    The bulk of the change. Use per cpu MCA/INIT stacks. Change the SAL
    to OS state (sos) to be per process. Do all the assembler work on the
    MCA/INIT stacks, leaving the original stack alone. Pass per cpu state
    data to the C handlers for MCA and INIT, which also means changing the
    mca_drv interfaces slightly. Lots of verification on whether the
    original stack is usable before converting it to a sleeping process.

    Signed-off-by: Keith Owens
    Signed-off-by: Tony Luck

    Keith Owens
     

11 Sep, 2005

1 commit

  • fb1c8f93d   [PATCH] spinlock consolidation ... Browse Code »

    This patch (written by me and also containing many suggestions of Arjan van
    de Ven) does a major cleanup of the spinlock code. It does the following
    things:

    - consolidates and enhances the spinlock/rwlock debugging code

    - simplifies the asm/spinlock.h files

    - encapsulates the raw spinlock type and moves generic spinlock
    features (such as ->break_lock) into the generic code.

    - cleans up the spinlock code hierarchy to get rid of the spaghetti.

    Most notably there's now only a single variant of the debugging code,
    located in lib/spinlock_debug.c. (previously we had one SMP debugging
    variant per architecture, plus a separate generic one for UP builds)

    Also, i've enhanced the rwlock debugging facility, it will now track
    write-owners. There is new spinlock-owner/CPU-tracking on SMP builds too.
    All locks have lockup detection now, which will work for both soft and hard
    spin/rwlock lockups.

    The arch-level include files now only contain the minimally necessary
    subset of the spinlock code - all the rest that can be generalized now
    lives in the generic headers:

    include/asm-i386/spinlock_types.h | 16
    include/asm-x86_64/spinlock_types.h | 16

    I have also split up the various spinlock variants into separate files,
    making it easier to see which does what. The new layout is:

    SMP | UP
    ----------------------------|-----------------------------------
    asm/spinlock_types_smp.h | linux/spinlock_types_up.h
    linux/spinlock_types.h | linux/spinlock_types.h
    asm/spinlock_smp.h | linux/spinlock_up.h
    linux/spinlock_api_smp.h | linux/spinlock_api_up.h
    linux/spinlock.h | linux/spinlock.h

    /*
    * here's the role of the various spinlock/rwlock related include files:
    *
    * on SMP builds:
    *
    * asm/spinlock_types.h: contains the raw_spinlock_t/raw_rwlock_t and the
    * initializers
    *
    * linux/spinlock_types.h:
    * defines the generic type and initializers
    *
    * asm/spinlock.h: contains the __raw_spin_*()/etc. lowlevel
    * implementations, mostly inline assembly code
    *
    * (also included on UP-debug builds:)
    *
    * linux/spinlock_api_smp.h:
    * contains the prototypes for the _spin_*() APIs.
    *
    * linux/spinlock.h: builds the final spin_*() APIs.
    *
    * on UP builds:
    *
    * linux/spinlock_type_up.h:
    * contains the generic, simplified UP spinlock type.
    * (which is an empty structure on non-debug builds)
    *
    * linux/spinlock_types.h:
    * defines the generic type and initializers
    *
    * linux/spinlock_up.h:
    * contains the __raw_spin_*()/etc. version of UP
    * builds. (which are NOPs on non-debug, non-preempt
    * builds)
    *
    * (included on UP-non-debug builds:)
    *
    * linux/spinlock_api_up.h:
    * builds the _spin_*() APIs.
    *
    * linux/spinlock.h: builds the final spin_*() APIs.
    */

    All SMP and UP architectures are converted by this patch.

    arm, i386, ia64, ppc, ppc64, s390/s390x, x64 was build-tested via
    crosscompilers. m32r, mips, sh, sparc, have not been tested yet, but should
    be mostly fine.

    From: Grant Grundler

    Booted and lightly tested on a500-44 (64-bit, SMP kernel, dual CPU).
    Builds 32-bit SMP kernel (not booted or tested). I did not try to build
    non-SMP kernels. That should be trivial to fix up later if necessary.

    I converted bit ops atomic_hash lock to raw_spinlock_t. Doing so avoids
    some ugly nesting of linux/*.h and asm/*.h files. Those particular locks
    are well tested and contained entirely inside arch specific code. I do NOT
    expect any new issues to arise with them.

    If someone does ever need to use debug/metrics with them, then they will
    need to unravel this hairball between spinlocks, atomic ops, and bit ops
    that exist only because parisc has exactly one atomic instruction: LDCW
    (load and clear word).

    From: "Luck, Tony"

    ia64 fix

    Signed-off-by: Ingo Molnar
    Signed-off-by: Arjan van de Ven
    Signed-off-by: Grant Grundler
    Cc: Matthew Wilcox
    Signed-off-by: Hirokazu Takata
    Signed-off-by: Mikael Pettersson
    Signed-off-by: Benoit Boissinot
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Ingo Molnar
     

12 Jul, 2005

1 commit

02 Jun, 2005

1 commit

18 May, 2005

1 commit

  • bb68c12b4   [IA64-SGI] cpe interrupts are not being enabled. ... Browse Code »

    acpi_request_vector() is called in ia64_mca_init() to get the cpe_vector.
    The problem is that acpi_request_vector() looks in platform_intr_list[] to
    get the vector, but platform_intr_list[] is not initialized with a valid
    vector until later (in sn_setup()). Without a valid vector the code
    defaults to polling mode.

    This patch moves the call to acpi_request_vector() from ia64_mca_init()
    to ia64_mca_late_init(), which is after platform_intr_list[] is initialized.

    Signed-off-by: Russ Anderson (rja@sgi.com)
    Signed-off-by: Tony Luck

    Russ Anderson
     

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    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!

    Linus Torvalds