Eric Lee / smarc-fsl-linux-kernel

12 Oct, 2007

1 commit

22 Aug, 2007

1 commit

  • 0a87c5cfc   [S390] vmur: fix diag14 exceptions with addresses > 2GB. ... Browse Code »

    There are several s390 diagnose calls, which must be executed below the
    2GB memory boundary. In order to enforce this, those diagnoses must be
    compiled into the kernel. Currently diag 14 can be called within the
    vmur kernel module from addresses above 2GB. This leads to specification
    exceptions. This patch moves diag10, diag14 and diag210 into the new
    diag.c file.

    Signed-off-by: Michael Holzheu
    Signed-off-by: Martin Schwidefsky
    Signed-off-by: Heiko Carstens

    Michael Holzheu
     

27 Apr, 2007

2 commits

04 Dec, 2006

2 commits

  • ce26a8532   [S390] cio: Make ccw_dev_id_is_equal() more robust. ... Browse Code »

    Using memcmp to compare ccw_dev_id implies that the whole structure (incl.
    padding) has always been completely initialized to sane values. Comparing
    the structures field by field doesn't make such assumptions.

    Signed-off-by: Cornelia Huck
    Signed-off-by: Martin Schwidefsky

    Cornelia Huck
     
  • 15e9b586e   [S390] Reset infrastructure for re-IPL. ... Browse Code »

    In case of re-IPL and diag308 doesn't work we have to reset all devices
    manually and wait synchronously that each reset finished.
    This patch adds the necessary infrastucture and the first exploiter of it.

    Subsystems that need to add a function that needs to be called at re-IPL
    may register/unregister this function via

    struct reset_call {
    struct reset_call *next;
    void (*fn)(void);
    };

    void register_reset_call(struct reset_call *reset);
    void unregister_reset_call(struct reset_call *reset);

    When the registered function get called the context is:

    - all cpus beside the current one are stopped
    - all machine checks and interrupts are disabled
    - prefixing is disabled
    - a default machine check handler is available for use

    The registered functions may not take any locks are sleep.

    For the common I/O layer part of this patch:

    Introduce a reset_call css_reset that does the following:
    - clear all subchannels
    - perform a rchp on all channel paths and wait for the resulting
    machine checks
    This replaces the calls to clear_all_subchannels() and
    cio_reset_channel_paths() for kexec and ccw reipl. reipl_ccw_dev() now
    uses reipl_find_schid() to determine the subchannel id for a given
    device id.
    Also remove cio_reset_channel_paths() and friends since they are not
    needed anymore.

    Signed-off-by: Heiko Carstens
    Signed-off-by: Cornelia Huck
    Signed-off-by: Martin Schwidefsky

    Heiko Carstens
     

11 Oct, 2006

1 commit

20 Sep, 2006

1 commit

  • ff6b8ea68   [S390] ipl/dump on panic. ... Browse Code »

    It is now possible to specify a ccw/fcp dump device which is used to
    automatically create a system dump in case of a kernel panic. The dump
    device can be configured under /sys/firmware/dump.
    In addition it is now possible to specify a ccw/fcp device which is used
    for the next reboot of Linux. The reipl device can be configured under
    /sys/firmware/reipl.

    Signed-off-by: Michael Holzheu
    Signed-off-by: Martin Schwidefsky

    Michael Holzheu
     

12 Jul, 2006

1 commit

  • 7e560814d   [S390] path grouping and path verifications fixes. ... Browse Code »

    1. Multipath devices for which SetPGID is not supported are not handled well.
    Use NOP ccws for path verification (sans path grouping) when SetPGID is not
    supported.
    2. Check for PGIDs already set with SensePGID on _all_ paths (not just the
    first one) and try to find a common one. Moan if no common PGID can be
    found (and use NOP verification). If no PGIDs have been set, use the css
    global PGID (as before). (Rationale: SetPGID will get a command reject if
    the PGID it tries to set does not match the already set PGID.)
    3. Immediately before reboot, issue RESET CHANNEL PATH (rcp) on all chpids. This
    will remove the old PGIDs. rcp will generate solicited CRWs which can be
    savely ignored by the machine check handler (all other actions create
    unsolicited CRWs).

    Signed-off-by: Cornelia Huck
    Signed-off-by: Martin Schwidefsky

    Cornelia Huck
     

29 Jun, 2006

1 commit

  • 40154b824   [S390] cio async subchannel reprobe. ... Browse Code »

    Changes in the DASD driver require an asynchronous implementation of the
    subchannel reprobe loop. This loop was so far only used by the blacklisting
    mechanism but is now available to all CCW device drivers.

    Signed-off-by: Peter Oberparleiter
    Signed-off-by: Martin Schwidefsky

    Peter Oberparleiter
     

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