JP2015014931A - Simulator apparatus, program, and log information processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technique for outputting logs that make clear the time sequence of operations performed by firmware and hardware.SOLUTION: A simulator apparatus comprises: an execution unit emulating instructions of firmware, acquiring time information in response to an input/output instruction from the firmware, adding the time information to the input/output instruction, and executing the input/output instruction; a first virtual device outputting first operation information output in a first output form and the time information in response to execution of the input/output instruction to which the time information is added, the first operation information being associated with the time information; a second virtual device outputting second operation information output in a second output form and the time information in response to the execution of the input/output instruction to which the time information is added, the second operation information being associated with the time information; and an integration unit outputting operation history information in which the first operation information and the second operation information are arranged in a time sequence on the basis of the time information.

Description

  The present invention relates to a log information processing technique of a simulator device.

  In debugging embedded software (hereinafter referred to as “Firmware (FW)”), FW is tested by using an actual ICE (device on which embedded software is mounted) and using an ICE (In-circuit emulator). However, in debugging for illegal operations such as fault tests, if the hardware component (hereinafter referred to as "Hardware (HW)") such as LSI (Large Scale Integration) causes an error, the actual HW is destroyed or a pseudo failure It is necessary to create a dedicated jig.

  Therefore, in recent years, a debugging method using a software emulator (hereinafter referred to as “simulator”) is often used instead of an actual machine. If a simulator is used, debugging can be performed in a virtual device environment.

  If an unexpected failure occurs during debugging using the simulator, do the following: In other words, since the actual device of the embedded device does not have an internal storage medium, check the log (FW log) output to the TTY (Tele-TYpewriter) console for debugging so that the FW can check the operation status by itself. , Perform motion analysis. In recent years, internal information of HWs emulated by using a simulator is also stored in a log (HW log) and used for analysis of FW defects.

  By the way, in debugging, when analyzing log data, the easier it is to analyze log data, the shorter the time required for debugging. As described above, there are the following techniques for improving the efficiency of log data analysis.

  As the first technique, there is the following technique. First, log data including a keyword and a reception time for individually identifying a synchronization message is generated by the first and second system visualization processing devices arranged in different segments, and the first system visualization processing is performed from the second system visualization processing device. Send log data to the device. The first system visualization processing device corrects the reception time of log data of other messages according to the difference in reception time of log data including the same identification information. If the log of duplicate messages is deleted and then all log data is sorted by reception time, the same log data as usual can be obtained. This makes it possible to visualize transactions in the analysis target system even when the analysis target system is separated into a plurality of segments and some messages are transmitted only within one segment.

  As the second technique, there is the following technique. The log output device outputs a log file including log information and data structure information of the log information. The log conversion device converts the log information into standard log information having a specific data structure based on the log information included in the log file acquired from the log output device and the data structure information of the log information. Thereby, even if the log file includes a plurality of types of log information having different data structures, the log analysis work can be performed efficiently.

  As a third technique, there is the following technique. Each time series data stored in a different file is divided into windows for each file and displayed in a scrollable manner by the window display processing unit. When the user selects one of the windows and scrolls, the scroll processing means adjusts the date / time data of the time series data at the top of the other window so that the date / time data at the top of the other window matches the date / time data of the other window. Scroll the window. Thereafter, the synchronized display processing unit displays the time-series data in the scrolled windows so that the time-series data having the same date and time data are arranged on the screen. Thereby, each stored data of a plurality of time-series data files having enormous time-series data such as log files can be displayed so as to be easily compared with each other. For this reason, it is possible to efficiently perform evaluation / confirmation between data of a plurality of log files.

JP 2011-1544489 A JP 2011-39834 A Japanese Patent Application Laid-Open No. 2001-265311

  In the simulator, the FW log is output character by character (character device), whereas the HW log is output line by line (block device). For this reason, when the FW log and the HW log are output to the same storage location, the HW log information enters between one character of the FW log, and the FW log and the HW log are mixed.

  Also, it is difficult to determine the temporal and proximate relationship between the operation of firmware and hardware for the following reasons. That is, the time recognized by the firmware is the virtual time operating on the simulator. On the other hand, the time recognized by the hardware is the real time on the host where the simulator is operating. As described above, since the time axes recognized by the firmware and the hardware are different, it is not easy to determine the temporal relationship between the operations of the firmware and the hardware.

  Further, since none of the first to third technologies is a technology for integrating logs of different time axes, it is impossible to determine a temporal relationship between firmware and hardware operations.

  As one aspect, the present invention provides a technique for outputting a log in which a time series of firmware and hardware operations is clarified.

  As one aspect, the simulator apparatus according to the present invention includes an execution unit, a first virtual device, a second virtual device, and an integration unit. The execution unit emulates a firmware instruction, acquires time information related to the actual time according to the input / output instruction from the firmware, adds the time information to the input / output instruction, and executes the input / output instruction. The first virtual device virtually performs the operation of the first device, and the first operation information and time output in the first output format according to the execution of the input / output instruction to which the time information is added. The first operation history information associated with the information is output. The second virtual device virtually performs the operation of the second device, and outputs the second operation information and time output in the second output format in response to the execution of the input / output command to which the time information is added. The second operation history information associated with the information is output. The integration unit integrates the first operation history information and the second operation history information based on the time information, and the operation history information is obtained by arranging the first operation information and the second operation information in time series. Is output.

  According to one aspect of the present invention, it is possible to output a log that clarifies the time series of firmware and hardware operations.

An example of the simulator apparatus in this embodiment is shown. 1 shows a configuration of a host device in the present embodiment. An example of HW log information and FW log information in the present embodiment is shown. An example of the merge log in this embodiment is shown. The processing flow about instruction execution of the virtual CPU in this embodiment is shown. The processing flow of the addition part in this embodiment is shown. 2 shows a processing flow of a virtual I / O device (virtual serial device) in the present embodiment. 5 shows a processing flow of a virtual I / O device (other than a virtual serial device) in the present embodiment. The processing flow of the log production | generation part 21 in this embodiment is shown. The processing flow of the merge part in this embodiment is shown. It is a block diagram of a hardware environment of a computer that executes a program according to the present embodiment.

  In the simulator, an FW log is output outside a machine (host) in which a server, a personal computer (PC) or the like is operating. In the case of a simulator, an FW log and an HW log are output on the host. However, the output destinations of the FW log and the HW log are different for the following reasons. When both the FW log and the HW log are output at the same location, the FW log is output character by character (character device), whereas the HW log is output line by line (block device). For this reason, as a result of the HW log information being inserted between one character of the FW log, the FW log and the HW log are mixed, making it difficult to read as meaningful information.

  As described above, since the FW log and the HW log are output separately, it is not possible to know the order of operation of the firmware and hardware and the time ahead of the operation, and it takes time to analyze the malfunction of the firmware. For example, if the firmware fails to register an interrupt handler, the following can be considered. That is, it is possible to discriminate the timing at which the CPU performs the interrupt processing and the timing at which the firmware interrupt handler operates from the HW log (log in which the CPU performed interrupt processing) and the FW log (interrupt handler execution log). Can not. As a result, even if the log is referred to, it cannot be easily determined whether the interrupt handler corresponding to the vector number that is the number indicating the cause of the interrupt is operating correctly.

Therefore, for example, the following method can be considered in order to obtain the temporal and proximate relationship between the firmware and hardware operations from the FW log and the HW log.
(I) Firmware and hardware add time information to each log, and merge the FW log and HW log to which the time information is added.
(Ii) When outputting the FW log and the HW log, time information is acquired from the common time axis and added to the FW log and the HW log.
(Iii) The FW log is also output line by line based on the line feed character code, and the FW log and the HW log are output to the same place. In other words, the FW log is temporarily held in the buffer until the line feed character code is output, and the FW logs held in the buffer are collectively output in response to the line feed character code.

However, the methods (i) to (iii) have the following problems.
When the time information is added to the FW log and the HW log for merging (in the case of (i) above), the time recognized by the firmware is the virtual time operating on the simulator. On the other hand, the time recognized by the hardware is the real time on the host where the simulator is operating.

  Using the virtual time, the operation of the firmware may be checked on the simulator by changing the speed or changing the date and time. For this reason, the recognition time differs between the firmware and the hardware, and it is impossible to determine the temporal relationship between the operations of the firmware and the hardware simply by adding the time information.

  Next, when outputting the FW log and the HW log, when acquiring and adding time information from the common time axis (in the case of (ii) above), the FW log information is received from the virtual serial device, and the real time information It is conceivable to add a configuration for acquiring and adding to the FW log information. Here, the virtual serial device is a virtual device for outputting information serially to a console terminal, for example. However, when such a configuration is used, the timing at which the virtual serial device operates due to the occurrence of an interrupt or the like may be significantly different from the timing at which the added mechanism acquires real time information. For this reason, in the configuration in which processing for obtaining time information from the time axis common to the HW log is added when the FW log is output, it is not possible to obtain an accurate relationship between the firmware and hardware in terms of temporal operation.

  Also, if the FW log is output line by line based on the line feed character code, and the FW log and the HW log are output to the same place (in the case of (iii) above), the order of the operation of the firmware and hardware should be grasped. Can do. In other words, the FW log is temporarily held in the buffer until the line feed character code is output, and the FW log held in the buffer is output in a batch triggered by the line feed character code. If the time until the character code is output is short, there is no problem.

  However, if it takes time to output the FW log, check what operation has been performed in the hardware from the time when the FW log started to be held in the buffer until the batch output is completed. I can't. Therefore, it is impossible to analyze a case in which a problem occurs when a specific HW device is operating during FW log output.

  Therefore, in this embodiment, real time information acquired at the same timing (timing at which an I / O operation has occurred from the virtual CPU to each virtual device) is added to each of the FW log and the HW log from the common time axis. The FW log and the HW log are merged in an easy-to-read manner according to the time series.

  FIG. 1 shows an example of a simulator device in the present embodiment. The simulator device 1 includes an execution unit 2, a first virtual device 3, a second virtual device 4, and an integration unit 5.

  The execution unit 2 emulates a firmware instruction, acquires time information related to the actual time according to the input / output instruction from the firmware, adds the time information to the input / output instruction, and executes the input / output instruction. An example of the execution unit 2 is the addition unit 16.

  The first virtual device 3 virtually performs the operation of the first device, and the first operation information output in the first output format in response to the execution of the input / output command to which the time information is added Correlate with time information and output.

  The second virtual device 4 virtually performs the operation of the second device, and the second operation information output in the second output format in response to the execution of the input / output command to which the time information is added. Correlate with time information and output.

  The integration unit 5 outputs operation history information in which the first operation information and the second operation information are arranged in time series based on the time information. An example of the integration unit 5 is a merge unit 24.

  The first virtual device or the second virtual device acquires the time information after executing the operation, and outputs the acquired time information in association with the operation information indicating the operation result after the execution. Further, the first virtual device outputs the first operation information in units of characters. The second virtual device is a virtual device other than the first virtual device, and outputs the second operation information collectively. An example of the first virtual device 3 is a virtual serial device 17. Examples of the second virtual device 4 include virtual I / O devices such as the virtual LAN 18, the virtual timer 19, and the virtual interrupt controller 20.

  With this configuration, the time series of firmware and hardware operations are clarified, and log information necessary for efficient failure analysis can be collected.

  FIG. 2 shows the configuration of the host device in this embodiment. A host device (hereinafter referred to as “host”) 11 is connected to a console terminal 27. The console terminal is, for example, a TTY console terminal. On the host 11, the simulator 12 is activated. The timer 26 is a function of an OS (Operating System) activated on the host 11 and manages real time.

  The simulator 12 emulates a firmware (FW) 14 instruction. The simulator 12 includes a virtual memory 13, firmware (FW) 14, virtual CPU 15, addition unit 16, virtual serial device 17, virtual LAN 18, virtual timer 19, virtual interrupt controller 20, log generation unit 21, and merge unit 24.

  The FW 14 operates by being expanded in the virtual memory 13. A virtual CPU (Central Processing Unit) 15 processes various interrupts.

  Virtual I / O devices such as a virtual local area network (LAN) 18, a virtual timer 19, and a virtual interrupt controller 20 are various I / O devices according to input / output (I / O) commands issued by the FW 14. Simulate the action. The virtual serial device 17 simulates a TTY interface for displaying the operation status information of the FW 14. The virtual LAN 18 simulates a LAN interface for connecting to a LAN so that it can communicate with an external device. The virtual timer 19 measures and manages the virtual time in the simulator 12. When an interrupt factor occurs in the device inside the simulator 12, the virtual interrupt controller 20 determines the interrupt factor, determines the priority of the interrupt factor, and notifies the virtual CPU 15 of the interrupt request.

  When the instruction decoded by the virtual CPU 15 is an I / O instruction for each virtual I / O device, the adding unit 16 obtains the actual time at that time from the timer 26 and uses the obtained actual time as a time stamp. It is added to the I / O instruction. Then, the adding unit 16 executes the I / O instruction.

  When the virtual I / O device is a virtual serial device, the log generation unit 21 stores and accumulates the result of the I / O operation of each virtual I / O device as FW log information 23 in the memory. Further, when the virtual I / O device is a device other than the virtual serial device, the log generation unit 21 stores / accumulates the result of the I / O operation of each I / O device as HW log information 22 in the memory. To do. The log generation unit 21 may be included in the function of the virtual I / O device depending on the specification.

  The merge unit 24 reads out the stored / accumulated HW log information 22 and FW log information 23 from the memory. For the FW log information 23, the merging unit 24 sets the first received character (the character received first after the start of operation or the character received next to the line feed character code) as the start character, and the “line feed character code”. Judged as the last character. The merge unit 24 handles a character string from the start character to the end character as one piece of FW log information. The merging unit 24 compares the real time added to the HW log information 22 with the real time added to the start character of the FW log information 23 so that each log information is arranged in parallel along the real time axis. To process.

  The merging unit 24 arranges the HW log information 22 having a real time between the real time of a specific character in the FW log information 23 and the real time of the next character between them. The merge log 25 is created by merging the log information.

  Thereby, the host 11 on which the simulator 12 operates outputs target system log information (serial output) and simulator system log information in time series in the order of occurrence. This makes it possible to clarify the relative relationship between the occurrence times of the two log information. Here, the target system log information represents log information output by the target system (device to be verified) to which the time managed by the target system is given. The simulator system log information represents log information collected by the simulator apparatus to which a time managed by the simulator system is given.

  FIG. 3 shows an example of HW log information and FW log information in the present embodiment. The HW log information 22 includes data items of “HW log time” 22a and “HW log” 22b. The “HW log time” 22a indicates the time when the HW log is generated. “HW log” 22b indicates the contents of the HW log. For example, the HW log “DeviceB (Initialize start)” indicates that the initialization of the device B is started. For example, the HW log “DeviceC (Wait message)” indicates that the device C is waiting for a message.

  The FW log information 23 includes data items of “FW log time” 23 a and “FW log (character code)” 23 b. The “FW log time” 23a indicates the time when the FW log is generated. "FW log (character code)" 23b indicates the content (character code) of the FW log.

  FIG. 4 shows an example of the merge log in this embodiment. The merge log 25 includes data items of “time” 25a, “FW log” 25b, and “HW log” 25c. “Time” 25a indicates the time when the FW log or the HW log is generated. The “FW log” 25b indicates the contents of the FW log. The log indicated by reference numeral 31 represents one FW log. For example, when outputting one FW log called “DeviceA Init”, as indicated by reference numeral 32 in the line before the start time corresponding to the FW log to be output in the “FW log” 25b, All characters from the start character to the end character are output. The next and subsequent lines are FW logs for each time as indicated by reference numeral 33. In the example of FIG. 4, the characters are output so as to be positioned below the character corresponding to the character included in the log indicated by the reference numeral 31 for easy viewing. The “HW log” 22b indicates the contents of the HW log at the time output at the “time” 25a.

Below, operation | movement of each part of the simulator 12 is demonstrated.
FIG. 5 shows a processing flow for instruction execution of the virtual CPU in the present embodiment. The virtual CPU 15 decodes the instruction from the firmware 14 (S1), and determines whether the decoded instruction is an I / O instruction (S2). If the decoded instruction is not an I / O instruction (“No” in S2), the virtual CPU 15 executes the instruction (S4). When the decoded instruction is an I / O instruction (“Yes” in S2), the virtual CPU 15 passes the operand of the I / O instruction to the adding unit 16 (S3). The operand of this I / O instruction includes information on the I / O port number, the value to be written, and the storage location of the read value.

  FIG. 6 shows a processing flow of the adding unit in the present embodiment. When an I / O instruction from the virtual CPU 15 to various virtual I / O devices is generated, that is, when the decoded instruction is an I / O instruction, the adding unit 16 receives an operand of the I / O instruction from the virtual CPU 15. Then do the following:

  First, the adding unit 16 acquires real time information from the timer 26 (S11). The adding unit 16 adds the acquired real time information to the operand of the I / O instruction received from the virtual CPU 15 (S12). Then, the adding unit 16 executes the I / O instruction based on the operand of the I / O instruction (S13).

  FIG. 7 shows a processing flow of the virtual I / O device (virtual serial device) in the present embodiment. When an I / O instruction is issued to the virtual serial device 17 due to the execution of the I / O instruction by the adding unit 16, the virtual serial device 17 acquires the real time information from the adding unit 16, and the I / O instruction is issued. The operation is performed based on the O operation command. Specifically, the virtual serial device 17 acquires a character code included in the I / O operation command and outputs a character corresponding to the character code to the console terminal 27 (S21). Then, the virtual serial device 17 passes the real time information, the character code, and the flag = 1 to the log generation unit 21 (S22). Here, the flag is information indicating whether or not the operation result of the virtual serial device. Flag = 1 indicates an operation result of the virtual serial device. Flag = 0 indicates an operation result of a virtual I / O device other than the virtual serial device.

  In the present embodiment, the virtual serial device 17 acquires real time information from the adding unit 16, but the present invention is not limited to this, and the virtual serial device 17 may acquire real time information from the timer 26.

  FIG. 8 shows a processing flow of a virtual I / O device (other than a virtual serial device) in the present embodiment. Examples of the virtual I / O device other than the virtual serial device include the virtual LAN 18, the virtual timer 19, and the virtual interrupt controller 20.

  When an I / O operation command for a virtual I / O device (other than a virtual serial device) is generated by the execution of the I / O command by the adding unit 16, the virtual I / O device receives the received real time information. And I / O operation information are passed to the log generation unit 21 (S31). Here, the I / O operation information includes the own device name and the processing content to be executed.

  The virtual I / O device (other than the virtual serial device) executes an I / O operation (S32). After executing the I / O operation, the virtual I / O device (other than the virtual serial device) acquires real time information from the timer 26 (S33). The virtual I / O device (other than the virtual serial device) passes the real time information, the I / O operation result, and the flag = 0 acquired in S33 to the log generation unit 21 (S34). The I / O operation result is notified as supplementary information.

  In S33 and S34, the real time information is acquired again, and the acquired real time and the I / O operation result are passed to the log generation unit 21 for the following reason. That is, a virtual I / O device other than a virtual serial device may communicate with other devices to request processing and wait for the processing result, and processing takes longer than that of a virtual serial device. This is because the log is acquired again later.

  FIG. 9 shows a processing flow of the log generation unit 21 in the present embodiment. The log generation unit 21 receives real time information, an I / O operation result, and a flag from each virtual I / O device (including a virtual serial device), and performs the following operation.

  Based on the flag, the log generation unit 21 determines whether the received I / O operation result is output from the virtual serial device (S41). When the received I / O operation result is output from the virtual serial device, that is, when flag = 1 (“Yes” in S41), the log generation unit 21 stores the actual FW log information 23 in the memory. Time information and a character code are output (stored) (S42, S43).

  When the received I / O operation result is not output from the virtual serial device, that is, when the flag = 0 (“No” in S41), the log generation unit 21 stores the virtual I / O operation results in the HW log information 22 in the memory. The real time information acquired from the I / O device is output. Further, the log generation unit 21 outputs (stores) the I / O operation information or the I / O operation result to the HW log information 22 in the memory (S44, S45).

  FIG. 10 shows a processing flow of the merge unit in the present embodiment. The merge unit 24 acquires the output time (FW time) of the first character of the FW log from the FW log information 23 stored in the memory (S51). The merge unit 24 acquires the output time (HW time) of the HW log from the HW log information 22 stored in the memory (S52).

  If the acquired HW time is earlier than the acquired FW time (“Yes” in S53), the merge unit 24 outputs the HW time to a new area on the memory (S54). Here, information output to a new area on the memory is referred to as a merge log 25. The merge unit 24 outputs an HW log corresponding to the HW time to the merge log 25 (S55). The merge unit 24 acquires the HW time of the next HW log from the HW log information 22 stored in the memory (S56), and returns to the process of S53.

  When the acquired HW time is the same as or later than the acquired FW time (“No” in S53), the merge unit 24 indicates that the character corresponding to the acquired FW time is the FW log. It is determined whether or not it is the first character (S57). The merge unit 24 determines that the character at the time acquired first in S51 and the character corresponding to the time acquired after the output of the line feed character in S63 described later is the first character of the FW log.

  When the character corresponding to the acquired FW time is the first character of the FW log (“Yes” in S57), the merging unit 24 stores the FW log (start character in the merge log 25 as indicated by reference numeral 32 in FIG. 4). To end character). (S58) Further, the merge unit 24 outputs the FW time and the FW log (one character) to the next line of the merge log (S60, S61).

  When the acquired character corresponding to the FW time is not the first character of the FW log (“No” in S57), the merge unit 24 determines whether the log output immediately before is the HW log (S59).

  When the log output immediately before is not the HW log (“No” in S59), the merge unit 24 outputs the FW log (one character) to the merge log (S61).

  When the character output to the merge log is not a line feed character (“No” in S62), the merge unit 24 acquires the FW time of the next character in the FW log from the FW log information 23 (S64).

  When the character output to the merge log is a line feed character (“Yes” in S62), the merge unit 24 acquires the FW time of the first character of the next FW log from the FW log information 23 (S64).

  FIG. 11 is a configuration block diagram of a hardware environment of a computer that executes a program according to the present embodiment. The computer 40 is the server 15. The computer 40 includes a CPU 42, ROM 43, RAM 46, communication I / F 44, storage device 47, output I / F 41, input I / F 45, reading device 48, bus 49, output device 51, and input device 52.

  Here, CPU indicates a central processing unit. ROM indicates a read-only memory. RAM indicates random access memory. I / F indicates an interface. A CPU 42, ROM 43, RAM 46, communication I / F 44, storage device 47, output I / F 41, input I / F 45, and reading device 48 are connected to the bus 49. The reading device 48 is a device that reads a portable recording medium. The output device 51 is connected to the output I / F 41. The input device 52 is connected to the input I / F 45.

  As the storage device 47, various types of storage devices such as a hard disk, a flash memory, and a magnetic disk can be used. The storage device 47 or the ROM 43 stores a program and data for performing processing according to the present embodiment.

  The CPU 42 reads out a program that realizes the processing described in the above embodiment, stored in the storage device 47 or the like, and executes the program.

  The program for realizing the processing described in the above embodiment may be stored in, for example, the storage device 47 via the communication network 50 and the communication I / F 44 from the program provider side. Moreover, the program which implement | achieves the process demonstrated by the said embodiment may be stored in the portable storage medium marketed and distribute | circulated. In this case, the portable storage medium may be set in the reading device 48 and the program read by the CPU 42 and executed. As the portable storage medium, various types of storage media such as a CD-ROM, a flexible disk, an optical disk, a magneto-optical disk, an IC card, and a USB memory device can be used. The program stored in such a storage medium is read by the reading device 48.

  As the input device 52, a keyboard, a mouse, an electronic camera, a web camera, a microphone, a scanner, a sensor, a tablet, or the like can be used. The output device 51 can be a display, a printer, a speaker, or the like. The network 50 may be a communication network such as the Internet, a LAN, a WAN, a dedicated line, a cable, and a wireless network.

  According to this embodiment, the time series of FW and HW operations are clarified, and the time for failure analysis can be shortened. For example, when a failure occurs, it is possible to know which HW was performing what operation at which timing of the FW. Therefore, it is possible to trace from the point where the failure has occurred to the location where the failure has occurred, and the time for failure analysis can be reduced.

  The present invention is not limited to the above-described embodiment, and various configurations or embodiments can be taken without departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1 Simulator apparatus 2 Execution part 3 1st virtual device 4 2nd virtual device 5 Integration part 11 Host 12 Simulator 13 Virtual memory 14 Firmware (FW)
15 Virtual CPU
16 Addition unit 17 Virtual serial device 18 Virtual LAN
19 Virtual Timer 20 Virtual Interrupt Controller 21 Log Generation Unit 22 HW Log Information 23 FW Log Information 24 Merge Unit 25 Merge Log 26 Timer 27 Console Terminal

Claims (5)

An execution unit that emulates a firmware instruction, acquires time information related to an actual time according to an input / output instruction from the firmware, adds the time information to the input / output instruction, and executes the input / output instruction; ,
The operation of the first device is virtually performed, and the first operation information output in the first output format is associated with the time information in accordance with the execution of the input / output instruction to which the time information is added. A first virtual device to output,
The operation of the second device is virtually performed, and the second operation information output in the second output format is associated with the time information in accordance with the execution of the input / output command to which the time information is added. A second virtual device to output,
An integration unit that outputs operation history information in which the first operation information and the second operation information are arranged in time series based on the time information;
A simulator device comprising: The first virtual device or the second virtual device acquires the time information after executing the operation, and associates and outputs the acquired time information with operation information indicating an operation result after the execution. The simulator device according to claim 1, wherein: The first virtual device outputs the first operation information in character units,
The simulator device according to claim 1, wherein the second virtual device is a virtual device other than the first virtual device, and outputs the second operation information in a lump. On the computer,
Emulate a firmware instruction, and according to an input / output instruction from the firmware, obtain time information about the actual time, add the time information to the input / output instruction, execute the input / output instruction,
First operation information output in a first output format in response to execution of the input / output command to which the time information is added to the first virtual device that virtually performs the operation of the first device, and the The time information is related and output,
Second operation information output in a second output format in response to execution of the input / output command to which the time information is added to the second virtual device that virtually performs the operation of the second device; The time information is related and output,
Based on the time information, the operation history information in which the first operation information and the second operation information are arranged in time series is output.
A program characterized by causing processing to be executed. Computer
Emulate a firmware instruction, and according to an input / output instruction from the firmware, obtain time information about the actual time, add the time information to the input / output instruction, execute the input / output instruction,
First operation information output in a first output format in response to execution of the input / output command to which the time information is added to the first virtual device that virtually performs the operation of the first device, and the The time information is related and output,
Second operation information output in a second output format in response to execution of the input / output command to which the time information is added to the second virtual device that virtually performs the operation of the second device; The time information is related and output,
Based on the time information, the operation history information in which the first operation information and the second operation information are arranged in time series is output.
And a log information processing method.

Images