09 Jun, 2009

1 commit


08 Jun, 2009

6 commits


07 Jun, 2009

1 commit


06 Jun, 2009

1 commit

  • The powernow-k8 driver checks to see that the Performance Control/Status
    Registers are declared as FFH (functional fixed hardware) by the BIOS.
    However, this check got broken in the commit:
    0e64a0c982c06a6b8f5e2a7f29eb108fdf257b2f
    [CPUFREQ] checkpatch cleanups for powernow-k8

    Fix based on an original patch from Naga Chumbalkar.

    Signed-off-by: Naga Chumbalkar
    Cc: Mark Langsdorf
    Signed-off-by: Dave Jones

    Dave Jones
     

05 Jun, 2009

2 commits


04 Jun, 2009

4 commits


03 Jun, 2009

3 commits


02 Jun, 2009

1 commit


01 Jun, 2009

1 commit


30 May, 2009

4 commits

  • * 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6:
    ACPI, i915: build fix (v2)
    acpi-cpufreq: fix printk typo and indentation
    ACPI processor: remove spurious newline from warning message
    drm/i915: acpi/video.c fix section mismatch warning
    ACPI: video: DMI workaround broken Acer 5315 BIOS enabling display brightness
    ACPI: video: DMI workaround broken eMachines E510 BIOS enabling display brightness
    ACPI: sanity check _PSS frequency to prevent cpufreq crash
    i7300_idle: allow testing on i5000-series hardware w/o re-compile
    PCI/ACPI: fix wrong ref count handling in acpi_pci_bind()
    cpuidle: fix AMD C1E suspend hang
    cpuidle: makes AMD C1E work in acpi_idle

    Linus Torvalds
     
  • Signed-off-by: Joe Perches
    Signed-off-by: Andrew Morton
    Signed-off-by: Len Brown

    Joe Perches
     
  • CSUM copy to/from user assembler was missing allocatable and
    executable attributes for .fixup

    Signed-off-by: David S. Miller

    David S. Miller
     
  • * master.kernel.org:/home/rmk/linux-2.6-arm:
    [ARM] update mach-types
    [ARM] Add cmpxchg support for ARMv6+ systems (v5)
    [ARM] barriers: improve xchg, bitops and atomic SMP barriers
    Gemini: Fix SRAM/ROM location after memory swap
    MAINTAINER: Add F: entries for Gemini and FA526
    [ARM] disable NX support for OABI-supporting kernels
    [ARM] add coherent DMA mask for mv643xx_eth
    [ARM] pxa/palm: fix PalmLD/T5/TX AC97 MFP
    [ARM] pxa: add parameter to clksrc_read() for pxa168/910
    [ARM] pxa: fix the incorrectly defined drive strength macros for pxa{168,910}
    [ARM] Orion: Remove explicit name for platform device resources
    [ARM] Kirkwood: Correct MPP for SATA activity/presence LEDs of QNAP TS-119/TS-219.
    [ARM] pxa/ezx: fix pin configuration for low power mode
    [ARM] pxa/spitz: provide spitz_ohci_exit() that unregisters USB_HOST GPIO
    [ARM] pxa: enable GPIO receivers after configuring pins
    [ARM] pxa: allow gpio_reset drive high during normal work
    [ARM] pxa: save/restore PGSR on suspend/resume.

    Linus Torvalds
     

29 May, 2009

6 commits

  • Addresses http://bugzilla.kernel.org/show_bug.cgi?id=13302

    On x86 and x86-64, it is possible that page tables are shared beween
    shared mappings backed by hugetlbfs. As part of this,
    page_table_shareable() checks a pair of vma->vm_flags and they must match
    if they are to be shared. All VMA flags are taken into account, including
    VM_LOCKED.

    The problem is that VM_LOCKED is cleared on fork(). When a process with a
    shared memory segment forks() to exec() a helper, there will be shared
    VMAs with different flags. The impact is that the shared segment is
    sometimes considered shareable and other times not, depending on what
    process is checking.

    What happens is that the segment page tables are being shared but the
    count is inaccurate depending on the ordering of events. As the page
    tables are freed with put_page(), bad pmd's are found when some of the
    children exit. The hugepage counters also get corrupted and the Total and
    Free count will no longer match even when all the hugepage-backed regions
    are freed. This requires a reboot of the machine to "fix".

    This patch addresses the problem by comparing all flags except VM_LOCKED
    when deciding if pagetables should be shared or not for hugetlbfs-backed
    mapping.

    Signed-off-by: Mel Gorman
    Acked-by: Hugh Dickins
    Cc: Ingo Molnar
    Cc:
    Cc: Lee Schermerhorn
    Cc: KOSAKI Motohiro
    Cc:
    Cc: Eric B Munson
    Cc: Adam Litke
    Cc: Andy Whitcroft
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mel Gorman
     
  • The flat loader uses an architecture's flat_stack_align() to align the
    stack but assumes word-alignment is enough for the data sections.

    However, on the Xtensa S6000 we have registers up to 128bit width
    which can be used from userspace and therefor need userspace stack and
    data-section alignment of at least this size.

    This patch drops flat_stack_align() and uses the same alignment that
    is required for slab caches, ARCH_SLAB_MINALIGN, or wordsize if it's
    not defined by the architecture.

    It also fixes m32r which was obviously kaput, aligning an
    uninitialized stack entry instead of the stack pointer.

    [akpm@linux-foundation.org: coding-style fixes]
    Signed-off-by: Oskar Schirmer
    Cc: David Howells
    Cc: Russell King
    Cc: Bryan Wu
    Cc: Geert Uytterhoeven
    Acked-by: Paul Mundt
    Cc: Greg Ungerer
    Signed-off-by: Johannes Weiner
    Acked-by: Mike Frysinger
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Oskar Schirmer
     
  • Russell King
     
  • Signed-off-by: Russell King

    Russell King
     
  • Add cmpxchg/cmpxchg64 support for ARMv6K and ARMv7 systems
    (original patch from Catalin Marinas )

    The cmpxchg and cmpxchg64 functions can be implemented using the
    LDREX*/STREX* instructions. Since operand lengths other than 32bit are
    required, the full implementations are only available if the ARMv6K
    extensions are present (for the LDREXB, LDREXH and LDREXD instructions).

    For ARMv6, only 32-bits cmpxchg is available.

    Mathieu :

    Make cmpxchg_local always available with best implementation for all type sizes (1, 2, 4 bytes).
    Make cmpxchg64_local always available.

    Use "Ir" constraint for "old" operand, like atomic.h atomic_cmpxchg does.

    Change since v3 :
    - Add "memory" clobbers (thanks to Nicolas Pitre)
    - removed __asmeq(), only needed for old compilers, very unlikely on ARMv6+.

    Note : ARMv7-M should eventually be ifdefed-out of cmpxchg64. But it's not
    supported by the Linux kernel currently.

    Put back arm < v6 cmpxchg support.

    Signed-off-by: Mathieu Desnoyers
    CC: Catalin Marinas
    CC: Nicolas Pitre
    Signed-off-by: Russell King

    Mathieu Desnoyers
     
  • Mathieu Desnoyers pointed out that the ARM barriers were lacking:

    - cmpxchg, xchg and atomic add return need memory barriers on
    architectures which can reorder the relative order in which memory
    read/writes can be seen between CPUs, which seems to include recent
    ARM architectures. Those barriers are currently missing on ARM.

    - test_and_xxx_bit were missing SMP barriers.

    So put these barriers in. Provide separate atomic_add/atomic_sub
    operations which do not require barriers.

    Reported-Reviewed-and-Acked-by: Mathieu Desnoyers
    Signed-off-by: Russell King

    Russell King
     

28 May, 2009

2 commits


27 May, 2009

8 commits

  • The implementation we just revived has issues, such as using a
    Kconfig-defined virtual address area in kernel space that nothing
    actually carves out (and thus will overlap whatever is there),
    or having some dependencies on being self contained in a single
    PTE page which adds unnecessary constraints on the kernel virtual
    address space.

    This fixes it by using more classic PTE accessors and automatically
    locating the area for consistent memory, carving an appropriate hole
    in the kernel virtual address space, leaving only the size of that
    area as a Kconfig option. It also brings some dma-mask related fixes
    from the ARM implementation which was almost identical initially but
    grew its own fixes.

    Signed-off-by: Benjamin Herrenschmidt

    Benjamin Herrenschmidt
     
  • Make FIXADDR_TOP a compile time constant and cleanup a
    couple of definitions relative to the layout of the kernel
    address space on ppc32. We also print out that layout at
    boot time for debugging purposes.

    This is a pre-requisite for properly fixing non-coherent
    DMA allocactions.

    Signed-off-by: Benjamin Herrenschmidt

    Benjamin Herrenschmidt
     
  • (pre-requisite to make the next patches more palatable)

    Signed-off-by: Benjamin Herrenschmidt

    Benjamin Herrenschmidt
     
  • Fix some more fallout of the string changes:

    CC arch/blackfin/lib/strncmp.o
    In file included from include/linux/bitmap.h:9,
    from include/linux/nodemask.h:90,
    from include/linux/mmzone.h:17,
    from include/linux/gfp.h:5,
    from include/linux/kmod.h:23,
    from include/linux/module.h:14,
    from arch/blackfin/lib/strncmp.c:14:
    include/linux/string.h: In function ‘strstarts’:
    include/linux/string.h:132: error: implicit declaration of function ‘strncmp’
    make[1]: *** [arch/blackfin/lib/strncmp.o] Error 1

    Signed-off-by: Mike Frysinger
    CC: Rusty Russell

    Mike Frysinger
     
  • We don't create a include/asm/mach/ symlink anymore, so we don't need the
    .gitignore for it.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     
  • Signed-off-by: Mike Frysinger

    Mike Frysinger
     
  • Signed-off-by: Mike Frysinger

    Mike Frysinger
     
  • This reverts commit 33f00dcedb0e22cdb156a23632814fc580fcfcf8.

    While it was a good idea to try to use the mm/vmalloc.c allocator instead
    of our own (in fact, ours is itself a dup on an old variant of the vmalloc
    one), unfortunately, the approach is terminally busted since
    dma_alloc_coherent() can be called at interrupt time or in atomic contexts
    and there's little chances we'll make the code in mm/vmalloc.c cope with\ that :-(

    Until we can get the generic code to forbid that idiocy and fix all
    drivers abusing it, we pretty much have no choice but revert to
    our custom virtual space allocator.

    There's also a problem with SMP safety since freeing such mapping
    would require an IPI which cannot be done at interrupt time.

    However, right now, I don't think we support any platform that is
    both SMP and has non-coherent DMA (don't laugh, I know such things
    do exist !) so we can sort that out later.

    Signed-off-by: Benjamin Herrenschmidt

    Benjamin Herrenschmidt