.TH "Field Value Queries" 3 "24 Apr 2019" "Version 1.1" "NVML" \" -*- nroff -*-
.ad l
.nh
.SH NAME
Field Value Queries \- 
.SS "Functions"

.in +1c
.ti -1c
.RI "\fBnvmlReturn_t\fP DECLDIR \fBnvmlDeviceGetFieldValues\fP (nvmlDevice_t device, int valuesCount, \fBnvmlFieldValue_t\fP *values)"
.br
.in -1c
.SH "Detailed Description"
.PP 
This chapter describes NVML operations that are associated with retrieving Field Values from NVML 
.SH "Function Documentation"
.PP 
.SS "\fBnvmlReturn_t\fP DECLDIR nvmlDeviceGetFieldValues (nvmlDevice_t device, int valuesCount, \fBnvmlFieldValue_t\fP * values)"
.PP
Request values for a list of fields for a device. This API allows multiple fields to be queried at once. If any of the underlying fieldIds are populated by the same driver call, the results for those field IDs will be populated from a single call rather than making a driver call for each fieldId.
.PP
\fBParameters:\fP
.RS 4
\fIdevice\fP The device handle of the GPU to request field values for 
.br
\fIvaluesCount\fP Number of entries in values that should be retrieved 
.br
\fIvalues\fP Array of \fIvaluesCount\fP structures to hold field values. Each value's fieldId must be populated prior to this call
.RE
.PP
\fBReturns:\fP
.RS 4
.IP "\(bu" 2
\fBNVML_SUCCESS\fP if any values in \fIvalues\fP were populated. Note that you must check the nvmlReturn field of each value for each individual status
.IP "\(bu" 2
\fBNVML_ERROR_INVALID_ARGUMENT\fP if \fIdevice\fP is invalid or \fIvalues\fP is NULL 
.PP
.RE
.PP

.SH "Author"
.PP 
Generated automatically by Doxygen for NVML from the source code.