03.05.2012 21:22, Stas Sergeev wrote: >> That functionality has been there since October 2004 (git commit >> 879e51 during the 1.3.2 release cycle), and I certainly wouldn't want >> to kill it. But no actual mapping takes place there and then (inside >> DPMI function 0x800), all it does is to return the DOS address of the >> pre-mapped hardware RAM (from alloc_mapping: mmap_mapping does no >> actual mapping for these addresses, but returns the same thing as the >> alloc_mapping call just before that, and mprotect()s), since that is >> sufficient > This is sufficient because MAP_32BIT is used, while otherwise it > would not be sufficient. Oh, and please recall the fact that most DPMI clients do not like pointers with bit 31 set, so MAP_32BIT is not even the reliable solution. I'd really rather get rid of it forever.
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
