From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: avi@redhat.com, mtosatti@redhat.com
Cc: jan.kiszka@web.de, kvm@vger.kernel.org
Subject: [PATCH 0/1] KVM: MMU: Fix 64-bit paging breakage on x86_32
Date: Thu, 28 Apr 2011 07:02:38 +0900 [thread overview]
Message-ID: <20110428070238.ba6e67aa.takuya.yoshikawa@gmail.com> (raw)
Sorry for being late to send.
Making a PAE guest took longer than I expected.
The test was done before "unlikely" annotation was added.
But I did compile-test after adding "unlikely" on x86_32.
Thanks,
Takuya
Test conditions:
On x86_32: PAE/non-PAE Linux guest
On x86_64: Usual 64 guest
PAE guest on x86_32 tracing results:
qemu-system-x86-2042 [000] 5752.176099: funcgraph_entry: | paging64_walk_addr_generic() {
qemu-system-x86-2042 [000] 5752.176100: funcgraph_entry: 0.183 us | get_cr3();
qemu-system-x86-2042 [000] 5752.176101: funcgraph_entry: 0.182 us | get_cr3();
qemu-system-x86-2042 [000] 5752.176102: funcgraph_entry: | load_pdptrs() {
qemu-system-x86-2042 [000] 5752.176103: funcgraph_entry: | kvm_read_guest_page_mmu() {
qemu-system-x86-2042 [000] 5752.176103: funcgraph_entry: 0.171 us | translate_gpa();
qemu-system-x86-2042 [000] 5752.176105: funcgraph_entry: | kvm_read_guest_page() {
qemu-system-x86-2042 [000] 5752.176106: funcgraph_entry: 0.240 us | gfn_to_hva();
qemu-system-x86-2042 [000] 5752.176108: funcgraph_entry: | copy_from_user() {
qemu-system-x86-2042 [000] 5752.176108: funcgraph_entry: | _copy_from_user() {
qemu-system-x86-2042 [000] 5752.176109: funcgraph_entry: 0.178 us | _cond_resched();
qemu-system-x86-2042 [000] 5752.176110: funcgraph_exit: 1.423 us | }
qemu-system-x86-2042 [000] 5752.176111: funcgraph_exit: 2.613 us | }
qemu-system-x86-2042 [000] 5752.176111: funcgraph_exit: 5.148 us | }
qemu-system-x86-2042 [000] 5752.176112: funcgraph_exit: 8.573 us | }
qemu-system-x86-2042 [000] 5752.176112: funcgraph_exit: 9.832 us | }
qemu-system-x86-2042 [000] 5752.176113: funcgraph_entry: 0.181 us | translate_gpa();
qemu-system-x86-2042 [000] 5752.176114: funcgraph_entry: 0.242 us | gfn_to_hva();
qemu-system-x86-2042 [000] 5752.176115: funcgraph_entry: 0.181 us | kvm_is_error_hva();
qemu-system-x86-2042 [000] 5752.176117: funcgraph_entry: 0.182 us | _cond_resched();
qemu-system-x86-2042 [000] 5752.176118: funcgraph_entry: 0.182 us | _cond_resched();
qemu-system-x86-2042 [000] 5752.176119: funcgraph_entry: 0.176 us | translate_gpa();
qemu-system-x86-2042 [000] 5752.176121: funcgraph_entry: 0.242 us | gfn_to_hva();
qemu-system-x86-2042 [000] 5752.176122: funcgraph_entry: 0.181 us | kvm_is_error_hva();
qemu-system-x86-2042 [000] 5752.176123: funcgraph_entry: 0.183 us | _cond_resched();
qemu-system-x86-2042 [000] 5752.176124: funcgraph_entry: 0.182 us | _cond_resched();
qemu-system-x86-2042 [000] 5752.176125: funcgraph_entry: 0.181 us | translate_gpa();
qemu-system-x86-2042 [000] 5752.176127: funcgraph_exit: + 27.102 us | }
next reply other threads:[~2011-04-27 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 22:02 Takuya Yoshikawa [this message]
2011-04-27 22:08 ` [PATCH 1/1] KVM: MMU: Fix 64-bit paging breakage on x86_32 Takuya Yoshikawa
2011-04-28 10:06 ` Avi Kivity
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=20110428070238.ba6e67aa.takuya.yoshikawa@gmail.com \
--to=takuya.yoshikawa@gmail.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox