qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-fast kernel patch question
Date: Mon, 26 Jul 2004 20:51:30 +0700	[thread overview]
Message-ID: <200407262051.30041.a_mulyadi@softhome.net> (raw)
In-Reply-To: <20040725200311.GA23104@jbrown.mylinuxbox.org>

Hello Jim :-)

First thank you to help correcting my logics :-)

> 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.
Agree....why I don't think in such a logic before...hrrrrrr :-)

> 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. :)

So, that would be running mmap() scanning on early boot of Qemu, am  I right? 
from there, Qemu can take decision which area is free and which is already 
taken by host....Hm....looks like Qemu needs additional kernel module 
inserted to host's kernel to help Qemu on "memory layout" negotiation....:-)

regards

Mulyadi

      reply	other threads:[~2004-07-26 13:56 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
2004-07-26 13:51             ` Mulyadi Santosa [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=200407262051.30041.a_mulyadi@softhome.net \
    --to=a_mulyadi@softhome.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).