From: Richard Purdie <rpurdie@rpsys.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu and mmap_min_addr
Date: Fri, 02 May 2008 15:51:19 +0100 [thread overview]
Message-ID: <1209739879.5184.16.camel@dax.rpnet.com> (raw)
In-Reply-To: <481874A7.7000704@hut.fi>
On Wed, 2008-04-30 at 16:31 +0300, Jussi Hakala wrote:
> Paul Brook wrote:
> > You have to use a nonzero GUEST_BASE to offset the guest VM. However this
> > hasn't been tested in a while, and has probably bitrotted.
>
> For preliminary testing, setting GUEST_BASE to 65536 seemed to work.
> I'll investigate further and report back to you :)
I was also looking at this problem and setting GUEST_BASE seemed to fix
my test cases although I've not tried it in a wider environment.
I was wondering if mismatching the host and guest memory layouts like
that incurred a performance penalty though?
Regards,
Richard
prev parent reply other threads:[~2008-05-02 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 11:43 [Qemu-devel] Qemu and mmap_min_addr Jussi Hakala
2008-04-30 12:31 ` Paul Brook
2008-04-30 13:31 ` Jussi Hakala
2008-05-02 9:59 ` Jussi Hakala
2008-05-02 14:51 ` Richard Purdie [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=1209739879.5184.16.camel@dax.rpnet.com \
--to=rpurdie@rpsys.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).