blob: 33a2dcc85750db9c091f368e9509f6f456ab6f77 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook MathML Module V1.1b1//EN"
"" [
<!ENTITY cl_device_type_Inc SYSTEM "cl_device_type_Inc.xml">
<holder>The Khronos Group Inc.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and/or associated documentation files (the
"Materials"), to deal in the Materials without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Materials, and to
permit persons to whom the Materials are furnished to do so, subject to
the condition that this copyright notice and permission notice shall be included
in all copies or substantial portions of the Materials.</holder>
<!-- ================================ SYNOPSIS -->
<refnamediv id="clGetHostTimer">
<refpurpose>Return the current value of the host clock as seen by device.</refpurpose>
<refsynopsisdiv xmlns:xlink=""><title></title>
<link xlink:href="scalarDataTypes.html">cl_int</link>
<link xlink:href="abstractDataTypes.html">cl_device_id</link>
<link xlink:href="scalarDataTypes.html">cl_ulong *</link>
<!-- ================================ PARAMETERS -->
<refsect1 id="parameters"><title>Parameters</title>
A device returned by
Will be updated with the value of the current timer in nanoseconds. The
resolution of the timer may be queried via
and the flag
<!-- ================================ NOTES -->
<refsect1 id="notes"><title>Notes</title>
Return the current value of the host clock as seen by
<varname>device</varname>. This value is in the same timebase
as the host_timestamp returned from
The implementation will
return with as low a latency as possible to
allow a correlation with a subsequent application
sampled time. The host timestamp and device
timestamp returned by this function and
each have an implementation defined timebase. The timestamps
will always be in their respective timebases
regardless of which query function is used. The
timestamp returned from
for an event on a device and a device
timestamp queried from the same device will
always be in the same timebase.
<!-- ================================ ERRORS -->
<refsect1 id="errors"><title>Errors</title>
<function>clGetHostTimer</function> will return <errorname>CL_SUCCESS</errorname>
with a time value in <varname>host_timestamp</varname> if provided.
Otherwise, it returns one of the following errors:
<itemizedlist mark="disc">
<errorname>CL_INVALID_DEVICE</errorname> if <varname>device</varname> is not
a valid OpenCL device.
<errorname>CL_INVALID_VALUE</errorname> if <varname>host_timestamp</varname> is NULL.
<errorname>CL_OUT_OF_RESOURCES</errorname> if there is a failure to allocate resources
required by the OpenCL implementation on the device.
<errorname>CL_OUT_OF_HOST_MEMORY</errorname> if there is a failure to allocate
resources required by the OpenCL implementation on the host.
<!-- ================================ EXAMPLE -->
<refsect2 id="example1">
<informaltable frame="none">
<tgroup cols="1" align="left" colsep="0" rowsep="0">
<colspec colname="col1" colnum="1" />
Example goes here - it will be set in "code" type with white space preserved.
<!-- ================================ SPECIFICATION -->
<!-- Set the "uri" attribute in the <olink /> element to the "named destination" for the PDF page
<refsect1 id="specification"><title>Specification</title>
<para><imageobject><imagedata fileref="pdficon_small1.gif" format="gif" /></imageobject>
<olink uri="clGetHostTimer">OpenCL Specification</olink>
<!-- ================================ ALSO SEE -->
<refsect1 id="seealso"><title>Also see</title>
<!-- ============================== COPYRIGHT -->
<!-- Content included from -->
<refsect3 id="Copyright"><title></title>
<imagedata fileref="KhronosLogo.jpg" format="jpg" />
<para />
<!-- 29-Oct-2015, API rev. 19 -->