From: ANIMESH KUMAR SINHA <1912777@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1912777] Re: KVM_EXIT_MMIO has increased in Qemu4.0.0 when compared to Qemu 2.11.0
Date: Fri, 22 Jan 2021 15:41:44 -0000 [thread overview]
Message-ID: <161133010549.10605.2993520825397084708.launchpad@gac.canonical.com> (raw)
In-Reply-To: 161131847021.10154.14606822070729811950.malonedeb@gac.canonical.com
** Information type changed from Private Security to Public Security
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1912777
Title:
KVM_EXIT_MMIO has increased in Qemu4.0.0 when compared to Qemu 2.11.0
Status in QEMU:
New
Status in Ubuntu:
New
Bug description:
I was able to generate trace dump in Qemu for kvm_run_exit event in both QEMU 2.11.0 and QEMU 4.0.0
From the trace i noticed that the number of KVM_KXIT_MMIO calls has increased alot and is causing delay in testcase execution.
I executed same testcase from Qemu 2.11 and Qemu4.
Inside Virtual machine when using qemu 2.11 testcase got completed in 11 seconds
but the same testcase when executed on Qemu 4.0.0 got executed in 26 seconds.
I did a bit of digging and extracted the kvm_run_exit to figure out whats going on.
Please find
Stats from Qemu2.11:
KVM_EXIT_UNKNOWN : 0
KVM_EXIT_EXCEPTION : 0
KVM_EXIT_IO : 182513
KVM_EXIT_HYPERCALL : 0
KVM_EXIT_DEBUG : 0
KVM_EXIT_HLT : 0
KVM_EXIT_MMIO : 216701
KVM_EXIT_IRQ_WINDOW_OPEN : 0
KVM_EXIT_SHUTDOWN : 0
KVM_EXIT_FAIL_ENTRY : 0
KVM_EXIT_INTR : 0
KVM_EXIT_SET_TPR : 0
KVM_EXIT_TPR_ACCESS : 0
KVM_EXIT_S390_SIEIC : 0
KVM_EXIT_S390_RESET : 0
KVM_EXIT_DCR : 0
KVM_EXIT_NMI : 0
KVM_EXIT_INTERNAL_ERROR : 0
KVM_EXIT_OSI : 0
KVM_EXIT_PAPR_HCALL : 0
KVM_EXIT_S390_UCONTROL : 0
KVM_EXIT_WATCHDOG : 0
KVM_EXIT_S390_TSCH : 0
KVM_EXIT_EPR : 0
KVM_EXIT_SYSTEM_EVENT : 0
KVM_EXIT_S390_STSI : 0
KVM_EXIT_IOAPIC_EOI : 0
KVM_EXIT_HYPERV : 0
KVM_RUN_EXIT : 399214 (Total in Qemu 2.11 for a
testcase)
Stats For Qemu 4.0.0:
VM_EXIT_UNKNOWN : 0
KVM_EXIT_EXCEPTION : 0
KVM_EXIT_IO : 163729
KVM_EXIT_HYPERCALL : 0
KVM_EXIT_DEBUG : 0
KVM_EXIT_HLT : 0
KVM_EXIT_MMIO : 1094231
KVM_EXIT_IRQ_WINDOW_OPEN : 46
KVM_EXIT_SHUTDOWN : 0
KVM_EXIT_FAIL_ENTRY : 0
KVM_EXIT_INTR : 0
KVM_EXIT_SET_TPR : 0
KVM_EXIT_TPR_ACCESS : 0
KVM_EXIT_S390_SIEIC : 0
KVM_EXIT_S390_RESET : 0
KVM_EXIT_DCR : 0
KVM_EXIT_NMI : 0
KVM_EXIT_INTERNAL_ERROR : 0
KVM_EXIT_OSI : 0
KVM_EXIT_PAPR_HCALL : 0
KVM_EXIT_S390_UCONTROL : 0
KVM_EXIT_WATCHDOG : 0
KVM_EXIT_S390_TSCH : 0
KVM_EXIT_EPR : 0
KVM_EXIT_SYSTEM_EVENT : 0
KVM_EXIT_S390_STSI : 0
KVM_EXIT_IOAPIC_EOI : 464
KVM_EXIT_HYPERV : 0
KVM_RUN_EXIT : 1258470 (Total in qemu 4.0.0 for same
testcase)
From above analysis i found that the number of KVM_EXIT_MMIO has
increased by 4.x.
Could someone from qemu community help me understand as to why the
MMIO exits have increased in qemu4 ?
The results i obtained are after running same testcase.
On Qemu2.11 testcase gets completed in : 11seconds
on Qemu4.11 testcase gets completed in : 26 seconds
VM Qcow2 used in Ubuntu 16.04
VM kernel OS is : 4.4 generic
Let me know incase more information is required .
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1912777/+subscriptions
next parent reply other threads:[~2021-01-22 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <161131847021.10154.14606822070729811950.malonedeb@gac.canonical.com>
2021-01-22 15:41 ` ANIMESH KUMAR SINHA [this message]
2021-01-22 15:58 ` [Bug 1912777] Re: KVM_EXIT_MMIO has increased in Qemu4.0.0 when compared to Qemu 2.11.0 Thomas Huth
2021-01-27 5:28 ` ANIMESH KUMAR SINHA
2021-02-02 10:42 ` ANIMESH KUMAR SINHA
2021-02-02 12:57 ` ANIMESH KUMAR SINHA
2021-02-03 12:34 ` ANIMESH KUMAR SINHA
2021-02-04 7:23 ` ANIMESH KUMAR SINHA
2021-02-11 16:51 ` ANIMESH KUMAR SINHA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161133010549.10605.2993520825397084708.launchpad@gac.canonical.com \
--to=1912777@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.