All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentine Sinitsyn <valentine.sinitsyn@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	kvm@vger.kernel.org
Subject: Re: Nested paging in nested SVM setup
Date: Tue, 02 Sep 2014 01:21:36 +0600	[thread overview]
Message-ID: <5404C740.4010602@gmail.com> (raw)
In-Reply-To: <5404AFB2.3090000@redhat.com>

Hi Paolo,

On 01.09.2014 23:41, Paolo Bonzini wrote:
> Il 21/08/2014 14:28, Valentine Sinitsyn ha scritto:
> BTW npt_rsvd does *not* fail on the machine I've been testing on today.
I can confirm l1mmio test doesn't fail in kvm-unit-test's master 
anymore. npt_rsvd still does. I also needed to disable ioio test, or it 
was hanging for a long time (this doesn't happen if I use Jan's patched 
KVM that have IOPM bugs fixed). However, l1mmio test passes regardless I 
use stock kvm 3.16.1 or a patched version.

> Can you retry running the tests with the latest kvm-unit-tests (branch
> "master"), gather a trace of kvm and kvmmmu events, and send the
> compressed trace.dat my way?
You mean the trace when the problem reveal itself (not from running 
tests), I assume? It's around 2G uncompressed (probably I'm enabling 
tracing to early or doing anything else wrong). Will look into it 
tomorrow, hopefully, I can reduce the size (e.g. by switching to 
uniprocessor mode). Below is a trace snippet similar to the one I've 
sent earlier.

----------------------------------------------------------------------
qemu-system-x86-2728  [002]  1726.426225: kvm_exit:             reason 
npf rip 0xffffffff8104e876 info 10000000f fee000b0
  qemu-system-x86-2728  [002]  1726.426226: kvm_nested_vmexit:    rip: 
0xffffffff8104e876 reason: npf ext_inf1: 0x000000010000000f ext_inf2: 
0x00000000fee000b0 ext_int: 0x00000000 ext_int_err: 0x00000000
  qemu-system-x86-2728  [002]  1726.426227: kvm_page_fault: 
address fee000b0 error_code f
  qemu-system-x86-2725  [000]  1726.426227: kvm_exit:             reason 
npf rip 0xffffffff8104e876 info 10000000f fee000b0
  qemu-system-x86-2725  [000]  1726.426228: kvm_nested_vmexit:    rip: 
0xffffffff8104e876 reason: npf ext_inf1: 0x000000010000000f ext_inf2: 
0x00000000fee000b0 ext_int: 0x00000000 ext_int_err: 0x00000000
  qemu-system-x86-2725  [000]  1726.426229: kvm_page_fault: 
address fee000b0 error_code f
  qemu-system-x86-2728  [002]  1726.426229: kvm_emulate_insn: 
0:ffffffff8104e876:89 b7 00 b0 5f ff (prot64)
  qemu-system-x86-2725  [000]  1726.426230: kvm_emulate_insn: 
0:ffffffff8104e876:89 b7 00 b0 5f ff (prot64)
  qemu-system-x86-2728  [002]  1726.426231: kvm_mmu_pagetable_walk: addr 
ffffffffff5fb0b0 pferr 2 W
  qemu-system-x86-2725  [000]  1726.426231: kvm_mmu_pagetable_walk: addr 
ffffffffff5fb0b0 pferr 2 W
  qemu-system-x86-2728  [002]  1726.426231: kvm_mmu_pagetable_walk: addr 
1811000 pferr 6 W|U
  qemu-system-x86-2725  [000]  1726.426232: kvm_mmu_pagetable_walk: addr 
36c49000 pferr 6 W|U
  qemu-system-x86-2728  [002]  1726.426232: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2725  [000]  1726.426232: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2728  [002]  1726.426232: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2725  [000]  1726.426233: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2728  [002]  1726.426233: kvm_mmu_paging_element: pte 
18000e7 level 2
  qemu-system-x86-2725  [000]  1726.426233: kvm_mmu_paging_element: pte 
36c000e7 level 2
  qemu-system-x86-2728  [002]  1726.426233: kvm_mmu_paging_element: pte 
1814067 level 4
  qemu-system-x86-2725  [000]  1726.426233: kvm_mmu_paging_element: pte 
1814067 level 4
  qemu-system-x86-2728  [002]  1726.426233: kvm_mmu_pagetable_walk: addr 
1814000 pferr 6 W|U
  qemu-system-x86-2725  [000]  1726.426234: kvm_mmu_pagetable_walk: addr 
1814000 pferr 6 W|U
  qemu-system-x86-2728  [002]  1726.426234: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2725  [000]  1726.426234: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2728  [002]  1726.426234: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2725  [000]  1726.426235: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2728  [002]  1726.426235: kvm_mmu_paging_element: pte 
18000e7 level 2
  qemu-system-x86-2725  [000]  1726.426235: kvm_mmu_paging_element: pte 
18000e7 level 2
  qemu-system-x86-2728  [002]  1726.426235: kvm_mmu_paging_element: pte 
1816067 level 3
  qemu-system-x86-2725  [000]  1726.426235: kvm_mmu_paging_element: pte 
1816067 level 3
  qemu-system-x86-2728  [002]  1726.426235: kvm_mmu_pagetable_walk: addr 
1816000 pferr 6 W|U
  qemu-system-x86-2725  [000]  1726.426236: kvm_mmu_pagetable_walk: addr 
1816000 pferr 6 W|U
  qemu-system-x86-2728  [002]  1726.426236: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2725  [000]  1726.426236: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2728  [002]  1726.426236: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2725  [000]  1726.426236: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2728  [002]  1726.426236: kvm_mmu_paging_element: pte 
18000e7 level 2
  qemu-system-x86-2725  [000]  1726.426237: kvm_mmu_paging_element: pte 
18000e7 level 2
  qemu-system-x86-2728  [002]  1726.426237: kvm_mmu_paging_element: pte 
1a06067 level 2
  qemu-system-x86-2725  [000]  1726.426237: kvm_mmu_paging_element: pte 
1a06067 level 2
  qemu-system-x86-2725  [000]  1726.426238: kvm_mmu_pagetable_walk: addr 
1a06000 pferr 6 W|U
  qemu-system-x86-2728  [002]  1726.426238: kvm_mmu_pagetable_walk: addr 
1a06000 pferr 6 W|U
  qemu-system-x86-2725  [000]  1726.426238: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2728  [002]  1726.426238: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2725  [000]  1726.426238: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2725  [000]  1726.426239: kvm_mmu_paging_element: pte 
1a000e7 level 2
  qemu-system-x86-2728  [002]  1726.426239: kvm_mmu_paging_element: pte 
3c03d027 level 3
  qemu-system-x86-2725  [000]  1726.426239: kvm_mmu_paging_element: pte 
80000000fee0017b level 1
  qemu-system-x86-2728  [002]  1726.426239: kvm_mmu_paging_element: pte 
1a000e7 level 2
  qemu-system-x86-2725  [000]  1726.426239: kvm_mmu_pagetable_walk: addr 
fee00000 pferr 6 W|U
  qemu-system-x86-2728  [002]  1726.426239: kvm_mmu_paging_element: pte 
80000000fee0017b level 1
  qemu-system-x86-2725  [000]  1726.426240: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2728  [002]  1726.426240: kvm_mmu_pagetable_walk: addr 
fee00000 pferr 6 W|U
  qemu-system-x86-2725  [000]  1726.426240: kvm_mmu_paging_element: pte 
3c03b027 level 3
  qemu-system-x86-2728  [002]  1726.426240: kvm_mmu_paging_element: pte 
3c03a027 level 4
  qemu-system-x86-2725  [000]  1726.426240: kvm_mmu_paging_element: pte 
3c03c027 level 2
  qemu-system-x86-2728  [002]  1726.426241: kvm_mmu_paging_element: pte 
3c03b027 level 3
  qemu-system-x86-2725  [000]  1726.426241: kvm_mmu_paging_element: pte 
fee0003d level 1
  qemu-system-x86-2728  [002]  1726.426241: kvm_mmu_paging_element: pte 
3c03c027 level 2
  qemu-system-x86-2725  [000]  1726.426241: kvm_mmu_walker_error: pferr 
7 P|W|U
  qemu-system-x86-2728  [002]  1726.426241: kvm_mmu_paging_element: pte 
fee0003d level 1
  qemu-system-x86-2725  [000]  1726.426241: kvm_mmu_walker_error: pferr 2 W
  qemu-system-x86-2728  [002]  1726.426242: kvm_mmu_walker_error: pferr 
7 P|W|U
  qemu-system-x86-2728  [002]  1726.426242: kvm_mmu_walker_error: pferr 2 W
  qemu-system-x86-2725  [000]  1726.426243: kvm_inj_exception:    e (0x2)
  qemu-system-x86-2728  [002]  1726.426243: kvm_inj_exception:    e (0x2)
  qemu-system-x86-2725  [000]  1726.426244: kvm_entry:            vcpu 0

Thanks,
Valentine


  reply	other threads:[~2014-09-01 19:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 11:36 Nested paging in nested SVM setup Valentine Sinitsyn
2014-06-18 12:47 ` Jan Kiszka
2014-06-18 16:59   ` Valentine Sinitsyn
2014-06-19  9:32     ` Paolo Bonzini
2014-06-19  5:03   ` Valentine Sinitsyn
2014-08-20  6:46   ` Valentine Sinitsyn
2014-08-20  6:55     ` Paolo Bonzini
2014-08-20  7:37       ` Valentine Sinitsyn
2014-08-20  8:11         ` Paolo Bonzini
2014-08-20  9:49           ` Valentine Sinitsyn
2014-08-21  6:28           ` Valentine Sinitsyn
2014-08-21  8:48             ` Valentine Sinitsyn
2014-08-21 11:04               ` Paolo Bonzini
2014-08-21 11:06                 ` Jan Kiszka
2014-08-21 11:12                   ` Valentine Sinitsyn
2014-08-21 11:16                 ` Valentine Sinitsyn
2014-08-21 11:24               ` Paolo Bonzini
2014-08-21 12:28                 ` Valentine Sinitsyn
2014-08-21 12:38                   ` Valentine Sinitsyn
2014-08-21 13:40                   ` Valentine Sinitsyn
2014-09-01 17:41                   ` Paolo Bonzini
2014-09-01 19:21                     ` Valentine Sinitsyn [this message]
2014-09-02  8:25                       ` Paolo Bonzini
2014-09-02  9:16                         ` Valentine Sinitsyn
2014-09-02 11:21                           ` Paolo Bonzini
2014-09-02 11:26                             ` Valentine Sinitsyn
2014-08-21 17:35                 ` Valentine Sinitsyn
2014-08-21 20:31                   ` Paolo Bonzini
2014-08-22  4:33                     ` Valentine Sinitsyn
2014-08-22  8:53                       ` Paolo Bonzini
2014-09-01 16:11                       ` Paolo Bonzini
2014-09-01 17:04     ` Paolo Bonzini
2014-09-02  6:09       ` Valentine Sinitsyn
2014-09-02  6:21         ` Valentine Sinitsyn
2014-09-02  9:45         ` Paolo Bonzini
2014-09-02  9:53           ` Valentine Sinitsyn
2014-09-02 11:48             ` Paolo Bonzini
2014-09-02 10:31           ` Valentine Sinitsyn

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=5404C740.4010602@gmail.com \
    --to=valentine.sinitsyn@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@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 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.