1. 29 6月, 2018 2 次提交
  2. 23 6月, 2018 1 次提交
  3. 09 6月, 2018 1 次提交
  4. 01 6月, 2018 3 次提交
  5. 23 5月, 2018 1 次提交
  6. 22 5月, 2018 1 次提交
  7. 11 5月, 2018 1 次提交
  8. 09 4月, 2018 2 次提交
  9. 13 3月, 2018 4 次提交
  10. 18 1月, 2018 1 次提交
  11. 16 1月, 2018 2 次提交
  12. 12 1月, 2018 1 次提交
    • J
      i386/cpu/kvm: look at PMU's CPUID before setting MSRs · 0b368a10
      Jan Dakinevich 提交于
      Certain PMU-related MSRs are not supported for CPUs with PMU
      architecture below version 2. KVM rejects any access to them (see
      intel_is_valid_msr_idx routine in KVM), and QEMU fails on the following
      assertion:
      
        kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
      
      QEMU also could fail if KVM exposes less fixed counters then 3. It could
      happen if host system run inside another hypervisor, which is tweaking
      PMU-related CPUID. To prevent possible fail, number of fixed counters now is
      obtained in the same way as number of GP counters.
      Reviewed-by: NRoman Kagan <rkagan@virtuozzo.com>
      Signed-off-by: NJan Dakinevich <jan.dakinevich@virtuozzo.com>
      Message-Id: <1514383466-7257-1-git-send-email-jan.dakinevich@virtuozzo.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      0b368a10
  13. 22 12月, 2017 1 次提交
  14. 21 12月, 2017 3 次提交
  15. 18 12月, 2017 1 次提交
  16. 19 9月, 2017 6 次提交
  17. 01 8月, 2017 1 次提交
  18. 13 7月, 2017 1 次提交
    • A
      Convert error_report() to warn_report() · 3dc6f869
      Alistair Francis 提交于
      Convert all uses of error_report("warning:"... to use warn_report()
      instead. This helps standardise on a single method of printing warnings
      to the user.
      
      All of the warnings were changed using these two commands:
          find ./* -type f -exec sed -i \
            's|error_report(".*warning[,:] |warn_report("|Ig' {} +
      
      Indentation fixed up manually afterwards.
      
      The test-qdev-global-props test case was manually updated to ensure that
      this patch passes make check (as the test cases are case sensitive).
      Signed-off-by: NAlistair Francis <alistair.francis@xilinx.com>
      Suggested-by: NThomas Huth <thuth@redhat.com>
      Cc: Jeff Cody <jcody@redhat.com>
      Cc: Kevin Wolf <kwolf@redhat.com>
      Cc: Max Reitz <mreitz@redhat.com>
      Cc: Ronnie Sahlberg <ronniesahlberg@gmail.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Peter Lieven <pl@kamp.de>
      Cc: Josh Durgin <jdurgin@redhat.com>
      Cc: "Richard W.M. Jones" <rjones@redhat.com>
      Cc: Markus Armbruster <armbru@redhat.com>
      Cc: Peter Crosthwaite <crosthwaite.peter@gmail.com>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
      Cc: Greg Kurz <groug@kaod.org>
      Cc: Rob Herring <robh@kernel.org>
      Cc: Peter Maydell <peter.maydell@linaro.org>
      Cc: Peter Chubb <peter.chubb@nicta.com.au>
      Cc: Eduardo Habkost <ehabkost@redhat.com>
      Cc: Marcel Apfelbaum <marcel@redhat.com>
      Cc: "Michael S. Tsirkin" <mst@redhat.com>
      Cc: Igor Mammedov <imammedo@redhat.com>
      Cc: David Gibson <david@gibson.dropbear.id.au>
      Cc: Alexander Graf <agraf@suse.de>
      Cc: Gerd Hoffmann <kraxel@redhat.com>
      Cc: Jason Wang <jasowang@redhat.com>
      Cc: Marcelo Tosatti <mtosatti@redhat.com>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Cornelia Huck <cohuck@redhat.com>
      Cc: Stefan Hajnoczi <stefanha@redhat.com>
      Acked-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Acked-by: NGreg Kurz <groug@kaod.org>
      Acked-by: NCornelia Huck <cohuck@redhat.com>
      Reviewed-by: NStefan Hajnoczi <stefanha@redhat.com>
      Reviewed by: Peter Chubb <peter.chubb@data61.csiro.au>
      Acked-by: NMax Reitz <mreitz@redhat.com>
      Acked-by: NMarcel Apfelbaum <marcel@redhat.com>
      Message-Id: <e1cfa2cd47087c248dd24caca9c33d9af0c499b0.1499866456.git.alistair.francis@xilinx.com>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      3dc6f869
  19. 04 7月, 2017 1 次提交
  20. 08 6月, 2017 2 次提交
    • G
      kvm: don't register smram_listener when smm is off · d870cfde
      Gonglei 提交于
      If the user set disable smm by '-machine smm=off', we
      should not register smram_listener so that we can
      avoid waster memory in kvm since the added sencond
      address space.
      
      Meanwhile we should assign value of the global kvm_state
      before invoking the kvm_arch_init(), because
      pc_machine_is_smm_enabled() may use it by kvm_has_mm().
      Signed-off-by: NGonglei <arei.gonglei@huawei.com>
      Message-Id: <1496316915-121196-1-git-send-email-arei.gonglei@huawei.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      d870cfde
    • R
      i386/kvm: do not zero out segment flags if segment is unusable or not present · d45fc087
      Roman Pen 提交于
      This is a fix for the problem [1], where VMCB.CPL was set to 0 and interrupt
      was taken on userspace stack.  The root cause lies in the specific AMD CPU
      behaviour which manifests itself as unusable segment attributes on SYSRET[2].
      
      Here in this patch flags are not touched even segment is unusable or is not
      present, therefore CPL (which is stored in DPL field) should not be lost and
      will be successfully restored on kvm/svm kernel side.
      
      Also current patch should not break desired behavior described in this commit:
      
      4cae9c97 ("target-i386: kvm: clear unusable segments' flags in migration")
      
      since present bit will be dropped if segment is unusable or is not present.
      
      This is the second part of the whole fix of the corresponding problem [1],
      first part is related to kvm/svm kernel side and does exactly the same:
      segment attributes are not zeroed out.
      
      [1] Message id: CAJrWOzD6Xq==b-zYCDdFLgSRMPM-NkNuTSDFEtX=7MreT45i7Q@mail.gmail.com
      [2] Message id: 5d120f358612d73fc909f5bfa47e7bd082db0af0.1429841474.git.luto@kernel.org
      Signed-off-by: NRoman Pen <roman.penyaev@profitbricks.com>
      Signed-off-by: NMikhail Sennikovskii <mikhail.sennikovskii@profitbricks.com>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Radim Krčmář <rkrcmar@redhat.com>
      Cc: Michael Chapman <mike@very.puzzling.org>
      Cc: qemu-devel@nongnu.org
      Message-Id: <20170601085604.12980-1-roman.penyaev@profitbricks.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      d45fc087
  21. 07 6月, 2017 1 次提交
    • P
      kvm: irqchip: skip update msi when disabled · fd563564
      Peter Xu 提交于
      It's possible that one device kept its irqfd/virq there even when
      MSI/MSIX was disabled globally for that device. One example is
      virtio-net-pci (see commit f1d0f15a and virtio_pci_vq_vector_mask()).
      It is used as a fast path to avoid allocate/release irqfd/virq
      frequently when guest enables/disables MSIX.
      
      However, this fast path brought a problem to msi_route_list, that the
      device MSIRouteEntry is still dangling there even if MSIX disabled -
      then we cannot know which message to fetch, even if we can, the messages
      are meaningless. In this case, we can just simply ignore this entry.
      
      It's safe, since when MSIX is enabled again, we'll rebuild them no
      matter what.
      
      Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1448813Signed-off-by: NPeter Xu <peterx@redhat.com>
      Message-Id: <1494309644-18743-4-git-send-email-peterx@redhat.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      fd563564
  22. 23 5月, 2017 1 次提交
    • E
      shutdown: Add source information to SHUTDOWN and RESET · cf83f140
      Eric Blake 提交于
      Time to wire up all the call sites that request a shutdown or
      reset to use the enum added in the previous patch.
      
      It would have been less churn to keep the common case with no
      arguments as meaning guest-triggered, and only modified the
      host-triggered code paths, via a wrapper function, but then we'd
      still have to audit that I didn't miss any host-triggered spots;
      changing the signature forces us to double-check that I correctly
      categorized all callers.
      
      Since command line options can change whether a guest reset request
      causes an actual reset vs. a shutdown, it's easy to also add the
      information to reset requests.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Acked-by: David Gibson <david@gibson.dropbear.id.au> [ppc parts]
      Reviewed-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> [SPARC part]
      Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com> [s390x parts]
      Message-Id: <20170515214114.15442-5-eblake@redhat.com>
      Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      cf83f140
  23. 17 5月, 2017 1 次提交
  24. 14 3月, 2017 1 次提交