1. 19 3月, 2014 2 次提交
  2. 01 3月, 2014 1 次提交
  3. 26 2月, 2014 5 次提交
  4. 19 2月, 2014 1 次提交
    • I
      ARM: dts: keystone: drop msmcsram clock node · 5a2abe19
      Ivan Khoronzhuk 提交于
      At late init all unused clocks are disabled. So clocks that were not
      get before will be gated. In Keysone 2 SoC we have at least one
      necessary clock that is not used by any driver - "msmcsram". This
      clock is necessary, because it supplies the Multicore Shared Memory
      Controller (MSMC). MSMC is the coherency interconnect and all the
      coherent masters are connected to it including devices which are not
      under Linux OS control. MSMC clock should not be touched even in low
      power states.
      
      So drop the clock node, otherwise 'clk_ignore_unused' parameter will
      disable the clock leading to system stall.
      Signed-off-by: NIvan Khoronzhuk <ivan.khoronzhuk@ti.com>
      Signed-off-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      5a2abe19
  5. 17 2月, 2014 5 次提交
  6. 03 2月, 2014 5 次提交
  7. 02 2月, 2014 1 次提交
  8. 01 2月, 2014 17 次提交
  9. 31 1月, 2014 3 次提交
    • D
      xen/pvh: Fix misplaced kfree from xlated_setup_gnttab_pages · f93576e1
      Dave Jones 提交于
      Passing a freed 'pages' to free_xenballooned_pages will end badly
      on kernels with slub debug enabled.
      
      This looks out of place between the rc assign and the check, but
      we do want to kfree pages regardless of which path we take.
      Signed-off-by: NDave Jones <davej@fedoraproject.org>
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      f93576e1
    • Z
      xen/grant-table: Avoid m2p_override during mapping · 08ece5bb
      Zoltan Kiss 提交于
      The grant mapping API does m2p_override unnecessarily: only gntdev needs it,
      for blkback and future netback patches it just cause a lock contention, as
      those pages never go to userspace. Therefore this series does the following:
      - the original functions were renamed to __gnttab_[un]map_refs, with a new
        parameter m2p_override
      - based on m2p_override either they follow the original behaviour, or just set
        the private flag and call set_phys_to_machine
      - gnttab_[un]map_refs are now a wrapper to call __gnttab_[un]map_refs with
        m2p_override false
      - a new function gnttab_[un]map_refs_userspace provides the old behaviour
      
      It also removes a stray space from page.h and change ret to 0 if
      XENFEAT_auto_translated_physmap, as that is the only possible return value
      there.
      
      v2:
      - move the storing of the old mfn in page->index to gnttab_map_refs
      - move the function header update to a separate patch
      
      v3:
      - a new approach to retain old behaviour where it needed
      - squash the patches into one
      
      v4:
      - move out the common bits from m2p* functions, and pass pfn/mfn as parameter
      - clear page->private before doing anything with the page, so m2p_find_override
        won't race with this
      
      v5:
      - change return value handling in __gnttab_[un]map_refs
      - remove a stray space in page.h
      - add detail why ret = 0 now at some places
      
      v6:
      - don't pass pfn to m2p* functions, just get it locally
      Signed-off-by: NZoltan Kiss <zoltan.kiss@citrix.com>
      Suggested-by: NDavid Vrabel <david.vrabel@citrix.com>
      Acked-by: NDavid Vrabel <david.vrabel@citrix.com>
      Acked-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      08ece5bb
    • S
      arm64: mm: Introduce PTE_WRITE · c2c93e5b
      Steve Capper 提交于
      We have the following means for encoding writable or dirty ptes:
      
                                      PTE_DIRTY       PTE_RDONLY
      !pte_dirty && !pte_write        0               1
      !pte_dirty && pte_write         0               1
      pte_dirty && !pte_write         1               1
      pte_dirty && pte_write          1               0
      
      So we can't distinguish between writable clean ptes and read only
      ptes. This can cause problems with ptes being incorrectly flagged as
      read only when they are writable but not dirty.
      
      This patch introduces a new software bit PTE_WRITE which allows us to
      correctly identify writable ptes. PTE_RDONLY is now only clear for
      valid ptes where a page is both writable and dirty.
      Signed-off-by: NSteve Capper <steve.capper@arm.com>
      Reviewed-by: NCatalin Marinas <catalin.marinas@arm.com>
      Signed-off-by: NCatalin Marinas <catalin.marinas@arm.com>
      c2c93e5b