All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: linux 3.13 guest crash with -cpu host
Date: Mon, 3 Feb 2014 16:06:01 +0200	[thread overview]
Message-ID: <20140203140601.GA24944@redhat.com> (raw)
In-Reply-To: <20140203125828.GH2221@otherpad.lan.raisama.net>

On Mon, Feb 03, 2014 at 10:58:28AM -0200, Eduardo Habkost wrote:
> On Sun, Feb 02, 2014 at 10:59:30PM +0200, Michael S. Tsirkin wrote:
> > I observe this with guest 3.13 and host 3.13
> > when running with -cpu host on my laptop:
> > 
> > [    0.043000] Call Trace:
> > [    0.043000]  [<ffffffff81d0e873>] init_hw_perf_events+0x33/0x5cd
> > [    0.043000]  [<ffffffff81d0e840>] ? check_bugs+0x40/0x40
> > [    0.043000]  [<ffffffff8100030a>] do_one_initcall+0x13a/0x190
> > [    0.043000]  [<ffffffff81d15133>] ?
> > native_smp_prepare_cpus+0x285/0x3ee
> > [    0.043000]  [<ffffffff81d068da>] kernel_init_freeable+0x136/0x298
> > [    0.043000]  [<ffffffff816834e0>] ? rest_init+0x80/0x80
> > [    0.043000]  [<ffffffff816834ee>] kernel_init+0xe/0x130
> > [    0.043000]  [<ffffffff8169422c>] ret_from_fork+0x7c/0xb0
> > [    0.043000]  [<ffffffff816834e0>] ? rest_init+0x80/0x80
> > [    0.043000] Code: 0f 46 c2 41 83 e8 01 89 05 63 4c fd ff 7e 2e 44 89
> > d2 b8 03 00 00 00 b9 45 03 00 00 83 e2 1f 83 fa 02 0f 4f c2 89 05 6d 4b
> > fd ff <0f> 32 48 c1 e2 20 89 c0 48 09 c2 48 89 15 0b 4c fd ff e8 c6 d3 
> 
>    0:   0f 46 c2                cmovbe %edx,%eax
>    3:   41 83 e8 01             sub    $0x1,%r8d
>    7:   89 05 63 4c fd ff       mov    %eax,-0x2b39d(%rip)        # 0xfffffffffffd4c70
>    d:   7e 2e                   jle    0x3d
>    f:   44 89 d2                mov    %r10d,%edx
>   12:   b8 03 00 00 00          mov    $0x3,%eax
>   17:   b9 45 03 00 00          mov    $0x345,%ecx
>   1c:   83 e2 1f                and    $0x1f,%edx
>   1f:   83 fa 02                cmp    $0x2,%edx
>   22:   0f 4f c2                cmovg  %edx,%eax
>   25:   89 05 6d 4b fd ff       mov    %eax,-0x2b493(%rip)        # 0xfffffffffffd4b98
>   2b:*  0f 32                   rdmsr           <-- trapping instruction
>   2d:   48 c1 e2 20             shl    $0x20,%rdx
>   31:   89 c0                   mov    %eax,%eax
>   33:   48 09 c2                or     %rax,%rdx
>   36:   48 89 15 0b 4c fd ff    mov    %rdx,-0x2b3f5(%rip)        # 0xfffffffffffd4c48
>   3d:   e8                      .byte 0xe8
>   3e:   c6                      (bad)  
>   3f:   d3                      .byte 0xd3
> 
> Linux seems to be trying to read IA32_PERF_CAPABILITIES without checking the
> PDCM flag (CPUID[1].ECX[15]).
> 
> I can't see why this wasn't crashing before, though. That code seems to be old.
> 
> 	 * v2 and above have a perf capabilities MSR
> 	 */
> 	if (version > 1) {
> 		u64 capabilities;
> 
> 		rdmsrl(MSR_IA32_PERF_CAPABILITIES, capabilities);
> 		x86_pmu.intel_cap.capabilities = capabilities;
> 	}
> 
> Where does the "v2 and above have a perf capabilities MSR" claim in the code
> come from?


But why doesn't it crash on baremetal?
Probably baremetal simply returns 0 or something.
Let me try ..

> 
> 
> > [    0.043000] RIP  [<ffffffff81d0f8c3>] intel_pmu_init+0x208/0x95a
> > [    0.043000]  RSP <ffff88003f25fe18>
> > [    0.043012] ---[ end trace 9f1576f03a80bfa0 ]---
> > [    0.044018] Kernel panic - not syncing: Attempted to kill init!
> > exitcode=0x0000000b
> > 
> > -cpu kvm64 works fine.
> > 
> > Reproduces with upstream qemu a75143eda2ddf581b51e96c000974bcdfe2cbd10,
> > as well as with qemu-kvm from Fedora 19.
> > 
> > Tried recent git from Linus - it still has this problem.
> > 
> > -- 
> > MST
> 
> -- 
> Eduardo

  parent reply	other threads:[~2014-02-03 14:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02 20:59 linux 3.13 guest crash with -cpu host Michael S. Tsirkin
2014-02-03 12:58 ` Eduardo Habkost
2014-02-03 13:29   ` Peter Zijlstra
2014-02-21 21:14     ` [tip:perf/urgent] perf/x86: Correctly use FEATURE_PDCM tip-bot for Peter Zijlstra
2014-02-03 14:06   ` Michael S. Tsirkin [this message]
2014-02-03 14:07     ` linux 3.13 guest crash with -cpu host Paolo Bonzini
2014-02-03 14:42       ` Michael S. Tsirkin
2014-02-03 14:12     ` Peter Zijlstra
2014-02-03 14:19       ` Paolo Bonzini
2014-02-03 14:26         ` Peter Zijlstra
2014-02-03 14:28           ` Peter Zijlstra
2014-02-03 15:01             ` Paolo Bonzini
2014-02-03 14:45           ` Michael S. Tsirkin

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=20140203140601.GA24944@redhat.com \
    --to=mst@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ehabkost@redhat.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.