Eric Lee / smarc-fsl-linux-kernel

30 May, 2010

3 commits

28 Sep, 2009

1 commit

02 Sep, 2009

1 commit

  • d0420c83f   KEYS: Extend TIF_NOTIFY_RESUME to (almost) all architectures [try #6] ... Browse Code »

    Implement TIF_NOTIFY_RESUME for most of those architectures in which isn't yet
    available, and, whilst we're at it, have it call the appropriate tracehook.

    After this patch, blackfin, m68k* and xtensa still lack support and need
    alteration of assembly code to make it work.

    Resume notification can then be used (by a later patch) to install a new
    session keyring on the parent of a process.

    Signed-off-by: David Howells
    Acked-by: Russell King

    cc: linux-arch@vger.kernel.org
    Signed-off-by: James Morris

    David Howells
     

02 Aug, 2009

1 commit

31 Mar, 2009

3 commits

  • d75f054a2   parisc: add ftrace (function and graph tracer) functionality ... Browse Code »

    This patch adds the ftrace debugging functionality to the parisc kernel.
    It will currently only work with 64bit kernels, because the gcc options -pg
    and -ffunction-sections can't be enabled at the same time and -ffunction-sections
    is still needed to be able to link 32bit kernels.

    Signed-off-by: Helge Deller
    Signed-off-by: Kyle McMartin

    Helge Deller
     
  • afca25238   parisc: allow to build with 16k default kernel page size ... Browse Code »

    Introduce new convert_for_tlb_insert20 macro and use it to replace assembler
    statements with hardcoded constants.
    This change allows the parisc64 kernel to boot with 16kb default kernel page size,
    aka CONFIG_PARISC_PAGE_SIZE_16KB=y.

    Signed-off-by: Helge Deller
    Signed-off-by: Kyle McMartin

    Helge Deller
     
  • 1152a68c4   parisc: use constants instead of numbers in assembly ... Browse Code »

    A few small fixups:
    * _PAGE_SIZE_ENCODING_DEFAULT is wrong here, as one might assume that
    it's possible to define the page size that way. This is wrong. Use 0 instead.
    * use constants instead of hardcoded numerical values in depi and extru
    while building the PFN out of the pte entry
    * use SHRREG instead of extru (iitlba expects the PFN at bits {7..26})

    Still wondering why we can use the same register (pte) as extru source
    and target register, but it seems to work on PA1.1 and PA2.0...

    Signed-off-by: Helge Deller
    Signed-off-by: Kyle McMartin

    Helge Deller
     

13 Mar, 2009

1 commit

13 Jun, 2008

1 commit

15 May, 2008

2 commits

18 Oct, 2007

2 commits

30 May, 2007

2 commits

17 Feb, 2007

5 commits

04 Oct, 2006

3 commits

01 Jul, 2006

1 commit

28 Jun, 2006

1 commit

22 Apr, 2006

1 commit

  • 2fd830381   [PARISC] Further work for multiple page sizes ... Browse Code »

    More work towards supporing multiple page sizes on 64-bit. Convert
    some assumptions that 64bit uses 3 level page tables into testing
    PT_NLEVELS. Also some BUG() to BUG_ON() conversions and some cleanups
    to assembler.

    Signed-off-by: Helge Deller
    Signed-off-by: Kyle McMartin

    Helge Deller
     

31 Mar, 2006

2 commits

18 Nov, 2005

1 commit

22 Oct, 2005

5 commits

  • dd0fd51dc   [PARISC] Remove the spurious do_softirq calls from entry.S ... Browse Code »

    remove the spurious do_softirq calls from entry.S

    With these in we were calling do_softirq twice; plus the calls in
    entry.S took no account of nesting.

    Signed-off-by: James Bottomley

    Signed-off-by: Kyle McMartin

    James Bottomley
     
  • 618febd67   [PARISC] Fix the alloc_slabmgmt panic ... Browse Code »

    Fix the alloc_slabmgmt panic

    Hopefully this should also fix a lot of other intermittent kernel bugs.

    The problem has been around since 2.6.9-rc2-pa6 when we allowed
    floating point registers to be used in kernel code. The essence of
    the problem is that gcc prefers to use floating point for integer
    divides and multiples. Further, it can rely on the values in the no
    clobber fp regs being correct across a function call. Unfortunately,
    our task switch function only saves the integer no clobber registers,
    not the fp ones, so if gcc makes a function call to any function in
    the kernel which could sleep, the values it is relying on in any no
    clobber floating point register may be lost. In the case of
    alloc_slabmgmt, the value of the page offset is being stored in %fr12
    across a call to kmem_getpages(), which sleeps if no pages are
    available. Thus, the offset can be trashed and the slab code can end
    up with a completely bogus address leading to corruption.

    Kudos to Randolph who came up with the program to trip this problem at
    will and thus allowed it to be tracked and fixed.

    Signed-off-by: James Bottomley

    Signed-off-by: Kyle McMartin

    James Bottomley
     
  • 413059f28   [PARISC] Replace uses of __LP64__ with CONFIG_64BIT ... Browse Code »

    2.6.12-rc4-pa3 s/__LP64__/CONFIG_64BIT/ and fixup config.h usage

    Signed-off-by: Grant Grundler

    Signed-off-by: Kyle McMartin

    Grant Grundler
     
  • 99ac79479   [PARISC] Replace some calls to bl with b,l or bv to use longer offsets ... Browse Code »

    convert some bl calls to b,l or bv to use longer offsets

    Signed-off-by: Randolph Chung

    Signed-off-by: Kyle McMartin

    Randolph Chung
     
  • 896a37562   [PARISC] Make sure use of RFI conforms to PA 2.0 and 1.1 arch docs ... Browse Code »

    2.6.12-rc4-pa3 : first pass at making sure use of RFI conforms to
    PA 2.0 arch pages F-4 and F-5, PA 1.1 Arch page 3-19 and 3-20.

    The discussion revolves around all the rules for clearing PSW Q-bit.
    The hard part is meeting all the rules for "relied upon translation".

    .align directive is used to guarantee the critical sequence ends more than
    8 instructions (32 bytes) from the end of page.

    Signed-off-by: Grant Grundler

    Signed-off-by: Kyle McMartin

    Grant Grundler
     

10 Sep, 2005

1 commit

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