JPH1115704A - Emulation control method and emulator - Google Patents

Abstract

PROBLEM TO BE SOLVED: To obtain an emulation control method and an emulator by which the time that takes from the moment when a task that is an object transits to a ready state to the moment when it transits to a run state at the time of debugging a program that is carried out under an, is directly obtained, OS and the time measurement result to a user such as a programmer, is presented. SOLUTION: A time measurement stop watch 8 which starts time measurement when a task that is searched for by a task control block supervisory circuit 3 which searches for a task that transits to a ready state is a task of a previously determined supervisory object, stops time measurement when a run state task supervisory circuit 4 detects that the task of a supervisory object is in a run state and measures time which takes from the moment when the task of the supervisory object becomes a ready state to the moment when it becomes a run state is provided.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to an emulation control method used for debugging a program executed under an OS and an emulator apparatus using the control method.

[0002]

2. Description of the Related Art FIG. 5 is a block diagram showing an example of the configuration of an emulator device using a conventional emulation control method. In FIG. 5, reference numeral 31 denotes a target CPU which is an emulation target, and 32 denotes a program to be debugged and an OS. , A trace memory 39 for recording the contents of the target memory 32 being debugged, a host computer 40 for controlling emulation such as storing a program to be debugged in the target memory 32, 41 is an emulator device, 42 is an emulator control CP for controlling each unit of the emulator device 41
U and 43 are host communication circuits connecting the host computer 40 to the emulator device 41 for communication between the host computer 40 and the emulator device 41, and 44 is a target C
A PU bus 45 is an emulator control CPU bus.

Next, the operation will be described. The conventional emulator device as shown in FIG. 5 is designed to measure the time that elapses from the moment when the monitored task transitions to the READY state to the time when the task changes to the RUN state when debugging a program executed under the control of the OS. It does not have a direct means to measure, but instead uses a trace memory 39 to record the contents of the target memory 32 during debugging,
The time that elapses from the moment when the monitored task transitions to the READY state to the moment when the task changes to the RUN state is indirectly obtained.

First, in the emulator device 41, a time interval for writing the contents from the target memory 32 to the trace memory 39 (hereinafter referred to as a sampling time).
Is determined. Next, the contents of the target memory 32 in which the task control block managed by the OS and the task number in the RUN state are written are stored in the trace memory 3.
9 to be written. Then, the host computer 4
0 transfers the program to be debugged to the target memory 32, starts the execution of the program to be debugged by the target CPU 31, and starts debugging. Then, after a lapse of time that the task to be monitored is considered to have been processed, the host computer 40
Reads the contents of the trace memory 39 via the host communication circuit 43. Since the read contents of the trace memory 39 include information on transitions of all tasks, the host computer 40 determines from the contents that the task to be monitored has transitioned from any state to the READY state. The point where the task to be monitored has transitioned from the READY state to the RUN state is specified, and the time elapsed between the two points is obtained from the sampling number and the sampling time interposed between the two points. .

However, in this method, since there is much data to be written from the target memory 32 to the trace memory 39, the trace memory 39 may overflow. Further, since the information of all the tasks is written from the target memory 32 to the trace memory 39, it takes time and effort to specify only the information on the task to be monitored from the information. Furthermore, the location where the task to be monitored has transitioned from any state to the READY state and the task being monitored
Counting the number of samples interposed between the DY state and the transition to the RUN state requires more time and it is easy to make a mistake, so from the moment the task transitions to the READY state to the transition to the RUN state. This method of indirectly measuring the time that elapses is rarely used.

[0006]

Since the conventional emulation control method and the conventional emulation device are configured as described above, the task to be debugged when the program executed under the OS is debugged is in the READY state. The time that elapses from the moment of transition to the moment of transition to the RUN state must be indirectly obtained from the information of all the tasks transferred to the trace memory 39, and only the information of the task to be monitored is obtained from the information. There is a problem that it takes a lot of trouble to specify, and debugging cannot be performed efficiently.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problem. When debugging a program to be executed under an OS, a target task transitions from a ready state to a run state. It is an object of the present invention to obtain an emulation control method and an emulator device that can directly determine a time that elapses until a transition moment and present the time measurement result to a user such as a programmer.

[0008]

According to the first aspect of the present invention, there is provided an emulation control method in which a task which has transitioned to a READY state is searched for by monitoring task information, and the found task is a predetermined monitoring target task. If there is, start time measurement, and if the task to be monitored is RU
When detecting that the state has become N, the time measurement is stopped,
R from the moment the monitored task enters the READY state
It measures the time that has passed until the moment when it enters the UN state.

The emulation control method according to the second aspect of the present invention measures the elapsed time as described above, and then temporarily records the measured elapsed time in the emulator device.

The emulator device according to the third aspect of the present invention starts time measurement if the task found by the task control block monitoring means is a predetermined monitoring target task, and the RUN status task monitoring means sets the monitoring target Time measurement means for stopping the time measurement when detecting that the task is in the RUN state, and measuring the time elapsed from the moment the monitored task enters the RUN state to the moment it enters the RUN state. Things.

According to a fourth aspect of the present invention, there is provided an emulator device having a trace memory for recording the elapsed time measured by the time measuring means.

According to a fifth aspect of the present invention, in the emulator apparatus, the time measurement means starts time measurement when the task number output from the task control block monitoring means matches the task number held in the monitored task number register. When the task number output from the task number monitoring means matches the task number stored in the monitoring target task number register, the time measurement is stopped.

According to a sixth aspect of the present invention, in the emulator apparatus, the time measuring means outputs a start signal when the task number output by the task control block monitoring means matches the task number of the task to be monitored. 1
And a second comparator that outputs a stop signal when the task number output by the RUN status task monitoring means matches the task number of the task to be monitored, and starts time measurement in response to the start signal. A time measurement stopwatch that stops the time measurement in response to a stop signal.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below. Embodiment 1 FIG. FIG. 1 is a block diagram showing a configuration of an emulator apparatus for realizing an emulation control method according to Embodiment 1 of the present invention. In the figure, reference numeral 1 denotes a target CPU as an emulation target, and 2 denotes a program to be debugged and an OS. The target memory 3 for storing information on tasks executed by the target CPU 1, that is, task information such as task control blocks, monitors the task control blocks stored in the target memory 2. A task control block monitoring circuit (task control block monitoring means) for searching for a task that has transitioned to a task state and outputting the task number, monitors the task in the RUN state and outputs the task number of the task in the RUN state. RUN status task monitoring circuit (RUN status task monitoring means), 5 and 6 are comparators, 7 is a monitoring target task number register holding the task number of the monitoring target task, and 8 is a transition of the monitoring target task to the READY state. A time measurement stopwatch for measuring the time elapsed from the moment to the transition to the RUN state, 9 is a trace memory for recording the time measurement result by the time measurement stopwatch 8, and 10 is a debug target program stored in the target memory 2. And a host computer for controlling emulation, such as writing the task number of the monitored task to the monitored task number register 7.
2 is an emulator control CPU for controlling each unit of the emulator apparatus 11, 13 is a host communication circuit for connecting the host computer 10 to the emulator apparatus 11 for communication between the host computer 10 and the emulator apparatus 11, and 14 is A target CPU bus 15 is an emulator control CPU bus. The time measuring means includes two comparators 5 and 6, and a time measuring stopwatch 8.

FIG. 2 is an explanatory diagram showing a state of a task ready queue managed by the OS, and FIG. 3 is an explanatory diagram showing task information in the target memory 2. In FIG. 3, reference numeral 21 denotes a current RUN state task number written by the OS, and reference numeral 22 denotes a task control block (task number and task state) written in the target memory 2 by the OS. Actually, the task number is a binary number. Here, for the sake of simplicity, the task numbers of the tasks TA, TB, TC, and TD shown in FIG. It is assumed that they are "1", "2", "3", "4", and "5".

Next, the operation will be described. Before emulation execution, the program to be debugged is stored in the target memory 2 together with the OS. Then, when the emulation execution is started, the program to be debugged is executed in the target CPU 1 under the OS, and the tasks are sequentially processed.

Thereafter, it is assumed that the execution of the program is interrupted at some point. Also, at this time, it is assumed that the task TA, TB, TC, and TD are waiting for execution in the task ready queue in a state where the tasks TA, TB, TC, and TD are connected by the OS, as shown in FIG. At this time, the task number “1” of the task TA at the head of the task ready queue is written in the RUN status task number 21 in the target memory 2 by the OS. Further, the task TE whose execution has been interrupted and the states of tasks TA, TB, TC and TD waiting to be executed while being connected to the task ready queue are written in the task control block 22 by the OS. . Here, task TA of task number “1”
Is the RUN state, the state of the task TB with the task number “2” is the READY state, and the task TC with the task number “3”.
State is READY state, task T of task number "4"
The state of D is the READY state, and the state of the task TE of the task number “5” whose execution is suspended is the WAIT state.

FIG. 4 shows that a predetermined task in the emulator device according to the first embodiment is changed from the READY state to the RU state.
It is a flowchart which shows the flow of operation | movement which measures the time (waiting time) required until it changes to N state in real time. In a situation where the execution is suspended as described above, first, in step ST1, the host computer 10
Writes the task number of the task to be monitored to the monitored task number register 7 via the host communication circuit 13. In the first embodiment, the task number “5” of the task TE is written. Note that this task number is input to the host computer 1 in advance by a user such as a programmer via an input device or the like connected to the host computer 1. And the emulator device is the target CP
Resume execution of U1.

Next, in step ST2, the task control block monitoring circuit 3
A task that has transitioned from any state to the READY state is searched for from all the tasks TE, TA, TB, TC, and TD recorded in the task control block 22 shown in FIG. For example, the task T to be monitored
Assuming that E transitions from the WAIT state to the READY state, the OS connects the task TE at the end of the task ready queue, and changes the state of the task TE recorded in the task control block 22 from the WAIT state to the READY state. Then, the task control block monitoring circuit 3 searches for the task TE from all the tasks recorded in the task control block 22, and outputs the task number “5” of the task TE.

In this way, when the task control block monitoring circuit 3 searches for a task that has transitioned to the READY state, the comparator 5 determines in step ST3 the task number of the task found in step ST2 and the monitoring target task number register. 7 is compared with the task number written in 7 to determine whether they match. As a result of the determination, if they match, the process proceeds to step ST4, and if they do not match, the process proceeds to step ST2.
Return to At this time, if the task found by the task control block monitoring circuit 3 is the task TE as described above, the task number “5” matches the task number written in the monitoring target task number register 7. Therefore, the process proceeds to step ST4.

If the task number of the task found in step ST2 matches the task number written in the monitoring target task number register 7, the process proceeds to step ST2.
At 4, the comparator 5 outputs a start signal to the time measurement stopwatch 8 to start time measurement. Then, in step ST5, the RUN state task monitoring circuit 4 obtains the task number of the task currently in the RUN state from the RUN state task number 21 in the target memory 2 written by the OS. In this case, a plurality of tasks TA, TB, T as shown in FIG.
C and TD are connected and waiting for execution, and after the task TD, the task TE to be monitored is connected as described above. Therefore, the RUN status task monitoring circuit 4 first obtains the task number “1” of the task TA at the head. Then, in step ST6, the comparator 6 compares the task number obtained by the RUN status task monitoring circuit 4 in step ST5 with the task number written in the monitoring target task number register 7, and determines whether or not they match. judge. As a result of the determination, if they match, the process proceeds to step ST7, and if they do not match, the process returns to step ST5. In this case, the task number obtained first by the RUN status task monitoring circuit 4 is “1”, and the task number written in the monitoring target task number register 7 is “5”, so that the step ST5
Return to

Next, when the target CPU 1 finishes processing the task TA having the task number "1", the OS deletes information (task number) relating to the task TA at the head of the task ready queue, and is connected as follows. Shift tasks one by one. Thereafter, while the target CPU 1 sequentially processes the tasks TB, TC and TD, the RUN status task monitoring circuit 4 similarly obtains the task numbers "2", "3" and "4" of the first task in the same manner. During this time,
These task numbers are stored in the monitoring target task number register 7.
Does not match the task number written in step ST7, the process does not proceed to step ST7, and steps ST5 to ST6 are repeated.

When the target CPU 1 finishes processing the tasks TB, TC and TD in this way, the OS causes the task TE to transition from the READY state to the RUN state.
The OS sends the task T to the RUN status task number 21 shown in FIG.
The task number “5” of E is written, and the processing of the task TE of this task number is started. As a result, the RUN state task monitoring circuit 4 obtains the task number “5” of the task TE at the head of the task ready queue, so that the step ST
The condition of No. 6 becomes true, and the process proceeds to Step ST7. Then, in step ST7, the comparator 6 outputs a stop signal to the time measurement stopwatch 8 to stop the time measurement. Then, the emulator control CPU 12
In step ST8, the time measurement result of the time measurement stopwatch 8 is written into the trace memory 9, and from the moment the monitored task transitions to the READY state, R
The measurement processing of the time elapsed until the moment when the state transits to the UN state is ended. After that, the host computer 10 compares the time measurement result written in the trace memory 9 with the host communication circuit 13.
Can be read arbitrarily through. The read time measurement result is displayed on a display device of the host computer 10 for presentation to a user such as a programmer, or is stored in a storage device in the host computer 10.

As described above, according to the first embodiment, when a program executed under the OS is debugged, the task to be monitored transitions from the moment when the task transitions to the READY state to the RUN state. This has the effect of measuring the time elapsed until the moment when it is performed in real time. As a result, a user such as a programmer can take measures to reduce the task overhead based on the time measurement result, and develop a program that can guarantee task activation.

[0025]

As described above, according to the first aspect of the present invention, the emulation control method searches for a task that has transitioned to the READY state by monitoring task information, and the searched task determines a predetermined monitoring target. If it is a task, start time measurement, and if the task to be monitored is R
Since the time measurement is stopped when detecting the change to the UN state, and the time elapsed from the moment when the task to be monitored changes to the READY state to the moment to change to the RUN state is configured. Task is R
There is an effect that the time elapsed from the moment of transition to the EADY state to the moment of transition to the RUN state can be measured in real time. This also has the effect that a user such as a programmer can take measures to reduce the task overhead based on the time measurement result and develop a program that can guarantee task activation.

According to the second aspect of the present invention, the emulation control method is configured to measure the elapsed time as described above and then temporarily record the measured elapsed time in the emulator device. The elapsed time from the moment when the target task transitions to the READY state to the moment when the task transitions to the RUN state is measured in real time, and the elapsed time is measured for presentation to the user such as a programmer via the host computer. There is an effect that time can be recorded.

According to the third aspect of the present invention, if the task found by the task control block monitoring means is a predetermined monitoring target task, the emulator apparatus starts time measurement, and the RUN status task monitoring means sets When detecting that the task to be monitored is in the RUN state, the time measurement is stopped, and time measuring means for measuring the time elapsed from the moment when the task to be monitored enters the RUN state until the moment when the task to be monitored enters the RUN state. Since the monitoring target is provided, there is an effect that the time elapsed from the moment when the task to be monitored changes to the READY state to the moment when the task changes to the RUN state can be measured in real time. This also has the effect that a user such as a programmer can take measures to reduce the task overhead based on the time measurement result and develop a program that can guarantee task activation.

According to the fourth aspect of the present invention, since the emulator device is provided with the trace memory for recording the elapsed time measured by the time measuring means, the task to be monitored is in the READY state. There is an effect that the elapsed time from the moment of transition to the moment of transition to the RUN state is measured in real time, and the elapsed time measured for presenting this to a user such as a programmer via a host computer can be recorded. .

According to the fifth aspect of the present invention, the emulator device measures the time when the task number output from the task control block monitoring means matches the task number held in the monitoring target task number register. Is started, and when the task number output from the task number monitoring means matches the task number held in the monitoring target task number register, the time measurement is stopped, so that the monitoring target task is ready. There is an effect that the time elapsed from the moment of transition to the state to the moment of transition to the RUN state can be measured in real time.

According to the sixth aspect of the present invention, the emulator device outputs the start signal when the task number output by the task control block monitoring means and the task number of the task to be monitored coincide with each other by the time measuring means. A first comparator, a second comparator that outputs a stop signal when the task number output by the RUN status task monitoring means matches the task number of the task to be monitored, and a time measurement in response to the start signal. A time measurement stopwatch that starts and stops the time measurement in response to the stop signal is provided, so that the task to be monitored changes from the moment of transition to the READY state to the moment of transition to the RUN state. There is an effect that the elapsed time can be measured in real time.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of an emulator device that implements an emulation control method according to a first embodiment of the present invention.

FIG. 2 is an explanatory diagram showing a state of a task ready queue managed by an OS.

FIG. 3 shows a target memory 2 managed by the OS.
FIG. 4 is an explanatory diagram showing task information in the submenu.

FIG. 4 is a flowchart showing a process flow of an emulation control method according to the first embodiment of the present invention.

FIG. 5 is a block diagram illustrating a configuration of an emulator device that implements a conventional emulation control method.

[Explanation of symbols]

1 target CPU, 3 task control block monitoring circuit (task control block monitoring means),
4 RUN status task monitoring circuit (RUN status task monitoring means), 5, 6 comparator (time measuring means), 7
Monitored task number register, 8 time stopwatch (time measuring means), 9 trace memory, 11
Emulator device.

Claims (6)

[Claims] When a target CPU executes a program to be debugged, it monitors task information to search for a task that has transitioned to a READY state, and if the searched task is a predetermined task to be monitored, time measurement is performed. Is started, and when it is detected that the task to be monitored is in the RUN state by monitoring the task in the RUN state, the time measurement is stopped, and RUN is started from the moment when the monitored task enters the READY state. An emulation control method that measures the time that has elapsed until the moment when the state is reached. 2. The method according to claim 1, wherein the elapsed time from the moment when the task to be monitored enters the READY state to the moment when the task enters the RUN state is measured, and the measured elapsed time is temporarily recorded in the emulator device. The emulation control method according to claim 1. 3. A task control block monitoring means for monitoring a task control block when a target CPU executes a program to be debugged, thereby searching for a task that has transitioned to a READY state, and a RUN.
RUN status task monitoring means for monitoring status tasks;
When the task found by the task control block monitoring means is a predetermined monitoring target task, time measurement is started, and when the RUN state task monitoring means detects that the monitoring target task is in the RUN state, Stop the time measurement and the monitored task
An emulator device comprising: a time measuring means for measuring a time elapsed from the moment when the DY state is entered to the moment when the RUN state is entered. 4. A trace memory for recording the time elapsed from the moment when the task to be monitored enters the READY state to the moment when it enters the RUN state, measured by the time measuring means. 3. The emulator device according to 3. 5. A monitoring target task number register for holding a task number of a task to be monitored by the task control block monitoring means, wherein the task control block monitoring means monitors a task control block to enter a READY state. When the transitioned task is found, the task number is output. The RUN state task monitoring means monitors the task number of the RUN state task and outputs the task number. The time measurement means outputs the task control block monitoring means. When the number matches the task number stored in the monitored task number register, time measurement is started, and the task number output by the task number monitoring means matches the task number stored in the monitored task number register. Stop the time measurement when The emulator according to claim 3 or 4, wherein 6. The time measuring means compares a task number output by the task control block monitoring means with a task number held in a monitoring target task number register, and outputs a start signal when they match, A task number output by the RUN status task monitoring means is compared with a task number held in the monitored task number register, and when they match, a second comparator which outputs a stop signal, and time measurement in response to the start signal 6. The emulator device according to claim 5, further comprising: a time measurement stopwatch that starts the time measurement and stops the time measurement in response to the stop signal.