Claims:1. An apparatus comprising:
at least one memory; and
at least one processor to execute instructions to at least:
identify a first routine based on an identifier of a second routine executed by a graphics processing unit (GPU), the first routine based on an emulation of the second routine;
execute the first routine to determine a first value of a GPU state of the GPU, the first routine having (i) a first argument associated with the second routine and (ii) a second argument corresponding to a second value of the GPU state prior to executing the first routine; and
control a workload of the GPU based on the first value of the GPU state.
, Description:FIELD OF THE DISCLOSURE
[0002] This disclosure relates generally to computers and, more particularly, to methods and apparatus to generate graphics processing unit long instruction traces.

BACKGROUND
[0003] Software developers seek to develop code that may be executed as efficiently as possible. To better understand code execution, profiling is used to measure different code execution statistics such as, for example, execution time, memory consumption, etc. In some examples, profiling is implemented by insertion of profiling instructions into the code. Such profiling instructions can be used to store and analyze information about the code execution.

BRIEF DESCRIPTION OF THE DRAWINGS
[0004] FIG. 1 is a block diagram illustrating an example graphics processing unit long instruction trace (GLIT) engine inserting profiling instructions into an example graphics processing unit (GPU) kernel to be executed by an example GPU.
[0005] FIG. 2 is an illustration of an example implementation of an example portion of the GPU of FIG. 1.
[0006] FIG. 3 depicts an example format of an example long instruction trace.
[0007] FIG. 4 is a block diagram of an example implementation of the GLIT engine of FIG. 1.
[0008] FIG. 5 is an illustration of an example system that may implement the example GPU of FIG. 1 and/or the example GPU portion of FIG. 2 to control operation of an example execution unit hardware thread.
[0009] FIG. 6 is an illustration of an example GPU long instruction trace (GLIT) for the example GPU of FIG. 1 and/or the example GPU portion of FIG. 2.
[0010] FIG. 7 is an illustration of an example system to generate and analyze the GLIT of FIG. 6.
[0011] FIG. 8 is an illustration of an example system to emulate and analyze the GLIT of FIG. 6.
[0012] FIG. 9 depicts an example kernel and an example instrumented kernel.
[0013] FIG. 10 is an illustration of an example workflow to emulate execution of the example instrumented kernel of FIG. 9.
[0014] FIG. 11 depicts example source code to emulate execution of the example instrumented kernel of FIG. 9.
[0015] FIG. 12 depicts example source code to emulate execution of an example software thread.
[0016] FIG. 13 depicts example source code to emulate execution of an example instrumented software thread.
[0017] FIG. 14 depicts example source code to implement an emulation routine.
[0018] FIG. 15 is a flowchart representative of machine readable instructions that may be executed to implement the GLIT engine of FIGS. 1 and/or 4 to improve operation of the example GPU of FIG. 1 and/or the example GPU portion of FIG. 2.
[0019] FIG. 16 is a flowchart representative of machine readable instructions that may be executed to implement the GLIT engine of FIGS. 1 and/or 4 to emulate one or more example GLITs.
[0020] FIG. 17 is another flowchart representative of machine readable instructions that may be executed to implement the GLIT engine of FIGS. 1 and/or 4 to improve operation of the example GPU of FIG. 1 and/or the example GPU portion of FIG. 2.
[0021] FIG. 18 is a block diagram of an example processing platform structured to execute the machine readable instructions of FIGS. 11-17 to implement the example GLIT engine of FIGS. 1 and/or 4.
[0022] FIG. 19 is a block diagram of an example software distribution platform to distribute software (e.g., software corresponding to the example computer readable instructions of FIGS. 11-17) to client devices such as consumers (e.g., for license, sale and/or use), retailers (e.g., for sale, re-sale, license, and/or sub-license), and/or original equipment manufacturers (OEMs) (e.g., for inclusion in products to be distributed to, for example, retailers and/or to direct buy customers).

DETAILED DESCRIPTION
[0023] The figures are not to scale. In general, the same reference numbers will be used throughout the drawing(s) and accompanying written description to refer to the same or like parts. As used herein, connection references (e.g., attached, coupled, connected, and joined) may include intermediate members between the elements referenced by the connection reference and/or relative movement between those elements unless otherwise indicated. As such, connection references do not necessarily infer that two elements are directly connected and/or in fixed relation to each other.