Improve comments.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6321 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/lackey/lk_main.c b/lackey/lk_main.c
index 7ec5154..c85638b 100644
--- a/lackey/lk_main.c
+++ b/lackey/lk_main.c
@@ -106,8 +106,14 @@
// - It does not trace into the OS kernel, so system calls and other kernel
// operations (eg. some scheduling and signal handling code) are ignored.
//
-// - Valgrind replaces some code with its own, notably parts of code for
-// scheduling operations and signal handling. This code is not traced.
+// - It could model loads and stores done at the system call boundary using
+// the pre_mem_read/post_mem_write events. For example, if you call
+// fstat() you know that the passed in buffer has been written. But it
+// currently does not do this.
+//
+// - Valgrind replaces some code (not much) with its own, notably parts of
+// code for scheduling operations and signal handling. This code is not
+// traced.
//
// - There is no consideration of virtual-to-physical address mapping.
// This may not matter for many purposes.