From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris Webb <chris@arachsys.com>,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: Divide error in kvm_unlock_kick()
Date: Thu, 29 May 2014 19:51:18 +0200 [thread overview]
Message-ID: <53877396.8010503@redhat.com> (raw)
In-Reply-To: <D2F026E2-666F-4194-B95F-B5001843FA44@arachsys.com>
Il 29/05/2014 19:45, Chris Webb ha scritto:
> Chris Webb <chris@arachsys.com> wrote:
>
>> My CPU flags inside the crashing guest look like this:
>>
>> fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush
>> mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb lm rep_good nopl
>> extd_apicid pni pclmulqdq ssse3 fma cx16 sse4_1 sse4_2 x2apic popcnt aes xsave
>> avx f16c hypervisor lahf_lm cmp_legacy svm cr8_legacy abm sse4a misalignsse
>> 3dnowprefetch osvw xop fma4 tbm arat npt nrip_save tsc_adjust bmi1
>>
>> whereas in a (working) -cpu qemu64 guest, they look like this:
>>
>> fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx
>> fxsr sse sse2 ht syscall nx lm nopl pni cx16 x2apic popcnt hypervisor lahf_lm
>> cmp_legacy svm abm sse4a
>
> I thought I'd try to bisect on processor flags to see which was/were
> implicated.
Can you dump the full /proc/cpuinfo?
Paolo
next prev parent reply other threads:[~2014-05-29 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 16:42 Divide error in kvm_unlock_kick() Chris Webb
2014-05-29 17:45 ` Chris Webb
2014-05-29 17:51 ` Paolo Bonzini [this message]
2014-05-29 18:03 ` Chris Webb
2014-06-01 12:36 ` Chris Webb
2014-06-17 10:27 ` Chris Webb
2014-06-17 10:27 ` [Qemu-devel] " Chris Webb
2014-05-29 18:03 ` Chris Webb
2014-05-29 17:51 ` Paolo Bonzini
2014-05-29 17:45 ` Chris Webb
-- strict thread matches above, loose matches on Subject: below --
2014-05-28 16:42 Chris Webb
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=53877396.8010503@redhat.com \
--to=pbonzini@redhat.com \
--cc=chris@arachsys.com \
--cc=kvm@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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.