From: "Jim C. Brown" <jbrown106@phreaker.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-fast kernel patch question
Date: Sun, 25 Jul 2004 16:03:11 -0400 [thread overview]
Message-ID: <20040725200311.GA23104@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.LNX.4.56.0407251213260.1397@halef.NotaMusica.com>
On Sun, Jul 25, 2004 at 12:24:16PM +0200, Johannes Martin wrote:
> Hi,
>
> Here's a quote from qemu-tech.html:
> ---
> 2.10 MMU emulation
>
> For system emulation, QEMU uses the mmap() system call to emulate the
> target CPU MMU. It works as long the emulated OS does not use an area
> reserved by the host OS (such as the area above 0xc0000000 on x86
> Linux).
> ---
>
> As far as I understand this, the qemu kernel patch makes the guest kernel
> use a different reserved area than the linux host. So it shouldn't matter
> which kernel I apply the patch to, right? If I patch the (linux) host
> kernel, I should be able to boot any unpatched (linux) guest kernel, if I
> don't patch the (linux) host kernel, I have to patch my (linux) guest
> kernels. Or do we need a patch-aware qemy-fast to run on a patched host?
>
> Assuming that OS XYZ does not use the area around 0xc0000000, it should
> work inside qemu-fast, right? And if it does use that area, it should work
> inside qemu-fast on a patched host?
>
> Maybe one of the wizards could clarify this...
>
> Thanks
> Johannes
>
You could patch the host not to use that area, but then it would have to use
another area ... thus you'd have to patch the guest anyways, regardless of the
host.
Fabrice has said that the eventual idea is to have qemu-fast detect which areas
are not accessable via mmap() and use the softmmu to emulate for only those
areas. The rest would be accessed via the faster mmap(). So, if you patch
qemu-fast in the right way, you might not have to patch the guest or the host. :)
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2004-07-25 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 15:32 [Qemu-devel] qemu-fast kernel patch question Lindsay Mathieson
2004-07-24 22:55 ` Lindsay Mathieson
2004-07-25 0:37 ` Mulyadi Santosa
2004-07-25 2:13 ` Lindsay Mathieson
2004-07-25 7:01 ` Mulyadi Santosa
2004-07-25 10:24 ` Johannes Martin
2004-07-25 20:03 ` Jim C. Brown [this message]
2004-07-26 13: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=20040725200311.GA23104@jbrown.mylinuxbox.org \
--to=jbrown106@phreaker.net \
--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).