1. 30 8月, 2013 1 次提交
    • G
      Merge branch 'kvm-ppc-next' of git://github.com/agraf/linux-2.6 into queue · a9f6cf96
      Gleb Natapov 提交于
      * 'kvm-ppc-next' of git://github.com/agraf/linux-2.6:
        KVM: PPC: Book3S PR: Rework kvmppc_mmu_book3s_64_xlate()
        KVM: PPC: Book3S PR: Make instruction fetch fallback work for system calls
        KVM: PPC: Book3S PR: Don't corrupt guest state when kernel uses VMX
        KVM: PPC: Book3S: Fix compile error in XICS emulation
        KVM: PPC: Book3S PR: return appropriate error when allocation fails
        arch: powerpc: kvm: add signed type cast for comparation
        powerpc/kvm: Copy the pvr value after memset
        KVM: PPC: Book3S PR: Load up SPRG3 register with guest value on guest entry
        kvm/ppc/booke: Don't call kvm_guest_enter twice
        kvm/ppc: Call trace_hardirqs_on before entry
        KVM: PPC: Book3S HV: Allow negative offsets to real-mode hcall handlers
        KVM: PPC: Book3S HV: Correct tlbie usage
        powerpc/kvm: Use 256K chunk to track both RMA and hash page table allocation.
        powerpc/kvm: Contiguous memory allocator based RMA allocation
        powerpc/kvm: Contiguous memory allocator based hash page table allocation
        KVM: PPC: Book3S: Ignore DABR register
        mm/cma: Move dma contiguous changes into a seperate config
      a9f6cf96
  2. 29 8月, 2013 3 次提交
  3. 28 8月, 2013 9 次提交
  4. 27 8月, 2013 1 次提交
    • A
      kvm: optimize away THP checks in kvm_is_mmio_pfn() · 11feeb49
      Andrea Arcangeli 提交于
      The checks on PG_reserved in the page structure on head and tail pages
      aren't necessary because split_huge_page wouldn't transfer the
      PG_reserved bit from head to tail anyway.
      
      This was a forward-thinking check done in the case PageReserved was
      set by a driver-owned page mapped in userland with something like
      remap_pfn_range in a VM_PFNMAP region, but using hugepmds (not
      possible right now). It was meant to be very safe, but it's overkill
      as it's unlikely split_huge_page could ever run without the driver
      noticing and tearing down the hugepage itself.
      
      And if a driver in the future will really want to map a reserved
      hugepage in userland using an huge pmd it should simply take care of
      marking all subpages reserved too to keep KVM safe. This of course
      would require such a hypothetical driver to tear down the huge pmd
      itself and splitting the hugepage itself, instead of relaying on
      split_huge_page, but that sounds very reasonable, especially
      considering split_huge_page wouldn't currently transfer the reserved
      bit anyway.
      Signed-off-by: NAndrea Arcangeli <aarcange@redhat.com>
      Signed-off-by: NGleb Natapov <gleb@redhat.com>
      11feeb49
  5. 26 8月, 2013 10 次提交
  6. 23 8月, 2013 1 次提交
  7. 13 8月, 2013 1 次提交
  8. 07 8月, 2013 14 次提交