Lines Matching full:uv
7 * Ultravisor (UV) functions. The device only accepts IOCTLs and will only
14 * to existing UV-calls.
19 * by UV and to interpret the UV response. The uvdevice acts as a communication
33 #include <asm/uv.h>
157 * are sane. Every other check is made by the Ultravisor (UV) and won't result
159 * request, sends the UV-call, and copies the result to userspace.
162 * ARCB and User Data are inputs for the UV generated by userspace.
163 * Measurement and Additional Data are outputs for userspace generated by UV.
166 * and secured request to UV and User Data is some plaintext data which is
171 * ARCB, UV will add some Additional Data to the measurement calculation.
174 * If the Retrieve Attestation Measurement UV facility is not present,
175 * UV will return invalid command rc. This won't be fenced in the driver
248 * (UV). Therefore UV errors won't result in a negative return
249 * value. The request is then copied to kernelspace, the UV-call is
257 * If the Add Secret UV facility is not present, UV will return
304 * Every other check is made by the Ultravisor (UV) and won't result in a
305 * negative return value. It builds the request, performs the UV-call, and
308 * The argument specifies the location for the result of the UV-Call.
310 * If the List Secrets UV facility is not present, UV will return invalid
351 * performs the UV-call and copies the return codes to the ioctl control block.
357 * If the Lock Secrets UV facility is not present, UV will return invalid