qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user 32/64 bit mremap() problem
Date: Thu, 4 Sep 2008 07:59:47 +0300	[thread overview]
Message-ID: <cc557aab0809032159vd9d1386nac625b256c3cb727@mail.gmail.com> (raw)
In-Reply-To: <20080903165652.P92245@stanley.csl.cornell.edu>

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

On Thu, Sep 4, 2008 at 12:01 AM, Vince Weaver <vince@csl.cornell.edu> wrote:

> Hello
>
> This has been discuessed a year ago
>
> http://www.nabble.com/linux-user-mmap()-for-32-bit-guest-on-64-bit-host-td12934745.html<http://www.nabble.com/linux-user-mmap%28%29-for-32-bit-guest-on-64-bit-host-td12934745.html>
>  http://osdir.com/ml/linux.ports.x86-64.general/2007-10/msg00007.html
> but hasn't really been resolved.
>
> The linux-user mremap() syscall implementation will return a 64-bit value
> when running on a 64-bit machine, even when the architecture being simulated
> is only 32-bits.
>
> Has any progress been made on this issue?  I might try implementing the
> workaround the kernel people suggested.
>
> This actually prevents one of the perlbmk spec2k benchmarks from running
> with sparc32plus emulation on an x86_64 machine.
>

I have posted patch to the maillist witch add flag MAP_32BIT to mmap and
mremap calls. It helps on x86_64 host, but other 64-bit host doesn't support
this flag currently.

[-- Attachment #2: Type: text/html, Size: 1505 bytes --]

      reply	other threads:[~2008-09-04  4:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 21:01 [Qemu-devel] linux-user 32/64 bit mremap() problem Vince Weaver
2008-09-04  4:59 ` Kirill A. Shutemov [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=cc557aab0809032159vd9d1386nac625b256c3cb727@mail.gmail.com \
    --to=kirill@shutemov.name \
    --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).