[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 04/11] doc: document mach_port_set_protected_payload
From: |
Richard Braun |
Subject: |
Re: [PATCH 04/11] doc: document mach_port_set_protected_payload |
Date: |
Mon, 17 Feb 2014 23:35:12 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Mon, Feb 17, 2014 at 06:20:54PM +0100, Justus Winter wrote:
> +@deftypefun kern_return_t mach_port_set_protected_payload (@w{ipc_space_t
> @var{task}}, @w{mach_port_t @var{name}}, @w{unsigned long @var{payload}})
> +The function @code{mach_port_set_protected_payload} sets the protected
> +payload to @var{payload}. If @var{payload} is non-zero, the
> +@code{msgh_protected_payload} field will be set to @var{payload} if a
> +message is delivered to @var{name}.
If I'm right, this also means switching back from the protected payload
is done by calling this RPC with a payload of 0. It could be worth
emphasizing that 0 is an invalid value for a protected payload.
--
Richard Braun
- protected payloads for GNU Mach, Justus Winter, 2014/02/17
- [PATCH 01/11] include: skip routines related to migrating threads, Justus Winter, 2014/02/17
- [PATCH 04/11] doc: document mach_port_set_protected_payload, Justus Winter, 2014/02/17
- Re: [PATCH 04/11] doc: document mach_port_set_protected_payload,
Richard Braun <=
- [PATCH 02/11] ipc: add protected payload, Justus Winter, 2014/02/17
- [PATCH 03/11] ipc: implement mach_port_set_protected_payload, Justus Winter, 2014/02/17
- [PATCH 07/11] include: define MACH_MSG_TYPE_PROTECTED_PAYLOAD, Justus Winter, 2014/02/17
- [PATCH 08/11] doc: document MACH_MSG_TYPE_PROTECTED_PAYLOAD, Justus Winter, 2014/02/17
- [PATCH 06/11] doc: document msgh_protected_payload, Justus Winter, 2014/02/17
- [PATCH 10/11] ipc: clear the payload when moving a receive port, Justus Winter, 2014/02/17
- [PATCH 05/11] include: add msgh_protected_payload to mach_msg_header_t, Justus Winter, 2014/02/17
- [PATCH 11/11] doc: document message semantics with protected payloads, Justus Winter, 2014/02/17