From: Xin Tong <xerox.time.tech@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] In-kernel emulation
Date: Fri, 7 Oct 2011 08:32:46 -0400 [thread overview]
Message-ID: <CALKntY3uc=10Th6JkXJk3-CBGpsKHwe_dcyhSu5YDwhyLXxYdw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
I am wondering that whether there are any attempts (product-oriented or
research-based ) to push QEMU into the Linux kernel to speed up emulation.
If the emulation is running in the kernel, there are some resources it can
manipulate to speed up emulation in comparison to the when it is running as
a user process, i.e. MMU. Also, IO emulation may become faster, because 2
kernel enters and exits are incurred for a network packet if QEMU is running
as a user process. If QEMU is running in the kernel, only 1 kernel enter and
exit are needed. Any suggestions or discussions are welcome.
Thanks
Xin
[-- Attachment #2: Type: text/html, Size: 684 bytes --]
next reply other threads:[~2011-10-07 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 12:32 Xin Tong [this message]
2011-10-07 16:33 ` [Qemu-devel] In-kernel emulation 陳韋任
[not found] ` <CALKntY1nQ2AE5tD7TuSar2ygNivN5U5T4-PmsXZFx1JD1a1R9w@mail.gmail.com>
2011-10-07 19:10 ` 陳韋任
2011-10-07 19:16 ` Xin Tong
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='CALKntY3uc=10Th6JkXJk3-CBGpsKHwe_dcyhSu5YDwhyLXxYdw@mail.gmail.com' \
--to=xerox.time.tech@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).