From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM crash on unusual PM->RM transition
Date: Tue, 14 Apr 2009 19:16:33 +0300 [thread overview]
Message-ID: <49E4B6E1.6020308@redhat.com> (raw)
In-Reply-To: <49E4B581.4000808@zytor.com>
H. Peter Anvin wrote:
> Avi Kivity wrote:
>
>> - qemu doesn't do smp.
>>
>>
>
> It certainly claims to.
>
>
Sorry, not specific enough: it doesn't do real SMP. Atomic instructions
are translated as multiple, non-atomic instructions, so you can't run
tcg compiled code in parallel. If your host is different than your
target, you have memory ordering issues as well.
What qemu does is to multiplex multiple guest cpus on one host thread.
It's nice but it isn't how kvm works.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-04-14 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 23:42 KVM crash on unusual PM->RM transition H. Peter Anvin
2009-04-14 5:42 ` H. Peter Anvin
2009-04-14 8:14 ` Avi Kivity
2009-04-14 15:48 ` H. Peter Anvin
2009-04-14 16:07 ` Avi Kivity
2009-04-14 16:10 ` H. Peter Anvin
2009-04-14 16:16 ` Avi Kivity [this message]
2009-04-14 16:17 ` H. Peter Anvin
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=49E4B6E1.6020308@redhat.com \
--to=avi@redhat.com \
--cc=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox