From: Gleb Natapov <gleb@redhat.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Xiao Guangrong <xiaoguangrong.eric@gmail.com>,
kvm@vger.kernel.org,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: commit f8f559422b (KVM: MMU: fast invalidate all mmio sptes) causes hang
Date: Wed, 17 Jul 2013 21:55:39 +0300 [thread overview]
Message-ID: <20130717185539.GK13732@redhat.com> (raw)
In-Reply-To: <20130717184226.GA358@x4>
On Wed, Jul 17, 2013 at 08:42:26PM +0200, Markus Trippelsdorf wrote:
> On 2013.07.18 at 01:25 +0800, Xiao Guangrong wrote:
> > Hi Markus,
> >
> > Thanks for your report! I am downloading the ubuntu iso and will try to reproducible it.
> >
> > Could you please enable these tracepoints:
> > kvmmmu/check_mmio_spte
> > kvmmmu/handle_mmio_page_fault
> > kvmmmu/kvm_mmu_invalidate_zap_all_pages
> > kvmmmu/mark_mmio_spte
> > kvm/kvm_mmio
> > kvm/vcpu_match_mmio
> >
> > and post the output?
> >
> First line repeated ad nauseam.
> ...
> 10346367 qemu-system-x86-1403 [001] 1451.422225: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346368 qemu-system-x86-1403 [001] 1451.422226: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346369 qemu-system-x86-1403 [001] 1451.422227: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346370 qemu-system-x86-1403 [001] 1451.422228: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346371 qemu-system-x86-1403 [001] 1451.422229: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346372 qemu-system-x86-1404 [002] 1451.422229: kvm_mmio: mmio write len 4 gpa 0xfee000b0 val 0x0
> 10346373 qemu-system-x86-1403 [001] 1451.422230: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346374 qemu-system-x86-1403 [001] 1451.422231: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346375 qemu-system-x86-1403 [001] 1451.422232: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346376 qemu-system-x86-1403 [001] 1451.422233: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346377 qemu-system-x86-1403 [001] 1451.422234: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346378 qemu-system-x86-1403 [001] 1451.422235: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346379 qemu-system-x86-1404 [002] 1451.422236: kvm_mmio: mmio write len 4 gpa 0xfee00380 val 0x3c7b0
> 10346380 qemu-system-x86-1403 [001] 1451.422237: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346381 qemu-system-x86-1403 [001] 1451.422238: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346382 qemu-system-x86-1403 [001] 1451.422239: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346383 qemu-system-x86-1403 [001] 1451.422240: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346384 qemu-system-x86-1403 [001] 1451.422241: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346385 qemu-system-x86-1403 [001] 1451.422242: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346386 qemu-system-x86-1403 [001] 1451.422243: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346387 qemu-system-x86-1403 [001] 1451.422244: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> 10346403 qemu-system-x86-1403 [001] 1451.422260: check_mmio_spte: spte ffff0000fee00e3f kvm_gen 7ffc8 spte-gen 7ffc7 valid 0
> ...
> Last line repeated ad nauseam.
>
While this happens can you run "echo t > /proc/sysrq-trigger" and attach
dmesg here.
--
Gleb.
next prev parent reply other threads:[~2013-07-17 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 16:32 commit f8f559422b (KVM: MMU: fast invalidate all mmio sptes) causes hang Markus Trippelsdorf
2013-07-17 16:42 ` Gleb Natapov
2013-07-17 16:57 ` Markus Trippelsdorf
2013-07-17 17:25 ` Xiao Guangrong
2013-07-17 17:34 ` Markus Trippelsdorf
2013-07-17 18:42 ` Markus Trippelsdorf
2013-07-17 18:55 ` Gleb Natapov [this message]
2013-07-17 19:00 ` Markus Trippelsdorf
2013-07-17 19:27 ` Xiao Guangrong
2013-07-17 19:38 ` Markus Trippelsdorf
2013-07-17 19:28 ` Gleb Natapov
2013-07-17 19:22 ` Xiao Guangrong
2013-07-17 19:07 ` Xiao Guangrong
2013-07-17 19:31 ` Gleb Natapov
2013-07-17 19:52 ` Xiao Guangrong
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=20130717185539.GK13732@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=xiaoguangrong.eric@gmail.com \
--cc=xiaoguangrong@linux.vnet.ibm.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 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.