1. 01 12月, 2021 2 次提交
  2. 08 11月, 2021 1 次提交
  3. 11 10月, 2021 2 次提交
  4. 01 10月, 2021 1 次提交
  5. 20 8月, 2021 4 次提交
  6. 19 8月, 2021 1 次提交
  7. 18 8月, 2021 1 次提交
  8. 02 8月, 2021 1 次提交
    • M
      KVM: arm64: Remove PMSWINC_EL0 shadow register · 7a3ba309
      Marc Zyngier 提交于
      We keep an entry for the PMSWINC_EL0 register in the vcpu structure,
      while *never* writing anything there outside of reset.
      
      Given that the register is defined as write-only, that we always
      trap when this register is accessed, there is little point in saving
      anything anyway.
      
      Get rid of the entry, and save a mighty 8 bytes per vcpu structure.
      
      We still need to keep it exposed to userspace in order to preserve
      backward compatibility with previously saved VMs. Since userspace
      cannot expect any effect of writing to PMSWINC_EL0, treat the
      register as RAZ/WI for the purpose of userspace access.
      Signed-off-by: NMarc Zyngier <maz@kernel.org>
      Link: https://lore.kernel.org/r/20210719123902.1493805-5-maz@kernel.org
      7a3ba309
  9. 24 6月, 2021 1 次提交
  10. 22 6月, 2021 3 次提交
  11. 18 6月, 2021 2 次提交
  12. 17 4月, 2021 4 次提交
  13. 07 4月, 2021 4 次提交
  14. 25 3月, 2021 1 次提交
  15. 19 3月, 2021 4 次提交
  16. 18 3月, 2021 3 次提交
  17. 09 2月, 2021 1 次提交
    • V
      KVM: Raise the maximum number of user memslots · 4fc096a9
      Vitaly Kuznetsov 提交于
      Current KVM_USER_MEM_SLOTS limits are arch specific (512 on Power, 509 on x86,
      32 on s390, 16 on MIPS) but they don't really need to be. Memory slots are
      allocated dynamically in KVM when added so the only real limitation is
      'id_to_index' array which is 'short'. We don't have any other
      KVM_MEM_SLOTS_NUM/KVM_USER_MEM_SLOTS-sized statically defined structures.
      
      Low KVM_USER_MEM_SLOTS can be a limiting factor for some configurations.
      In particular, when QEMU tries to start a Windows guest with Hyper-V SynIC
      enabled and e.g. 256 vCPUs the limit is hit as SynIC requires two pages per
      vCPU and the guest is free to pick any GFN for each of them, this fragments
      memslots as QEMU wants to have a separate memslot for each of these pages
      (which are supposed to act as 'overlay' pages).
      Signed-off-by: NVitaly Kuznetsov <vkuznets@redhat.com>
      Message-Id: <20210127175731.2020089-3-vkuznets@redhat.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      4fc096a9
  18. 26 1月, 2021 1 次提交
  19. 22 12月, 2020 3 次提交