Lines Matching refs:as
5 (also known as `keys') to values. Clients may read and write values,
10 arbitrary binary data as values, this should generally be avoided.
24 Paths are /-separated and start with a /, just as Unix filenames.
47 and shared memory, as specified in io/xs_wire.h: each message in
48 either direction is a header formatted as a struct xsd_sockmsg
72 bulk data through xenstore is not recommended as the performance
90 Except as otherwise noted, reserved values are believed to be sent as
96 Error replies are as follows:
120 Integer domid, represented as decimal number 0..65535.
123 represented as integers; unless otherwise specified it
129 reply payloads as applicable:
151 Gives a list of the immediate children of <path>, as only the
156 Same as DIRECTORY, but to be used for children lists longer than
164 GET_PERMS <path>| <perm-as-string>|+
165 SET_PERMS <path>|<perm-as-string>|+?
166 <perm-as-string> is one of the following
214 are changed so as to make it unreadable, in which case future
220 as described above. req_id and tx_id are both 0.
228 Iff <wpath> for the watch was specified as a relative pathname,
241 represented as unsigned decimal. After this, transaction may
242 be referenced by using <transid> (as 32-bit binary) in the
275 for example passing a high-bit-set 32-bit gfn as an unsigned
287 Returns the domain's base path, as is used for relative
302 allows <domid> to behave as if it were dom0 when modifying
330 print <string> to syslog (xenstore runs as daemon) or
331 to console (xenstore runs as stubdom)