qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: qemu@zensonic.dk
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help getting an qemu-alpha environment to work
Date: Tue, 27 Apr 2010 08:00:03 +0200	[thread overview]
Message-ID: <20100427060003.GA30029@zensonic.dk> (raw)
In-Reply-To: <4BD395EE.2090409@twiddle.net>

> There's a problem with the current implementation of mmap
> in linux-user such that it can return addresses that are
> outside the "valid" address space of the guest.

How do I, either

1. avoid the problem? (Give the guest a larger valid address space)
2. Fix the problem ? (Could you give 4 lines describing the problem
and give hints to files to look at and/or send me your patch. I do not
mind any performance penalty/"ugliness" of code)

Thomas

  reply	other threads:[~2010-04-27  5:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 15:51 [Qemu-devel] Help getting an qemu-alpha environment to work qemu
2010-04-25  1:07 ` Richard Henderson
2010-04-27  6:00   ` qemu [this message]
2010-04-27 18:13     ` Richard Henderson

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=20100427060003.GA30029@zensonic.dk \
    --to=qemu@zensonic.dk \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).