From: Christoph Hellwig <hch@infradead.org>
To: Avi Kivity <avi@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, kvm@vger.kernel.org
Subject: Re: 32-bit qemu on current x86-64 kernel segfauls very early
Date: Tue, 2 Nov 2010 12:02:56 -0400 [thread overview]
Message-ID: <20101102160256.GA3435@infradead.org> (raw)
In-Reply-To: <4CD03574.6090708@redhat.com>
On Tue, Nov 02, 2010 at 11:59:48AM -0400, Avi Kivity wrote:
> > "KVM: Fix fs/gs reload oops with invalid ldt"
> >
>
> Interesting, I guess we corrupt %fs on x86_64.
>
> Intel or AMD?
Intel:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz
stepping : 6
cpu MHz : 2133.000
cache size : 6144 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dts tpr_shadow vnmi flexpriority
bogomips : 5588.00
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
next prev parent reply other threads:[~2010-11-02 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 13:06 32-bit qemu on current x86-64 kernel segfauls very early Christoph Hellwig
2010-11-02 15:11 ` Christoph Hellwig
2010-11-02 15:59 ` Avi Kivity
2010-11-02 16:02 ` Christoph Hellwig [this message]
2010-11-02 19:10 ` Avi Kivity
2010-11-03 12:37 ` 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=20101102160256.GA3435@infradead.org \
--to=hch@infradead.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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.