1. 30 5月, 2018 6 次提交
  2. 25 5月, 2018 1 次提交
  3. 22 5月, 2018 4 次提交
    • V
      PM / OPP: Fix shared OPP table support in dev_pm_opp_register_set_opp_helper() · 5019acc6
      Viresh Kumar 提交于
      It should be fine to call dev_pm_opp_register_set_opp_helper() for all
      possible CPUs, even if some of them share the OPP table as the caller
      may not be aware of sharing policy.
      
      Lets increment the reference count of the OPP table and return its
      pointer. The caller need to call dev_pm_opp_register_put_opp_helper()
      the same number of times later on to drop all the references.
      
      To avoid adding another counter to count how many times
      dev_pm_opp_register_set_opp_helper() is called for the same OPP table,
      dev_pm_opp_register_put_opp_helper() frees the resources on the very
      first call made to it, assuming that the caller would be calling it
      sequentially for all the CPUs. We can revisit that if that assumption is
      broken in the future.
      Signed-off-by: NViresh Kumar <viresh.kumar@linaro.org>
      5019acc6
    • V
      PM / OPP: Fix shared OPP table support in dev_pm_opp_set_regulators() · 779b783c
      Viresh Kumar 提交于
      It should be fine to call dev_pm_opp_set_regulators() for all possible
      CPUs, even if some of them share the OPP table as the caller may not be
      aware of sharing policy.
      
      Lets increment the reference count of the OPP table and return its
      pointer. The caller need to call dev_pm_opp_put_regulators() the same
      number of times later on to drop all the references.
      
      To avoid adding another counter to count how many times
      dev_pm_opp_set_regulators() is called for the same OPP table,
      dev_pm_opp_put_regulators() frees the resources on the very first call
      made to it, assuming that the caller would be calling it sequentially
      for all the CPUs. We can revisit that if that assumption is broken in
      the future.
      Signed-off-by: NViresh Kumar <viresh.kumar@linaro.org>
      779b783c
    • V
      PM / OPP: Fix shared OPP table support in dev_pm_opp_set_prop_name() · 878ec1a9
      Viresh Kumar 提交于
      It should be fine to call dev_pm_opp_set_prop_name() for all possible
      CPUs, even if some of them share the OPP table as the caller may not be
      aware of sharing policy.
      
      Lets increment the reference count of the OPP table and return its
      pointer. The caller need to call dev_pm_opp_put_prop_name() the same
      number of times later on to drop all the references.
      
      To avoid adding another counter to count how many times
      dev_pm_opp_set_prop_name() is called for the same OPP table,
      dev_pm_opp_put_prop_name() frees the resources on the very first call
      made to it, assuming that the caller would be calling it sequentially
      for all the CPUs. We can revisit that if that assumption is broken in
      the future.
      Signed-off-by: NViresh Kumar <viresh.kumar@linaro.org>
      878ec1a9
    • V
      PM / OPP: Fix shared OPP table support in dev_pm_opp_set_supported_hw() · 25419de1
      Viresh Kumar 提交于
      It should be fine to call dev_pm_opp_set_supported_hw() for all possible
      CPUs, even if some of them share the OPP table as the caller may not be
      aware of sharing policy.
      
      Lets increment the reference count of the OPP table and return its
      pointer. The caller need to call dev_pm_opp_put_supported_hw() the same
      number of times later on to drop all the references.
      
      To avoid adding another counter to count how many times
      dev_pm_opp_set_supported_hw() is called for the same OPP table,
      dev_pm_opp_put_supported_hw() frees the resources on the very first call
      made to it, assuming that the caller would be calling it sequentially
      for all the CPUs. We can revisit that if that assumption is broken in
      the future.
      Signed-off-by: NViresh Kumar <viresh.kumar@linaro.org>
      25419de1
  4. 17 5月, 2018 2 次提交
  5. 16 5月, 2018 1 次提交
  6. 15 5月, 2018 13 次提交
  7. 14 5月, 2018 5 次提交
    • L
      Linux 4.17-rc5 · 67b8d5c7
      Linus Torvalds 提交于
      67b8d5c7
    • L
      Merge branch 'x86-pti-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · 66e1c94d
      Linus Torvalds 提交于
      Pull x86/pti updates from Thomas Gleixner:
       "A mixed bag of fixes and updates for the ghosts which are hunting us.
      
        The scheduler fixes have been pulled into that branch to avoid
        conflicts.
      
         - A set of fixes to address a khread_parkme() race which caused lost
           wakeups and loss of state.
      
         - A deadlock fix for stop_machine() solved by moving the wakeups
           outside of the stopper_lock held region.
      
         - A set of Spectre V1 array access restrictions. The possible
           problematic spots were discuvered by Dan Carpenters new checks in
           smatch.
      
         - Removal of an unused file which was forgotten when the rest of that
           functionality was removed"
      
      * 'x86-pti-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        x86/vdso: Remove unused file
        perf/x86/cstate: Fix possible Spectre-v1 indexing for pkg_msr
        perf/x86/msr: Fix possible Spectre-v1 indexing in the MSR driver
        perf/x86: Fix possible Spectre-v1 indexing for x86_pmu::event_map()
        perf/x86: Fix possible Spectre-v1 indexing for hw_perf_event cache_*
        perf/core: Fix possible Spectre-v1 indexing for ->aux_pages[]
        sched/autogroup: Fix possible Spectre-v1 indexing for sched_prio_to_weight[]
        sched/core: Fix possible Spectre-v1 indexing for sched_prio_to_weight[]
        sched/core: Introduce set_special_state()
        kthread, sched/wait: Fix kthread_parkme() completion issue
        kthread, sched/wait: Fix kthread_parkme() wait-loop
        sched/fair: Fix the update of blocked load when newly idle
        stop_machine, sched: Fix migrate_swap() vs. active_balance() deadlock
      66e1c94d
    • L
      Merge branch 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · 86a4ac43
      Linus Torvalds 提交于
      Pull scheduler fix from Thomas Gleixner:
       "Revert the new NUMA aware placement approach which turned out to
        create more problems than it solved"
      
      * 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        Revert "sched/numa: Delay retrying placement for automatic NUMA balance after wake_affine()"
      86a4ac43
    • L
      Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · baeda713
      Linus Torvalds 提交于
      Pull perf tooling fixes from Thomas Gleixner:
       "Another small set of perf tooling fixes and updates:
      
         - Revert "perf pmu: Fix pmu events parsing rule", as it broke Intel
           PT event description parsing (Arnaldo Carvalho de Melo)
      
         - Sync x86's cpufeatures.h and kvm UAPI headers with the kernel
           sources, suppressing the ABI drift warnings (Arnaldo Carvalho de
           Melo)
      
         - Remove duplicated entry for westmereep-dp in Intel's mapfile.csv
           (William Cohen)
      
         - Fix typo in 'perf bench numa' options description (Yisheng Xie)"
      
      * 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        Revert "perf pmu: Fix pmu events parsing rule"
        tools headers kvm: Sync ARM UAPI headers with the kernel sources
        tools headers kvm: Sync uapi/linux/kvm.h with the kernel sources
        tools headers: Sync x86 cpufeatures.h with the kernel sources
        perf vendor events intel: Remove duplicated entry for westmereep-dp in mapfile.csv
        perf bench numa: Fix typo in options
      baeda713
    • L
      Merge tag 'dma-mapping-4.17-5' of git://git.infradead.org/users/hch/dma-mapping · 0503fd65
      Linus Torvalds 提交于
      Pull dma-mapping fix from Christoph Hellwig:
       "Just one little fix from Jean to avoid a harmless but very annoying
        warning, especially for the drm code"
      
      * tag 'dma-mapping-4.17-5' of git://git.infradead.org/users/hch/dma-mapping:
        swiotlb: silent unwanted warning "buffer is full"
      0503fd65
  8. 13 5月, 2018 3 次提交
  9. 12 5月, 2018 5 次提交