From: "Alexey Eremenko" <al4321@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][RFC] SVM support
Date: Sat, 25 Aug 2007 11:57:53 +0200 [thread overview]
Message-ID: <7fac565a0708250257g5fc5326eqe827d4e8b8c49a61@mail.gmail.com> (raw)
In-Reply-To: <46CF6FEB.1080504@bellard.org>
Alexander Graf:
Excuse me, but it is a bit unclear what you did.
Several questions arise:
a. Qemu now is able to emulate SVM on non-SVM old 32-bit processors ?
-or-
b. Qemu now is able to emulate SVM on SVM processors ?
c. Qemu now is able to emulate SVM on VT processors ?
d. How fast it works ? (theoretically, or benchmark results )
Anyway it's nice to hear about this feature.
--
-Alexey Eremenko "Technologov"
next prev parent reply other threads:[~2007-08-25 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 19:58 [Qemu-devel] [PATCH][RFC] SVM support Alexander Graf
2007-08-22 20:19 ` Blue Swirl
2007-08-22 20:26 ` Alexander Graf
2007-08-23 9:14 ` Avi Kivity
2007-08-23 9:05 ` Avi Kivity
2007-08-24 17:13 ` Alexander Graf
2007-08-24 23:55 ` Fabrice Bellard
2007-08-25 9:57 ` Alexey Eremenko [this message]
2007-08-25 12:30 ` Alexander Graf
2007-08-25 17:51 ` Mulyadi Santosa
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=7fac565a0708250257g5fc5326eqe827d4e8b8c49a61@mail.gmail.com \
--to=al4321@gmail.com \
--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).