Add procfs/kmm to show the state of the kernel heap

TODO

@@ -1,4 +1,4 @@
-NuttX TODO List (Last updated February 2, 2016)
+NuttX TODO List (Last updated February 6, 2016)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 This file summarizes known NuttX bugs, limitations, inconsistencies with
@@ -14,8 +14,8 @@ nuttx/
   (3)  Signals (sched/signal, arch/)
   (2)  pthreads (sched/pthread)
   (0)  Message Queues (sched/mqueue)
-  (7)  Kernel/Protected Build
-  (4)  C++ Support
+  (6)  Kernel/Protected Build
+  (3)  C++ Support
   (6)  Binary loaders (binfmt/)
  (12)  Network (net/, drivers/net)
   (4)  USB (drivers/usbdev, drivers/usbhost)
@@ -463,14 +463,6 @@ o Kernel/Protected Build
   Priority:    Medium/High -- the kernel build configuration is not fully fielded
                yet.
 
-  Title:       NSH free COMMAND LIMITATION
-  Description: The NSH 'free' command only shows memory usage in the user
-               heap only, not usage in the kernel heap.  I am thinking that
-               kernel heap memory usage should be available in /proc/memory.
-               Better /proc/kmm
-  Status:      Open
-  Priority:    Medium/High
-
   Title:       NxTERM PARTITIONING.
   Description: NxTerm is implemented (correctly) as a driver that resides
                in the nuttx/ directory.  However, the user interfaces must be
@@ -590,20 +582,6 @@ o C++ Support
                would be to get a hold of the compilers definition of size_t.
   Priority:    Low.
 
-  Title:       STATIC CONSTRUCTORS
-  Description: Need to call static constructors
-               Update:  Static constructors are implemented for the STM32 F4 and
-               this will provide the model for all solutions.  Basically, if
-               CONFIG_HAVE_CXXINITIALIZE=y is defined in the configuration, then
-               board-specific code must provide the interface up_cxxinitialize().
-               up_cxxinitialize() is called from application logic to initialize
-               all static class instances.  This TODO item probably has to stay
-               open because this solution is only available on STM32 F4.
-  Status:      Open
-  Priority:    Low, depends on toolchain.  Call to gcc's built-in static
-               constructor logic will probably have to be performed by
-               user logic in the application.
-
   Title:       STATIC CONSTRUCTORS AND MULTITASKING
   Description: The logic that calls static constructors operates on the main
                thread of the initial user application task.  Any static