History log of /fuchsia/zircon/docs/syscalls/vmo_get_size.md
Revision Date Author Comments
# 99387274 23-Jul-2018 George Kulakowski <kulakowski@google.com>

[docs][syscalls] Add TODOs about documenting system call rights

ZX-2399 #comment

Test: no functional change
Change-Id: I1f285c677e2444fcf1d720d7ecbd9f490c303962


# f3e2126c 12-Sep-2017 Roland McGrath <mcgrathr@google.com>

[zx] Magenta -> Zircon

The Great Renaming is here!

Change-Id: I3229bdeb2a3d0e40fb4db6fec8ca7d971fbffb94


# 4e0f8792 09-Jun-2017 George Kulakowski <kulakowski@google.com>

[docs][errors] Rename all the errors in docs/ to MX_OK and MX_ERR_*

Change-Id: I62451456a83145760c6454a619d4c699ce8e9017


# bca62941 04-Apr-2017 Travis Geiselbrecht <travisg@google.com>

[kernel][vm][clone] implement VMO clone operation

Add a syscall and mechanism to create a clone of a range
of an existing vmo into a new vmo. At the moment only
supports the COPY_ON_WRITE flag, so the cloned vmo will
fault in new copies of pages as they are written to.

Change-Id: I318182438a411952fdcf1cc121f59b600587c852


# d4ba06df 23-Feb-2017 George Kulakowski <kulakowski@google.com>

[docs][syscalls] Fix all the manpages

Change-Id: Ie9ba25060f3331de8d9c178caf6332fb48fc80f5


# 63a28e08 07-Nov-2016 Travis Geiselbrecht <travisg@google.com>

[docs][syscalls][vmo] start some simple syscall docs for vmos

Change-Id: I428d83224d977e83d8e3a543984a903d2615c0a1