12.13. GDC¶
【Debug Information】
# cat /proc/cvitek/gdc
Module: [GDC], Build Time[#1 SMP PREEMPT Wed Feb 24 15:02:47 CST 2021]
-------------------------------RECENT JOB INFO----------------------------
SeqNo ModName TaskNum State InSize(pixel) OutSize(pixel) CostTime(us) HwTime(us)
# 0 VO 1 SUCCESS 921600 921600 3952 3539
# 1 VO 1 SUCCESS 921600 921600 3941 3534
# 2 VO 1 SUCCESS 921600 921600 3952 3553
# 3 VO 1 SUCCESS 921600 921600 3938 3540
# 4 VO 1 SUCCESS 921600 921600 3947 3547
# 5 VO 1 SUCCESS 921600 921600 3936 3536
# 6 VO 1 SUCCESS 921600 921600 3948 3551
# 7 VO 1 SUCCESS 921600 921600 3926 3530
-------------------------------MAX WASTE TIME JOB INFO--------------------
ModName TaskNum State InSize(pixel) OutSize(pixel) CostTime(us) HwTime(us)
VO 1 SUCCESS 921600 921600 4007
3530
-------------------------------GDC JOB STATUS-----------------------------
Success Fail Cancel BeginNum BusyNum ProcingNum
754 0 0 0 0 0
-------------------------------GDC TASK STATUS----------------------------
Success Fail Cancel BusyNum
754 0 0 0
-------------------------------GDC INT STATUS-----------------------------
IntNum IntTm(us) HalProcTm(us)
754 3536 126
-------------------------------GDC CALL CORRECTION STATUS-----------------
TaskSuc TaskFail EndSuc EndFail CbCnt
0 0 0 0 0
【Analysis】
Record several tasks recently completed by GDC module, including the most time-consuming tasks recently, and historical cumulative information.
【Parameter Description】
Parameter |
Decription |
|
|---|---|---|
RECENT JOB INFO |
SeqNo |
Print sequence numbers. Value range: [0, 7] |
ModName |
Module name that submitted the job |
|
TaskNum |
Task numbers included in the job |
|
State |
The processing state of the job. Value range：{FA IL、SUCCESS、WORKING} FAIL：job execution failed SUCCESS：job execution success WORKING：job execution in progress |
|
InSize(pixel) |
The sum of the input image area of each task in the job Unit：pixels Every time a task is added to the job, the input area of the task is added to this item. |
|
OutSize(pixel) |
The sum of the output image area of each task in the job Unit: pixels Every time a task is added to the job, the output area of the task is added to this item. |
|
CostTime(us) |
The job takes a long time from submission to completion. Unit: us. The time includes the processing time of software, hardware and interrupt service program for the task. |
|
HwTime(us) |
The time that the job takes to process in hardware. Unit: US. This time is hardware processing time, generally shorter than CostTime. |
|
MAX WASTE TIME JOBINFO |
All items are the same as members of RECENT JOB INFO |
The most time-consuming job in the last 500 tasks. Its items are the same as the members of recentjob info. Please refer to the above for details. When there are more time-consuming tasks or the total number of tasks exceeds 500, the group value is updated. Through this group of values, we can know the recent GDC performance, and whether GDC processing is not timely. |
GDC JOB STATUS |
Success |
Cumulative number of jobs successfully processed. Increase by 1 when hardware processing is successful. |
Fail |
Cumulative number of jobs that failed to process. When GDC submits a task to the driver layer and fails, 1 is added. As the value increases, you can see the reason for the failure by looking at the log. |
|
Cancel |
Cumulative number of canceled jobs. Add 1 when calling cancelJob interface. |
|
BeginNum |
The number of jobs that the user has created but not yet submitted (EndJob interface). |
|
BusyNum |
The number of tasks submitted by the user (EndJob interface) but not yet submitted to the hardware for processing. |
|
ProcingNum |
The number of tasks in hardware processing. |
|
GDC TASK STATUS |
Success |
Cumulative number of tasks successfully processed. A job contains one or more scaling tasks, so the Success of a job indicates that all the tasks under it are successful, so the cumulative value is faster than the Success item of the job. When the hardware processes a job successfully, this value accumulates the number of tasks under the job. |
Fail |
Cumulative number of tasks that failed to process. If a job fails, all tasks under it will fail. When the job fails to execute, this item accumulates the number of failed tasks under it. As the value increases, you can see the reason for the failure by looking at the log. |
|
Cancel |
The cumulative number of tasks to cancel. When the canceljob interface is called, the execution of all tasks under the job is cancelled, and this item is accumulated. |
|
BusyNum |
The number of tasks that have been added to the job but have not been submitted to the hardware for processing |
|
GDC INT STATUSGDC interrupt status |
IntNum |
The number of GDC interrupted. When the hardware completes a job, the value will increase by 1. |
IntTm(us) |
GDC average interrupt processing time. Unit: us |
|
HalProcTm(us) |
The average time to submit a Job to the driver layer is used by internal debugging. Unit: us |
|
GDC CALL CORRECTIONSTATUSFisheye correctionprocessing status |
TaskSuc |
The number of times the FISHEYE task was successfully added. |
TaskFail |
The number of times adding FISHEYE task failed. |
|
EndSuc |
The number of times GDC successfully submitted the FISHEYE job. |
|
EndFail |
The number of times GDC failed to submit the FISHEYE job. |
|
CbCnt |
The number of times GDC corrects the callbacks after task processing. |