Re: Towards a working "wine". [long]

From: Peter Edwards (peadar.edwards_at_gmail.com)
Date: 06/18/05

  • Next message: Mike Tancsa: "Re: ichwd fixes / patches" 
    Date: Sat, 18 Jun 2005 13:06:36 +0100
To: Alexander Leidinger <Alexander@leidinger.net>

    On 6/18/05, Alexander Leidinger <Alexander@leidinger.net> wrote:
    > On Fri, 17 Jun 2005 17:59:38 -0700 (PDT)
    > Jon Dama <jd@ugcs.caltech.edu> wrote:
    >
    > > My intuition says that mmap should ignore requests to map into the
    > > existing brk region but not reject requests that are merely between the
    > > existing brk region and the DS limit.
    >
    > Have you seen Martin Cracauer's mail ("My hacks to make the memory map
    > fit") on emulation@ which deals with the memory map? Maybe it's of help
    > here...

    No I hadn't seen them, thanks for the reference.
    These won't help in this case: It's almost the opposite problem. I think.
    Martin's hack leaves a gap between the data segment and the area that
    mmap starts looking in for address space. However, because of the
    format of the wine binary, it's data segment is very high in memory,
    and the area required by wine's mmap actually falls inside it. i.e.,
    Martins fix pushes out the starting point for mmap searches, but wine
    needs hit dragged in.

    Jean-Marc DETREZ posted an interesting patch to emulation@ and wine's
    patches list around the same time that's more promising, though:
    "patch for unbreaking wine on freebsd"

    This uses mincore() + mmap(... MAP_FIXED ...) when mincore returns
    EFAULT. I'll have a read of it.

    It looks like both OpenBSD and NetBSD now incorporate a MAP_TRYFIXED,
    though. And, from a comment on the OpenBSD 3.4 changelog, adding it to
    the linuxulator may also help compatibility there.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Mike Tancsa: "Re: ichwd fixes / patches"

    Relevant Pages

    • Re: Can I mmap a file without a red zone?
      ... I'd like to mmap it in sequential chunks, moving the window forward ... to have given you an 8k buffer which was aligned in this way. ... map of 8192+500MB should be sufficient to create the working space, ...
      (comp.unix.solaris)
    • Re: Towards a working "wine". [long]
      ... My intuition says that mmap should ignore requests to map into the ... existing brk region and the DS limit. ... It doesn't matter in Linux because sbrk() has much less ...
      (freebsd-current)
    • Re: Towards a working "wine". [long]
      ... > existing brk region and the DS limit. ... it's adjusted to be just beyond the data segment. ... mmap() starts looking for space after the data segment. ... found enough room in the processes memory map. ...
      (freebsd-current)
    • Re: shared memory reguion
      ... I want to map a file to specific memory location and attach ... If you're making a MAP_SHARED mmap object, ... For anything other than MPAS, ... map the file private [if you don't need any changes ...
      (comp.sys.hp.hpux)
    • Cyrus mmap vs lseek/write usage - (WAS: BUG: mmapfile/writev spurious zero bytes (x86_64/not i38
      ... Writing is all done with seeks and writes, followed by a map ... The theory I think was that mmap write ... I'm not actually a maintainer for Cyrus, ... Cyrus provides an operating system ...
      (Linux-Kernel)