From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>, Julien Cristau <jcristau@debian.org>
Subject: Re: [Qemu-devel] default qemu64 &Co CPUs makes no sense?
Date: Thu, 10 May 2012 09:30:27 +0200 [thread overview]
Message-ID: <4FAB6E93.5050009@redhat.com> (raw)
In-Reply-To: <4FAAA13E.10308@msgid.tls.msk.ru>
Il 09/05/2012 18:54, Michael Tokarev ha scritto:
> And in case kvm is enabled, and we run on some other CPU
> (not intel and not amd), we'll have some other CPU model,
> which might exist or might not, which may make some sense
> or may not, etc - we simple don't know.
Leaving aside the discussions on TCG, yes, this makes no sense for kvm.
You should use kvm32 and kvm64 instead.
Paolo
next prev parent reply other threads:[~2012-05-10 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 16:54 [Qemu-devel] default qemu64 &Co CPUs makes no sense? Michael Tokarev
2012-05-10 7:30 ` Paolo Bonzini [this message]
2012-05-10 7:46 ` Michael Tokarev
2012-05-10 7:49 ` Paolo Bonzini
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=4FAB6E93.5050009@redhat.com \
--to=pbonzini@redhat.com \
--cc=jcristau@debian.org \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).