From: Amit Shah <amit.shah@redhat.com>
To: yuanzhu86 <yuanzhu86@163.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] why did qemu add the KVM ?
Date: Fri, 11 Sep 2009 11:27:21 +0530 [thread overview]
Message-ID: <20090911055721.GD31399@amit-x200.redhat.com> (raw)
In-Reply-To: <1838424.876271252597541773.JavaMail.coremail@app185.163.com>
On (Thu) Sep 10 2009 [23:45:41], yuanzhu86 wrote:
> there is a KVM.c in the target-i386 ,
> but why did QEMU have this program?
> shall anyone tell me the fuction of KVM.c to the QEMU ?
When a disk image is given to qemu, qemu converts instructions from the
target architecture to the native architecture. This enables it to run,
for example, ARM binaries on x86. However, when you want to execute x86
code on x86, the translations are not necessary. KVM is code that
short-circuits those translations so that x86 binaries are run directly
on the host x86 CPU.
KVM is a kernel module that handles processor-specific state so that
guests can run side by side normal processes. KVM.c in QEMU sources
interfaces with the KVM kernel modules.
Amit
prev parent reply other threads:[~2009-09-11 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 15:45 [Qemu-devel] why did qemu add the KVM ? yuanzhu86
2009-09-11 5:57 ` Amit Shah [this message]
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=20090911055721.GD31399@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yuanzhu86@163.com \
/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).