mmap address allocation
From: John Birrell (jb_at_cimlogic.com.au)
Date: 06/18/04
- Previous message: PaTaNa: "K7VM2-R3.0 and duron 1.3Gh procesor"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 18 Jun 2004 10:41:59 +1000 To: arch@freebsd.org
The current Wine code won't run on either FreeBSD4 or -current now that they've
added code that tries to snaffle (mmap) all memory in user space from 0x80000000
up. They do this because Windows 9x uses that area as a shared heap. The snaffle
takes place as early as they can, before they start loading libraries like ntdll
and kernel32.
The FreeBSD mmap address allocation in the case where no address hint is provided,
always tries to allocate memory above all existing allocations. Obviously this
fails when dlopen() tries to load another shared library.
There is a comment in sys/vm/vm_mmap.c:mmap that mentions "There should really be
a pmap call to determine a reasonable location".
What are people's thoughts about implementing such a thing (and having it do a
better job of choosing an address)?
-- John Birrell _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: PaTaNa: "K7VM2-R3.0 and duron 1.3Gh procesor"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
