Add link to testhr.

vmam was merged into vm.

Copied from Perforce
 Change: 187363
 ServerID: perforce.ravenbrook.com

mps/design/index.txt

@@ -108,7 +108,6 @@ type_                   General MPS types
 version-library_        Library version mechanism
 version_                Software versions
 vm_                     Virtual mapping
-vman_                   Generic virtual mapping
 vmo1_                   VM Module on DEC Unix
 vmso_                   VM Design for Solaris
 writef_                 The WriteF function 
@@ -175,6 +174,7 @@ writef_                 The WriteF function
 .. _strategy: strategy
 .. _telemetry: telemetry
 .. _tests: tests
+.. _testthr: testthr
 .. _thread-manager: thread-manager
 .. _thread-safety: thread-safety
 .. _trace: trace

mps/design/vman.txt

@@ -1,98 +0,0 @@
-.. mode: -*- rst -*-
-
-Generic virtual mapping
-=======================
-
-:Tag: design.mps.vman
-:Author: David Jones
-:Date: 1996-11-07
-:Status: complete document
-:Revision: $Id$
-:Copyright: See `Copyright and License`_.
-:Index terms: pair: ANSI fake VM; design
-
-
-Introduction
-------------
-
-_`.intro`: The generic virtual mapping module implements the virtual
-mapping interface (see design.mps.vm_) using only services provided by
-the Standard C Library (standard.ansic.7).
-
-.. _design.mps.vm: vm
-
-_`.readership`: Any MPS developer.
-
-
-Design
-------
-
-_`.page.size`: The generic VM uses a fake page size, given by the
-constant ``VMAN_PAGE_SIZE`` in ``config.h``.
-
-_`.reserve`: Address space is "reserved" by calling ``malloc()``.
-
-_`.release`: Address space is "released" by calling ``free()``.
-
-_`.map`: Mapping (and unmapping) fills the mapped region with copies
-of ``VMJunkBYTE`` to emulate the erasure of freshly mapped pages by
-virtual memory systems.
-
-
-Document History
-----------------
-- 1996-11-07 David Jones. Incomplete document.
-
-- 2002-06-07 RB_ Converted from MMInfo database design document.
-
-- 2013-05-23 GDR_ Converted to reStructuredText.
-
-- 2014-06-18 GDR_ Bring up to date.
-
-- 2014-10-22 GDR_ Complete design.
-
-.. _RB: http://www.ravenbrook.com/consultants/rb/
-.. _GDR: http://www.ravenbrook.com/consultants/gdr/
-
-
-Copyright and License
----------------------
-
-Copyright © 2013-2014 Ravenbrook Limited. All rights reserved.
-<http://www.ravenbrook.com/>. This is an open source license. Contact
-Ravenbrook for commercial licensing options.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions are
-met:
-
-#. Redistributions of source code must retain the above copyright
-   notice, this list of conditions and the following disclaimer.
-
-#. Redistributions in binary form must reproduce the above copyright
-   notice, this list of conditions and the following disclaimer in the
-   documentation and/or other materials provided with the distribution.
-
-#. Redistributions in any form must be accompanied by information on how
-   to obtain complete source code for this software and any
-   accompanying software that uses this software.  The source code must
-   either be included in the distribution or be available for no more than
-   the cost of distribution plus a nominal fee, and must be freely
-   redistributable under reasonable conditions.  For an executable file,
-   complete source code means the source code for all modules it contains.
-   It does not include source code for modules or files that typically
-   accompany the major components of the operating system on which the
-   executable file runs.
-
-**This software is provided by the copyright holders and contributors
-"as is" and any express or implied warranties, including, but not
-limited to, the implied warranties of merchantability, fitness for a
-particular purpose, or non-infringement, are disclaimed.  In no event
-shall the copyright holders and contributors be liable for any direct,
-indirect, incidental, special, exemplary, or consequential damages
-(including, but not limited to, procurement of substitute goods or
-services; loss of use, data, or profits; or business interruption)
-however caused and on any theory of liability, whether in contract,
-strict liability, or tort (including negligence or otherwise) arising in
-any way out of the use of this software, even if advised of the
-possibility of such damage.**