Eric Lee / smarc-fsl-linux-kernel

12 Oct, 2007

2 commits

11 Sep, 2007

1 commit

  • 7b0fdaa6a   [MIPS] Provide empty irq_enable_hazard definition for legacy and R1 cores. ... Browse Code »

    Following a strict interpretation the empty definition of irq_enable_hazard
    has always been a bug - but an intentional one because it didn't bite.
    This has now changed, for uniprocessor kernels mm/slab.c:do_drain()

    [...]
    on_each_cpu(do_drain, cachep, 1, 1);
    check_irq_on();
    [...]

    may be compiled into a mtc0 c0_status; mfc0 c0_status sequence resulting
    in a back-to-back hazard.

    Signed-off-by: Ralf Baechle

    Ralf Baechle
     

01 Aug, 2007

1 commit

11 May, 2007

2 commits

25 Mar, 2007

1 commit

  • 7605b3906   [MIPS] Fix pipeline hazard. ... Browse Code »

    In the the sequence:
    ei
    ..
    mfc0 $x, $status

    the mfc0 may not see the SR_IE bit set. This was a deliberate bug in the
    kernel code because we knew this was a safe thing to do on all R2 silicon
    so far but new silicon is changing this.

    Signed-off-by: Ralf Baechle

    Ralf Baechle
     

25 Jan, 2007

1 commit

27 Sep, 2006

2 commits

30 Jun, 2006

1 commit

26 Apr, 2006

1 commit

19 Apr, 2006

1 commit

19 Mar, 2006

1 commit

07 Feb, 2006

1 commit

10 Jan, 2006

1 commit

  • 7043ad4f4   MIPS: R2: Try to bulletproof instruction_hazard against miss-compilation. ... Browse Code »

    Gcc has a tradition of misscompiling the previous construct using the
    address of a label as argument to inline assembler. Gas otoh has the
    annoying difference between la and dla which are only usable for 32-bit
    rsp. 64-bit code, so can't be used without conditional compilation.
    The alterantive is switching the assembler to 64-bit code which happens
    to work right even for 32-bit code ...

    Signed-off-by: Ralf Baechle

    Ralf Baechle
     

30 Oct, 2005

6 commits

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