1. 29 Jan, 2013 1 commit
  2. 27 Jan, 2013 3 commits
  3. 24 Jan, 2013 17 commits
  4. 22 Jan, 2013 3 commits
  5. 17 Jan, 2013 4 commits
  6. 14 Jan, 2013 8 commits
  7. 10 Jan, 2013 4 commits
    • Cornelia Huck's avatar
      KVM: trace: Fix exit decoding. · f79ed82d
      Cornelia Huck authored
      trace_kvm_userspace_exit has been missing the KVM_EXIT_WATCHDOG exit.
      
      CC: Bharat Bhushan <r65777@freescale.com>
      Signed-off-by: default avatarCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: default avatarMarcelo Tosatti <mtosatti@redhat.com>
      f79ed82d
    • Xiao Guangrong's avatar
      KVM: MMU: fix infinite fault access retry · 7751babd
      Xiao Guangrong authored
      We have two issues in current code:
      - if target gfn is used as its page table, guest will refault then kvm will use
        small page size to map it. We need two #PF to fix its shadow page table
      
      - sometimes, say a exception is triggered during vm-exit caused by #PF
        (see handle_exception() in vmx.c), we remove all the shadow pages shadowed
        by the target gfn before go into page fault path, it will cause infinite
        loop:
        delete shadow pages shadowed by the gfn -> try to use large page size to map
        the gfn -> retry the access ->...
      
      To fix these, we can adjust page size early if the target gfn is used as page
      table
      Signed-off-by: default avatarXiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
      Signed-off-by: default avatarMarcelo Tosatti <mtosatti@redhat.com>
      7751babd
    • Xiao Guangrong's avatar
      KVM: MMU: fix Dirty bit missed if CR0.WP = 0 · c2288505
      Xiao Guangrong authored
      If the write-fault access is from supervisor and CR0.WP is not set on the
      vcpu, kvm will fix it by adjusting pte access - it sets the W bit on pte
      and clears U bit. This is the chance that kvm can change pte access from
      readonly to writable
      
      Unfortunately, the pte access is the access of 'direct' shadow page table,
      means direct sp.role.access = pte_access, then we will create a writable
      spte entry on the readonly shadow page table. It will cause Dirty bit is
      not tracked when two guest ptes point to the same large page. Note, it
      does not have other impact except Dirty bit since cr0.wp is encoded into
      sp.role
      
      It can be fixed by adjusting pte access before establishing shadow page
      table. Also, after that, no mmu specified code exists in the common function
      and drop two parameters in set_spte
      Signed-off-by: default avatarXiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
      Signed-off-by: default avatarMarcelo Tosatti <mtosatti@redhat.com>
      c2288505
    • Alexander Graf's avatar
      KVM: PPC: BookE: Add EPR ONE_REG sync · 324b3e63
      Alexander Graf authored
      We need to be able to read and write the contents of the EPR register
      from user space.
      
      This patch implements that logic through the ONE_REG API and declares
      its (never implemented) SREGS counterpart as deprecated.
      Signed-off-by: default avatarAlexander Graf <agraf@suse.de>
      324b3e63