Eric Lee / smarc-fsl-linux-kernel

16 Apr, 2010

2 commits

03 Feb, 2010

1 commit

02 Feb, 2010

11 commits

01 Feb, 2010

19 commits

31 Jan, 2010

3 commits

  • f3f1e14ce   Merge branch 'fix/asoc' into for-linus Browse Code »
    Takashi Iwai
     
  • 74ce25c0e   Merge branch 'fix/hda' into for-linus Browse Code »
    Takashi Iwai
     
  • 61684ceaa   x86/agp: Fix agp_amd64_init regression ... Browse Code »

    This fixes the regression introduced by commit
    42590a75019a50012f25a962246498dead428433 ("x86/agp: Fix
    agp_amd64_init and agp_amd64_cleanup").

    The above commit changes agp_amd64_init() not to do anything if
    gart_iommu_aperture is not zero.

    If GART iommu calls agp_amd64_init(), we need to skip
    agp_amd64_init() when it's called later via module_init.

    The problem is that gart_iommu_init() calls agp_amd64_init()
    with not zero gart_iommu_aperture so agp_amd64_init() is never
    initialized.

    When gart_iommu_init() calls agp_amd64_init(), agp should be
    always initialized.

    Reported-by: Marin Mitov
    Reported-by: Johannes Hirte
    Signed-off-by: FUJITA Tomonori
    Tested-by: Marin Mitov
    Tested-by: Kevin Winchester
    Cc: davej@redhat.com
    Cc: Linus Torvalds
    LKML-Reference:
    Signed-off-by: Ingo Molnar

    FUJITA Tomonori
     

30 Jan, 2010

4 commits

  • 5352ae638   perf, hw_breakpoint, kgdb: Do not take mutex for kernel debugger ... Browse Code »

    This patch fixes the regression in functionality where the
    kernel debugger and the perf API do not nicely share hw
    breakpoint reservations.

    The kernel debugger cannot use any mutex_lock() calls because it
    can start the kernel running from an invalid context.

    A mutex free version of the reservation API needed to get
    created for the kernel debugger to safely update hw breakpoint
    reservations.

    The possibility for a breakpoint reservation to be concurrently
    processed at the time that kgdb interrupts the system is
    improbable. Should this corner case occur the end user is
    warned, and the kernel debugger will prohibit updating the
    hardware breakpoint reservations.

    Any time the kernel debugger reserves a hardware breakpoint it
    will be a system wide reservation.

    Signed-off-by: Jason Wessel
    Acked-by: Frederic Weisbecker
    Cc: kgdb-bugreport@lists.sourceforge.net
    Cc: K.Prasad
    Cc: Peter Zijlstra
    Cc: Alan Stern
    Cc: torvalds@linux-foundation.org
    LKML-Reference:
    Signed-off-by: Ingo Molnar

    Jason Wessel
     
  • cc0967490   x86, hw_breakpoints, kgdb: Fix kgdb to use hw_breakpoint API ... Browse Code »

    In the 2.6.33 kernel, the hw_breakpoint API is now used for the
    performance event counters. The hw_breakpoint_handler() now
    consumes the hw breakpoints that were previously set by kgdb
    arch specific code. In order for kgdb to work in conjunction
    with this core API change, kgdb must use some of the low level
    functions of the hw_breakpoint API to install, uninstall, and
    deal with hw breakpoint reservations.

    The kgdb core required a change to call kgdb_disable_hw_debug
    anytime a slave cpu enters kgdb_wait() in order to keep all the
    hw breakpoints in sync as well as to prevent hitting a hw
    breakpoint while kgdb is active.

    During the architecture specific initialization of kgdb, it will
    pre-allocate 4 disabled (struct perf event **) structures. Kgdb
    will use these to manage the capabilities for the 4 hw
    breakpoint registers, per cpu. Right now the hw_breakpoint API
    does not have a way to ask how many breakpoints are available,
    on each CPU so it is possible that the install of a breakpoint
    might fail when kgdb restores the system to the run state. The
    intent of this patch is to first get the basic functionality of
    hw breakpoints working and leave it to the person debugging the
    kernel to understand what hw breakpoints are in use and what
    restrictions have been imposed as a result. Breakpoint
    constraints will be dealt with in a future patch.

    While atomic, the x86 specific kgdb code will call
    arch_uninstall_hw_breakpoint() and arch_install_hw_breakpoint()
    to manage the cpu specific hw breakpoints.

    The net result of these changes allow kgdb to use the same pool
    of hw_breakpoints that are used by the perf event API, but
    neither knows about future reservations for the available hw
    breakpoint slots.

    Signed-off-by: Jason Wessel
    Acked-by: Frederic Weisbecker
    Cc: kgdb-bugreport@lists.sourceforge.net
    Cc: K.Prasad
    Cc: Peter Zijlstra
    Cc: Alan Stern
    Cc: torvalds@linux-foundation.org
    LKML-Reference:
    Signed-off-by: Ingo Molnar

    Jason Wessel
     
  • 7c099ce15   x86: Add quirk for Intel DG45FC board to avoid low memory corruption ... Browse Code »

    Commit 6aa542a694dc9ea4344a8a590d2628c33d1b9431 added a quirk for the
    Intel DG45ID board due to low memory corruption. The Intel DG45FC
    shares the same BIOS (and the same bug) as noted in:

    http://bugzilla.kernel.org/show_bug.cgi?id=13736

    Signed-off-by: David Härdeman
    LKML-Reference:
    Cc:
    Cc: Alexey Fisher
    Cc: ykzhao
    Cc: Tony Bones
    Cc: Ingo Molnar
    Signed-off-by: H. Peter Anvin

    David Härdeman
     
  • abe94c756   Linux 2.6.33-rc6 Browse Code »
    Linus Torvalds