JP2007328597A - Computer system, trace data storage method of computer system, and trace data storing program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To achieve both the maintenance of the time sequence of trace data having occurred in user mode software and kernel mode software and the reduction of an overhead applied to the trace of the user mode software. <P>SOLUTION: When user-side trace data are generated, a user-side trace control part 13 refers to user-side trace control information 7 memory-mapped to kernel-side trace control information 6 to determine whether or not it is necessary to store the trace data. When it is determined that it is necessary to store the trace data, the user-side trace control part 13 stores the user-side trace data into a kernel-side trace buffer 5 through a user-side trace output vicarious execution part 12 and a kernel-side trace output part 10. When kernel-side trace data are generated, a kernel-side trace control part 11 stores the kernel-side trace data into the kernel-side trace buffer 5 through the kernel-side trace output part 10. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a computer system for accumulating software trace data, a trace data accumulation method for the computer system, and a trace data accumulation program.

In a computer system (hereinafter referred to as a system) such as a general-purpose personal computer (PC) or an embedded device, trace data is accumulated in order to grasp the operation history of software of the entire system when a failure occurs. However, since the software operation slows down when the trace data is accumulated, a switch (accumulation necessity flag) indicating whether or not the trace data is accumulated is provided in the system, and the trace data accumulation function is disabled at the time of product release. (For example, Patent Document 1).
However, among the above systems, software operating on an OS (Operating System) having a memory protection function generally includes a user mode (also referred to as non-privileged mode) and a kernel mode (also referred to as privileged mode or supervisor mode). Operates in either mode. The user mode is a state where executable CPU (Central Processing Unit) instructions are restricted and the memory protection function is valid. Application software (hereinafter referred to as an application) operates in this user mode. In the user mode, a memory space is generally allocated for each application, and the memory is protected by the OS so that data of other applications operating in different memory spaces cannot be directly accessed. The kernel mode is a state in which there is no restriction on the CPU instruction described above, and the OS itself, the device driver, and the like operate in this kernel mode.
In such a system, the kernel mode side includes the above-described accumulation necessity flag and a trace buffer for accumulating trace data. By temporarily changing the operation mode from the user mode to the kernel mode via the OS, The user mode software trace data was accumulated using the accumulation necessity flag and the trace buffer on the kernel mode side.
In other systems, the accumulation necessity flag and the trace buffer are provided in both the user mode and the kernel mode, and the trace data is individually accumulated in the user mode and the kernel mode.
JP 2002-149444 A (2nd page, paragraph [0002])

However, in the former case, since the accumulation necessity flag is provided on the kernel mode side, every time the user mode software determines the validity / invalidity of the trace data accumulation function with reference to the accumulation necessity flag, the OS mode It is necessary to transition to kernel mode via a system call. For this reason, the former system has a problem that the overhead for storing traces of user mode software increases.
In the latter case, the user mode software and kernel mode software accumulate trace data in their respective trace buffers. Therefore, in order to grasp the operation history of the entire system, traces accumulated in both the user mode and kernel mode are stored. It is necessary to merge the data and refer to the trace data by rearranging the data in the order of occurrence. As a method of rearranging the trace data in the order of generation, it is conceivable to embed a counter value of a high-precision hardware timer installed in the system in the trace data. However, in embedded devices with many restrictions such as mounting cost and power consumption, there are many cases where the high-precision hardware timer is not installed or the high-precision hardware timer cannot always be used. The replacement method could not be used. In addition, when the hardware timer to be used has low accuracy, the user mode trace data and the kernel mode trace data indicate the same occurrence time, and the trace data may not be rearranged in the correct generation order. . That is, the latter system has a problem of high cost and high power consumption in order to obtain time-series trace data.

The present invention has been made in order to solve the above-described problems in a computer system that does not include a special hardware device for maintaining time series of individual operation modes and software trace data. Is.
For example, the present invention realizes both maintaining a time series of trace data generated in both user mode software and kernel mode software and reducing overhead required for tracing of user mode software. Objective.

  The computer system of the present invention is a user mode that operates in a user mode that uses a function provided by the system, based on kernel-side trace control information stored in a kernel-side memory that is used in a kernel mode that executes the function provided by the system. A computer system for storing user-side trace data indicating an operation history of a software program, used in a user mode, and storing a control information address indicating a storage area of the kernel-side trace control information in the kernel-side memory A kernel-side trace output unit for storing user-side trace data in the kernel-side memory, and the kernel-side trace stored in a storage area in the kernel-side memory indicated by the control information address stored in the user-side memory control A user-side trace control unit that determines whether or not user-side trace data needs to be stored based on the storage-necessity flag indicated by the referenced kernel-side trace control information, and the user-side trace control unit A user-side trace output proxy unit that calls the kernel-side trace output unit when it is determined that data accumulation is necessary, and the kernel-side trace output unit is configured to call the user-side trace output unit when called from the user-side trace output proxy unit. Data is stored in the kernel side memory.

  According to the present invention, for example, it is possible to both maintain a time series of trace data generated in both user mode software and kernel mode software, and reduce overhead required for tracing of user mode software. A computer system, a computer system trace data storage method, and a trace data storage program can be provided.

Embodiment 1 FIG.
In the first embodiment, in a computer system that accumulates kernel-mode trace data and user-mode trace data, a control information address indicating a storage area of kernel-side trace control information stored in the kernel-side memory is stored in the user-side memory. Thus, an embodiment is described in which it is determined whether or not the trace data needs to be accumulated in the user mode without changing to the kernel mode.

The kernel mode is one of operation modes of the computer system, also called a privilege mode or a supervisor mode, and a specific CPU instruction that is a function provided by the computer system is executed only in the kernel mode.
User mode is one of the computer system operation modes, also called non-privileged mode, which limits the CPU instructions that can be executed, and is used by memory used in kernel mode and other software programs operating in user mode. Access to the memory is limited. Therefore, when it is necessary to execute a restricted CPU instruction and access to the restricted memory, in the user mode, a system call is performed to transit to the kernel mode via the OS to access the restricted memory.

Below, the memory used in the kernel mode is the kernel side memory, the software program that operates in the kernel mode is the kernel mode software (or kernel mode software program), and the trace data that is generated in the kernel mode and indicates the operation history of the kernel mode software Kernel side trace data.
Also, the memory used in the user mode is the user side memory, the software program that operates in the user mode is the user mode software (or user mode software program), and the trace data that is generated in the user mode and indicates the operation history of the user mode software Use user-side trace data.
Further, the trace data including at least one of the kernel side trace data and the user side trace data is set as the system trace data.

The kernel side memory and the user side memory may be either real memory or virtual memory, and the storage areas of the real memory and virtual memory are also referred to as buffers and memory spaces.
Memory mapping is an example of processing for storing an address (control information address) indicating a specific storage area. In memory mapping, a virtual memory address and a real memory address are mainly stored in association with each other. By performing memory mapping, each application can access the real memory using the address of the virtual memory. In the memory mapping described below, an address indicating the storage area of the user-side trace control information 7 (see FIG. 1) and an address (control information address) indicating the storage area of the kernel-side trace control information 6 (see FIG. 1) are obtained. Assume that the data is stored in a storage area of a memory protection unit (MMU) of the system. Here, the address indicating the storage area of the user-side trace control information 7 is associated in the MMU storage area with the control information address indicating the storage area of the kernel-side trace control information 6 by the memory mapping. It is assumed that the control information address indicating the storage area of the kernel side trace control information 6 is included in the storage.
Further, software called an application or application program is an example of user mode software, and the OS is an example of kernel mode software.

A computer system is also simply referred to as a computer or system.
A software program is also simply referred to as software or a program.

FIG. 1 is a configuration diagram of a computer system 1 according to the first embodiment.
In FIG. 1, the computer system 1 also means a machine that has or uses the computer system 1, such as an embedded device.
The OS execution unit 2 executes an OS having functions such as a memory protection function.
The user mode software execution unit 3 executes user mode software that operates in a user mode such as application software.
The kernel mode software execution unit 4 executes kernel mode software that operates in a kernel mode, such as a device driver.
The kernel side trace buffer 5 (first kernel side memory) stores system trace data of the kernel side trace data output from the kernel mode software execution unit 4 and the user side trace data output from the user mode software execution unit 3. To do.
The kernel-side trace control information 6 includes information on whether or not to accumulate trace data (hereinafter referred to as an accumulation necessity flag), and is stored in the kernel-side memory 194 (second kernel-side memory).
User-side trace control information 7 indicates kernel-side trace control information 6 (control information address) that is memory-mapped in a user-mode memory space (user-side memory 192 [second user-side memory]).
The kernel side trace initialization unit 8 initializes the kernel side trace control information 6.
The trace control information map unit 9 is called from the kernel side trace initialization unit 8 and performs memory mapping of the kernel side trace control information 6 as user side trace control information 7.
The kernel side trace output unit 10 writes system trace data to the kernel side trace buffer 5.
The kernel-side trace control unit 11 refers to the kernel-side trace control information 6 and determines whether to call the kernel-side trace output unit 10.
The user side trace output proxy unit 12 calls the kernel side trace output unit 10 to write the user side trace data to the kernel side trace buffer 5.
The user-side trace control unit 13 refers to the user-side trace control information 7 and determines whether or not to call the user-side trace output proxy unit 12.

  The kernel mode software execution unit 4, the kernel side trace control unit 11, the kernel side trace output unit 10, the trace control information map unit 9, and the kernel side trace initialization unit 8, using the CPU 911, a kernel mode that is an OS extension unit It is executed as software or kernel mode software independent of the OS.

FIG. 2 is a diagram illustrating an example of hardware resources of the computer system 1 according to the first embodiment.
2, the computer system 1 includes a CPU 911 (also referred to as a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, or a processor) that executes a program. The CPU 911 is connected to the ROM 913, the RAM 914, the communication board 915, and the magnetic disk device 920 via the bus 912, and controls these hardware devices.
The RAM 914 is an example of a volatile memory. The storage medium of the ROM 913 and the magnetic disk device 920 is an example of a nonvolatile memory. These are examples of a storage device, a storage device, or a storage unit.
The communication board 915 is an example of an input / output device, an input / output device, or an input / output unit.

The communication board 915 is wired or wirelessly connected to a communication network such as a LAN (Local Area Network), the Internet, a WAN (Wide Area Network) such as ISDN, and a telephone line.
The magnetic disk device 920 stores an OS 921 (operating system), a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911 and the OS 921.

The program group 923 stores a program for executing a function described as “˜unit” in the embodiment. The program is read and executed by the CPU 911.
In the file group 924, in the embodiment, result data such as “determination result”, “calculation result of”, “processing result of” when executing the function of “to part”, “to part” The data to be passed between programs that execute the function “,” other information, data, signal values, variable values, and parameters are stored as items “˜file” and “˜database”. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. For example, user side trace control information 7, kernel side trace control information 6, system trace data, and the like are stored in the recording medium. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.
In addition, arrows in the flowcharts described in the embodiments mainly indicate input / output of data and signals, and the data and signal values are recorded in the memory of the RAM 914, the magnetic disk of the magnetic disk device 920, and other recording media. . Data and signal values are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In addition, what is described as “˜unit” in the embodiment may be “˜circuit”, “˜device”, “˜device”, “˜means”, and “˜step”, “˜”. “Procedure” and “˜Process” may be used. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs on a magnetic disk or other recording medium. The program is read by the CPU 911 and executed by the CPU 911. In other words, the trace data storage program causes the computer to function as “to part”. Alternatively, the procedure or method of “to part” is executed by a computer.

Next, the operation of the trace data storage method in the computer system 1 will be described.
The computer system 1 according to the first embodiment performs system initialization processing (see FIG. 3), kernel-side trace output processing (see FIG. 4), and user-side trace output processing (see FIG. 5) described below. Accumulate trace data.

FIG. 3 is a flowchart showing system initialization processing executed by the computer system 1 according to the first embodiment.
First, the operation of the initialization process of the system executed when the computer system 1 activates the trace function will be described below with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

The OS execution unit 2 calls the kernel side trace initialization unit 8 when the system is started or when the use of the trace function is started (S100).
When called from the OS execution unit 2, the kernel side trace initialization unit 8 initializes the kernel side trace control information 6 in the kernel side memory 194 (S101).
The kernel side trace initialization unit 8 also initializes the kernel side trace buffer 5 (S102).
Next, the kernel side trace initialization unit 8 calls the trace control information map unit 9 (S103).
The trace control information map unit 9 uses the memory protection unit provided in the system (usually the CPU 911) or the system call related to the MMU operation provided by the OS execution unit 2 to store the kernel side trace control information 6. Memory mapping is performed as user-side trace control information 7 in a user-mode memory space (user-side memory 192) (S104: control information address storage process).

  Note that the computer system 1 has a memory area that is commonly used by all user mode software when a plurality of user mode software is activated and a memory space is allocated for each user mode software. Kernel side trace control information 6 may be memory mapped. Further, the computer system 1 may perform memory mapping of the kernel side trace control information 6 on each memory space. When a new user mode memory space is generated by the OS execution unit 2, the trace control information map unit 9 is called each time, and the kernel side trace control information is also generated for the newly generated memory space. 6 is a memory mapping.

FIG. 4 is a flowchart showing kernel-side trace output processing executed by the computer system 1 according to the first embodiment.
Next, the operation when outputting kernel mode software trace data (kernel-side trace data) will be described with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

The kernel mode software execution unit 4 calls the kernel side trace control unit 11 in order to output the kernel side trace data generated during the execution of the kernel mode software (S111).
The kernel-side trace control unit 11 determines whether or not kernel-side trace data needs to be stored with reference to the storage necessity flag included in the kernel-side trace control information 6 (S112: kernel-side trace control processing).
When it is determined that the kernel side trace data is to be accumulated, the kernel side trace control unit 11 calls the kernel side trace output unit 10 (S113).
The kernel side trace output unit 10 writes the kernel side trace data to the kernel side trace buffer 5, and the kernel mode software execution unit 4 ends the kernel side trace output process. The kernel-side trace output unit 10 writes the kernel-side trace data after the system trace data that has been written in the kernel-side trace buffer 5 to secure a time series of the system trace data (S114: kernel-side trace output) processing).
If it is determined in S112 that the kernel side trace data is not accumulated, the kernel side trace control unit 11 returns the process to the kernel mode software execution unit 4 that is the caller, and the kernel mode software execution unit 4 performs the kernel side trace output process. finish.

FIG. 5 is a flowchart showing user-side trace output processing executed by the computer system 1 according to the first embodiment.
Next, the operation when outputting the trace data (user side trace data) of the user mode software will be described with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

The user mode software execution unit 3 calls the user side trace control unit 13 to output user side trace data generated during the execution of the user mode software (S121).
The user-side trace control unit 13 refers to the user-side trace control information 7 in the user-side memory 192 to set the accumulation necessity flag included in the kernel-side trace control information 6 that is memory-mapped to the user-side trace control information 7. refer. Then, the user side trace control unit 13 determines whether or not the user side trace data needs to be accumulated based on the accumulation necessity flag (S122: user side trace control process).
When it is determined that user-side trace data is to be accumulated, the user-side trace control unit 13 calls the user-side trace output proxy unit 12 (S123).
The user side trace output proxy unit 12 calls the kernel side trace output unit 10 via the OS execution unit 2 in order to write the user side trace data to the kernel side trace buffer 5 (S124: user side trace output proxy process).
Then, the kernel side trace output unit 10 writes the user side trace data to the kernel side trace buffer 5, and the user mode software execution unit 3 ends the user side trace output process. The kernel-side trace output unit 10 writes the user-side trace data after the system trace data already written in the kernel-side trace buffer 5 to secure the time series of the system trace data (S125: user-side trace output) processing).
If it is determined in S122 that the user side trace data is not accumulated, the user side trace control unit 13 returns the process to the user mode software execution unit 3 that is the caller, and the user mode software execution unit 3 performs the user side trace output process. finish.

In the present embodiment, the system trace data storage method including the following means has been described.
(A) User mode in which kernel-side trace control information 6 including an accumulation necessity flag indicating whether or not to accumulate trace data is provided in the kernel mode side for operating kernel mode software and an operating system. A trace control information map unit 9 that performs memory mapping on a user-side memory 192 that is a memory space that can be directly accessed by software.
(B) A user-side trace control unit 13 that directly refers to the user-side trace control information 7 memory-mapped by the trace control information map unit 9 and determines whether to accumulate user-side trace data.
(C) User-side trace output proxy that is called when the user-side trace control unit 13 determines that accumulation is necessary and calls the kernel-side trace output unit 10 to write user-side trace data to the kernel-side trace buffer 5 Part 12.

As described above, according to the present embodiment, the time series of the system trace data is maintained by writing the trace data of both the user mode software and the kernel mode software in the only kernel side trace buffer 5 in the system in the order of generation. can do.
In the present embodiment, the kernel-side trace control information 6 is memory-mapped to the user-side trace control information 7 so that the accumulation necessity flag included in the kernel-side trace control information 6 can be directly referred to from the user mode. . This eliminates the need to transition from the user mode to the kernel mode in order to determine whether or not the user-side trace data needs to be accumulated, thereby reducing the overhead.
Further, in this embodiment, even when a plurality of user mode softwares are operating, it is necessary to store system trace data for all user mode softwares by simply rewriting the storage necessity flag in the kernel side trace control information 6. No can be changed.

Embodiment 2. FIG.
In the first embodiment described above, an embodiment in which the kernel-side trace control information 6 is memory-mapped to the user-side trace control information 7 by the trace control information map unit 9 is described. However, in the second embodiment, memory mapping is not used. The embodiment of copying the contents of the kernel side trace control information 6 to the user side trace control information 7 will be described.
Hereinafter, items different from the first embodiment will be described, and items not described are the same as those of the first embodiment.

FIG. 6 is a configuration diagram of the computer system 1 according to the second embodiment.
The same reference numerals as those in FIG. 1 denote the same or corresponding parts.

In FIG. 6, the trace control information address table 14 has one or more memory addresses of the user side trace control information 7 and is stored in the kernel side memory 195.
The trace control information copying unit 15 copies the kernel side trace control information 6 to the user side trace control information 7 based on the trace control information address table 14.
The trace control information changing unit 16 has a function of changing the kernel side trace control information 6 and a function of notifying the trace control information copying unit 15 that the kernel side trace control information 6 has been changed.
The trace control information address registration unit 17 registers the memory address of the user side trace control information 7 in the trace control information address table 14.
The user side trace initialization unit 18 is executed before the user mode software execution unit 3 calls the user side trace control unit 13.

  The trace control information copying unit 15, the trace control information changing unit 16, and the trace control information address registering unit 17 are executed using the CPU 911 as kernel mode software that is an OS expansion unit or as kernel mode software independent of the OS. .

Next, the operation of the trace data storage method in the computer system 1 will be described.
First, an operation of a system initialization process executed when the computer system 1 starts the trace function will be described. The computer system 1 initializes the system by executing a kernel mode initialization process (see FIG. 7) and a user mode software initialization process (see FIG. 8) described below.

FIG. 7 is a flowchart illustrating kernel mode initialization processing executed by the computer system 1 according to the second embodiment.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

The OS execution unit 2 calls the kernel side trace initialization unit 8 when the system is started or when the use of the trace function is started (S200).
When called from the OS execution unit 2, the kernel side trace initialization unit 8 initializes the kernel side trace control information 6 (S201).
The kernel side trace initialization unit 8 also initializes the kernel side trace buffer 5 (S202).
Further, the kernel side trace initialization unit 8 also initializes the trace control information address table 14 (S203).

FIG. 8 is a flowchart showing user mode software initialization processing executed by the computer system 1 according to the second embodiment.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

When starting the accumulation of user side trace data, the user mode software execution unit 3 calls the user side trace initialization unit 18 once before calling the user side trace control unit 13 (S211).
The user-side trace initialization unit 18 secures the memory used for the user-side trace control information 7 in the user-side memory 192 for each user mode software being operated, and the user-side trace control information 7 in the secured memory. Is initialized (S212).
Next, the user side trace initialization unit 18 notifies the trace control information address registration unit 17 of the memory addresses of all user side trace control information 7 via the OS execution unit 2 (S213).
The trace control information address registration unit 17 adds the notified memory address of the user side trace control information 7 to the trace control information address table 14 (S214).
Next, the trace control information address registration unit 17 calls the trace control information copying unit 15 (S215).
The trace control information copying unit 15 refers to the trace control information address table 14 (S216).
Then, the trace control information copying unit 15 copies the kernel side trace control information 6 to the user side trace control information 7 for all the memory addresses registered in the trace control information address table 14 (S217: user side trace control information). Amnestic processing).

When the user mode software is terminated, the user mode software execution unit 3 releases the memory used for the user side trace control information 7 via the user side trace initialization unit 18, and the trace control information address registration unit. The memory address of the user side trace control information 7 registered in the trace control information address table 14 via 17 is deleted.
Further, when the user mode software is newly activated, the computer system 1 performs the above-described processing (S211 to S217) for the newly activated user mode software.

  The operation (kernel-side trace output processing) at the time of outputting the trace data of the kernel mode software is the same as that of the first embodiment (FIG. 4), and thus the description thereof is omitted.

  Since the operation (user side trace output processing) when outputting the trace data of the user mode software is the same as that of the first embodiment (FIG. 5), the description is omitted.

FIG. 9 is a flowchart showing user side trace control information update processing executed by the computer system 1 according to the second embodiment.
Next, a change in necessity of accumulating system trace data during execution of user mode software will be described with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

When changing whether or not to accumulate system trace data, the kernel mode software execution unit 4 calls the kernel side trace control unit 11 (S221).
The kernel side trace control unit 11 calls the trace control information change unit 16 (S222).
The trace control information changing unit 16 rewrites the system trace data accumulation necessity flag of the kernel side trace control information 6 (S223).
Next, the trace control information changing unit 16 calls the trace control information copying unit 15 (S224).
The trace control information copying unit 15 refers to the trace control information address table 14 (S225).
Then, the trace control information copying unit 15 copies the kernel side trace control information 6 to the user side trace control information 7 for all the memory addresses registered in the trace control information address table 14 (S226: Trace control information copy processing). ).

In the present embodiment, the system trace data storage method including the following means has been described.
(A) The trace control information including the accumulation necessity flag is secured and initialized in the user side memory 192 which is a memory space in the user mode, and the memory address of the user side memory 192 is notified to the trace control information address registration unit 17. A user-side trace initialization unit 18 for
(B) A user-side trace control unit 13 that directly refers to the user-side trace control information 7 secured and initialized by the user-side trace initialization unit 18 and determines whether to accumulate user-side trace data.
(C) User-side trace output proxy that is called when the user-side trace control unit 13 determines that accumulation is necessary and calls the kernel-side trace output unit 10 to write user-side trace data to the kernel-side trace buffer 5 Part 12.
(D) A trace control information address registration unit 17 that registers the memory address of the user side trace control information 7 notified from the user side trace initialization unit 18 in the trace control information address table 14.
(E) A trace control information changing unit 16 that has a function of changing the kernel-side trace control information 6 and notifies the trace control information copying unit 15 of the change.
(F) Called when the trace control information address table 14 is changed by the trace control information address registration unit 17 or when the kernel side trace control information 6 is changed by the trace control information change unit 16, and the kernel side trace control information is called. A trace control information copying unit 15 for copying 6 to the memory address destination memory described in the trace control information address table 14;

As described above, according to the present embodiment, the time series of the system trace data is maintained by writing the trace data of both the user mode software and the kernel mode software in the only kernel side trace buffer 5 in the system in the order of generation. can do.
In the present embodiment, the kernel side trace control information 6 is copied to the user side trace control information 7 so that the accumulation flag included in the kernel side trace control information 6 can be directly referred to from the user mode. As a result, the user mode is used to determine whether or not the user-side trace data needs to be stored even when there is a problem with the OS when the MMU is directly operated, or when the OS does not provide a system call related to the MMU operation. It is no longer necessary to make a transition from the kernel mode to the kernel mode, and the overhead can be reduced.
In this embodiment, user-side trace data can also be accumulated in time series for newly operated user mode software, and the necessity of accumulating system trace data can be changed during the operation of user mode software. Can do.

Embodiment 3 FIG.
In the first embodiment described above, the embodiment has been described in which the time series of the system trace data is maintained by only including the kernel side trace buffer 5 as an area for storing the kernel side trace data and the user side trace data. In the third embodiment, a kernel trace buffer 5 and one user trace buffer are provided to maintain a time series of system trace data.
Hereinafter, items different from the first embodiment will be described, and items not described are the same as those of the first embodiment.

FIG. 10 is a configuration diagram of the computer system 1 according to the third embodiment.
1 and 6 denote the same or corresponding parts.

In FIG. 10, the user side trace buffer 19 (first user side memory) stores user side trace data output from the user mode software execution unit 3.
The user side trace output unit 20 writes the user side trace data to the user side trace buffer 19.
The trace data moving unit 21 acquires user side trace data from the user side trace buffer 19 and writes the acquired user side trace data to the kernel side trace buffer 5.

  The trace data moving unit 21 is executed using the CPU 911 as kernel mode software that is an OS extension unit or kernel mode software independent of the OS.

Next, the operation of the trace data storage method in the computer system 1 will be described.
FIG. 11 is a flowchart illustrating system initialization processing executed by the computer system 1 according to the third embodiment.
First, the operation of the initialization process of the system executed when the computer system 1 activates the trace function will be described below with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

<Kernel mode initialization processing: S300 to S304>
The OS execution unit 2 calls the kernel side trace initialization unit 8 when the system is started or when the use of the trace function is started (S300).
When called from the OS execution unit 2, the kernel side trace initialization unit 8 initializes the kernel side trace control information 6 (S301).
The kernel side trace initialization unit 8 also initializes the kernel side trace buffer 5 (S302).
Next, the kernel side trace initialization unit 8 calls the trace control information map unit 9 (S303).
The trace control information map unit 9 uses the memory protection unit (MMU) included in the system (usually the CPU 911) or the system call related to the MMU operation provided by the OS execution unit 2 to perform kernel-side trace control. The information 6 is subjected to memory mapping in the user mode memory space (user side memory 192) (S304: control information address storage process).
<User mode initialization processing: S311 to S314>
Next, when starting the accumulation of the user side trace data, the user mode software execution unit 3 calls the user side trace initialization unit 18 once before calling the user side trace control unit 13 (S311).
The user side trace initialization unit 18 secures and initializes the memory of the user side trace buffer 19 (S312).
Next, the user side trace initialization unit 18 notifies the trace data moving unit 21 of the memory address of the user side trace buffer 19 via the OS execution unit 2 (S313).
The trace data moving unit 21 stores the notified memory address of the user side trace buffer 19 (S314).

FIG. 12 is a flowchart illustrating kernel-side trace output processing executed by the computer system 1 according to the third embodiment.
Next, the operation for outputting the kernel mode software trace data (kernel-side trace data) will be described with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

The kernel mode software execution unit 4 calls the kernel side trace control unit 11 to output the kernel side trace data generated during the execution of the kernel mode software (S321).
The kernel-side trace control unit 11 determines whether or not kernel-side trace data needs to be stored with reference to the storage necessity flag included in the kernel-side trace control information 6 (S322: kernel-side trace control processing).
When it is determined that the kernel side trace data is to be accumulated, the kernel side trace control unit 11 calls the trace data moving unit 21 (S323).
The trace data moving unit 21 acquires the user-side trace data accumulated at that time from the user-side trace buffer 19 indicated by the memory address stored in S314 (S324).
Then, the trace data moving unit 21 writes the acquired user side trace data to the kernel side trace buffer 5. The trace data moving unit 21 writes the user-side trace data after the system trace data already written in the kernel-side trace buffer 5 to secure the time series of the system trace data (S325: user-side trace data movement) processing).
Thereafter, the kernel side trace control unit 11 calls the kernel side trace output unit 10 (S326).
Then, the kernel side trace output unit 10 writes the kernel side trace data in the kernel side trace buffer 5, and the kernel mode software execution unit 4 ends the kernel side trace output process. The kernel-side trace output unit 10 writes the kernel-side trace data after the system trace data that has been written in the kernel-side trace buffer 5 to secure the time series of the system trace data (S327: kernel-side trace output) processing).
If it is determined in S322 that the kernel side trace data is not accumulated, the kernel side trace control unit 11 returns the process to the kernel mode software execution unit 4 that is the caller, and the kernel mode software execution unit 4 performs the kernel side trace output process. finish.

FIG. 13 is a flowchart illustrating user-side trace output processing executed by the computer system 1 according to the third embodiment.
Next, the operation when outputting the trace data (user side trace data) of the user mode software will be described with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

The user mode software execution unit 3 calls the user side trace control unit 13 in order to output user side trace data generated during the execution of the user mode software (S331).
The user-side trace control unit 13 determines whether or not user-side trace data needs to be stored with reference to the storage necessity flag included in the kernel-side trace control information 6 memory-mapped to the user-side trace control information 7 (S332: User side trace control processing).
When it is determined that user-side trace data is to be accumulated, the user-side trace control unit 13 calls the user-side trace output unit 20 (S333).
The user side trace output unit 20 writes the user side trace data in the user side trace buffer 19. The user-side trace output unit 20 writes user-side trace data after the user-side trace data already written in the user-side trace buffer 19 to secure a time series of user-side trace data (S334: user-side) Trace output processing).
In S332, when it is determined that the user side trace data is not accumulated, the user side trace control unit 13 returns the process to the user mode software execution unit 3 that is the caller, and the user mode software execution unit 3 performs the user side trace output process. finish.

When the user mode software is terminated, the user mode software execution unit 3 releases the user side trace buffer 19 via the user side trace initialization unit 18 and is stored in the trace data moving unit 21. The memory address of the user side trace buffer 19 is invalidated. Further, the user side trace initialization unit 18 notifies the trace data moving unit 21 via the OS execution unit 2 before releasing the user side trace buffer 19, thereby remaining the trace data remaining in the user side trace buffer 19. Can be moved to the kernel-side trace buffer 5.
In S325, when the memory address of the user side trace buffer 19 is not notified or invalid, the trace data moving unit 21 performs no processing.

  In the above description, the computer system 1 uses the user-side trace control information 7 obtained by mapping the kernel-side trace control information 6 in the same manner as in the first embodiment to determine whether or not the user-side trace data needs to be stored. Similarly to the second embodiment, the computer system 1 may use the user side trace control information 7 obtained by copying the kernel side trace control information 6.

In the present embodiment, the system trace data storage method including the following means has been described.
(A) A user-side trace initialization unit 18 that secures and initializes the user-side trace buffer 19 in a user-mode memory space and notifies the trace data moving unit 21 of the memory address of the user-side trace buffer 19.
(B) When called from the kernel mode software execution unit 4, the kernel side trace control unit 11 calls the kernel side trace output unit 10 after calling the trace data moving unit 21.
(C) Acquired accumulated user-side trace data from the user-side trace buffer 19 called from the kernel-side trace control unit 11 and notified in advance from the user-side trace initialization unit 18, and writes it to the kernel-side trace buffer 5 A trace data moving unit 21 for performing

As described above, according to the present embodiment, before the trace data of kernel mode software is written in the kernel side trace buffer 5, the user mode software trace data accumulated so far is written in the kernel side trace buffer 5. Thus, the time series of the system trace data can be maintained.
Further, in the present embodiment, it is not necessary to shift from the user mode to the kernel mode in order to determine whether or not the user side trace data needs to be accumulated, and the overhead can be reduced.
In this embodiment, while the kernel-side trace data is generated, the user-side trace data is accumulated in the user-side trace buffer 19 so that the user mode is changed to the kernel mode every time the user-side trace data is generated. This is unnecessary, and the overhead can be reduced.
Also, in this embodiment, when there is no more space in the user-side trace buffer 19, the user-side trace output unit 20 notifies the trace data moving unit 21 of the shortage of the user-side trace buffer 19 area. The trace data moving unit 21 moves the user side trace data from the user side trace buffer 19 to the kernel side trace buffer 5, thereby preventing the user side trace data from being unable to be written to the user side trace buffer 19 due to insufficient area. it can.

Embodiment 4 FIG.
In the above-described third embodiment, an embodiment in which one kernel-side trace buffer 5 and one user-side trace buffer 19 are provided as areas for accumulating system trace data has been described. An embodiment comprising a trace buffer 5 and one or more user side trace buffers is shown.
In the third embodiment, when the kernel-side trace data is generated, the user-side trace data stored in the user-side trace buffer 19 is moved to the kernel-side trace buffer 5 before the kernel-side trace data is stored. Thus, an embodiment for maintaining a time series of system trace data has been shown. In the fourth embodiment, at the time of transition from the user mode to the kernel mode, the user side trace data stored in the user side trace buffer 19 is moved to the kernel side trace buffer 5 before the generation of the kernel side trace data. Shows an embodiment for maintaining a time series of system trace data.
Hereinafter, items different from the first embodiment will be described, and items not described are the same as those of the first embodiment.

FIG. 14 is a configuration diagram of the computer system 1 according to the fourth embodiment.
1, 6, and 10 indicate the same or corresponding parts.

In FIG. 14, the trace buffer address table 23 has one or more memory addresses of the user side trace buffer 19 and is stored in the kernel side memory 196.
The trace buffer address registration unit 22 registers the memory address of the user side trace buffer 19 in the trace buffer address table 23.

  Using the CPU 911, the trace buffer address registration unit 22 is executed as kernel mode software that is an extension unit of the OS or kernel mode software independent of the OS.

Next, the operation of the trace data storage method in the computer system 1 will be described.
First, an operation of a system initialization process executed when the computer system 1 starts the trace function will be described. The computer system 1 initializes the system by executing a kernel mode initialization process (see FIG. 15) and a user mode software initialization process (see FIG. 16) described below.

FIG. 15 is a flowchart illustrating kernel mode initialization processing executed by the computer system 1 according to the fourth embodiment.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

The OS execution unit 2 calls the kernel side trace initialization unit 8 when the system is started or when the use of the trace function is started (S400).
When called from the OS execution unit 2, the kernel side trace initialization unit 8 initializes the kernel side trace control information 6 (S401).
The kernel side trace initialization unit 8 also initializes the kernel side trace buffer 5 (S402).
Further, the kernel side trace initialization unit 8 also initializes the trace buffer address table 23 (S403).

FIG. 16 is a flowchart illustrating user mode software initialization processing executed by the computer system 1 according to the fourth embodiment.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

When starting the accumulation of user side trace data, the user mode software execution unit 3 calls the user side trace initialization unit 18 once before calling the user side trace control unit 13 (S411).
The user-side trace initialization unit 18 secures and initializes the memory of the user-side trace buffer 19 for each user mode software being operated (S412).
Next, the user side trace initialization unit 18 notifies the trace buffer address registration unit 22 of the memory addresses of all the user side trace buffers 19 via the OS execution unit 2 (S413).
The trace buffer address registration unit 22 adds the notified memory address of the user side trace control information 7 to the trace buffer address table 23 (S414).

  The operation (kernel-side trace output processing) at the time of outputting the trace data of the kernel mode software is the same as that of the first embodiment (FIG. 4), and thus the description thereof is omitted.

  Since the operation (user side trace output processing) when outputting the trace data of the user mode software is the same as that of the third embodiment (FIG. 13), the description is omitted.

  That is, in the fourth embodiment, kernel-side trace data is accumulated in the kernel-side trace buffer 5, and user-side trace data is temporarily accumulated in the user-side trace buffer 19 for each user mode software.

FIG. 17 is a flowchart showing kernel-side trace data movement processing executed by the computer system 1 according to the fourth embodiment.
Next, the operation of the process of moving the user side trace data stored in the user side trace buffer 19 to the kernel side trace buffer 5 will be described with reference to FIG.
Each component of the computer system 1 described as “unit” executes the following processing using the CPU 911.

When the operation mode transitions from the user mode to the kernel mode, the OS execution unit 2 calls the trace data moving unit 21. As a trigger for the OS execution unit 2 to call the trace data moving unit 21, for example, when switching execution between user mode software (generally process switching), when issuing a system call from the user mode software execution unit 3, This includes the occurrence of an interrupt from the hardware. When called, the trace data moving unit 21 can identify a value that can identify the user mode software that has been operating until then, or the user side trace buffer 19 that corresponds to the user mode software that has been operated until then. For example, the process ID is notified from the OS execution unit 2 as a value (S421).
The trace data moving unit 21 refers to the trace buffer address table 23 based on the notification from the OS execution unit 2 and acquires the memory address of the user side trace buffer 19 corresponding to the user mode software that has been operating until then ( S422).
Next, the trace data moving unit 21 extracts the user side trace data of the user mode software stored at that time from the user side trace buffer 19 indicated by the acquired memory address (S423).
Then, the trace data moving unit 21 writes the extracted user side trace data into the kernel side trace buffer 5. The trace data moving unit 21 writes the user-side trace data after the system trace data already written in the kernel-side trace buffer 5 to secure the time series of the system trace data (S424: user-side trace data movement). processing).

That is, the computer system 1 according to the fourth embodiment stores the trace data of the user mode software before the process switching in the kernel side trace buffer 5 before the trace data is generated in the user mode software after the process switching. A time series of trace data between user mode software can be secured.
Further, the computer system 1 according to the fourth embodiment stores the user side trace data generated before the transition to the kernel mode in the kernel side trace buffer 5 before the trace data is generated in the kernel mode after the mode transition. The time series between the user side trace data and the kernel side trace data can be secured.

  When the user mode software is terminated, the user mode software execution unit 3 releases the user side trace buffer 19 via the user side trace initialization unit 18 and the trace buffer via the trace buffer address registration unit 22. It is assumed that the memory address of the user side trace buffer 19 registered in the address table 23 is deleted. Further, the user side trace initialization unit 18 notifies the trace data moving unit 21 via the OS execution unit 2 before releasing the user side trace buffer 19, thereby remaining the trace data remaining in the user side trace buffer 19. Can be moved to the kernel-side trace buffer 5.

  In the above description, the computer system 1 uses the user-side trace control information 7 obtained by mapping the kernel-side trace control information 6 in the same manner as in the first embodiment to determine whether or not the user-side trace data needs to be stored. Similarly to the second embodiment, the computer system 1 may use the user side trace control information 7 obtained by copying the kernel side trace control information 6.

As described above, according to the present embodiment, when the OS execution unit 2 makes a transition from the user mode to the kernel mode, the user mode software trace data accumulated so far is written into the kernel side trace buffer 5. The time series of system trace data can be maintained.
In this embodiment, it is not necessary to shift from user mode to kernel mode in order to determine whether or not user-side trace data needs to be stored for one or a plurality of user mode software, thereby reducing the overhead. be able to.
In the present embodiment, user-side trace data is accumulated in the kernel-side trace buffer 5 by accumulating user-side trace data in the kernel-side trace buffer 5 by using an opportunity to change from the user mode to the kernel mode. Therefore, it is not necessary to make a transition from the user mode to the kernel mode only for the purpose, and the overhead can be reduced.

In the present embodiment, the system trace data storage method including the following means has been described.
(A) A trace buffer address registration unit 22 that registers the memory address of the user side trace buffer 19 that has been secured and initialized by the user side trace initialization unit 18 in the trace buffer address table 23.
(B) The user side that has been stored in the user side trace buffer 19 of the user mode software that is called from the OS execution unit 2 and notified from the OS execution unit 2 among the user side trace buffers 19 described in the trace buffer address table 23 A trace data moving unit 21 that acquires trace data and writes the acquired user-side trace data to the kernel-side trace buffer 5.

1 is a configuration diagram of a computer system 1 according to Embodiment 1. FIG. FIG. 3 is a diagram illustrating an example of hardware resources of the computer system 1 according to the first embodiment. 3 is a flowchart showing system initialization processing executed by the computer system 1 according to the first embodiment. 3 is a flowchart showing kernel-side trace output processing executed by the computer system 1 according to the first embodiment. 5 is a flowchart showing user-side trace output processing executed by the computer system 1 according to the first embodiment. FIG. 3 is a configuration diagram of a computer system 1 according to a second embodiment. 9 is a flowchart showing kernel mode initialization processing executed by the computer system 1 according to the second embodiment. 9 is a flowchart illustrating user mode software initialization processing executed by the computer system 1 according to the second embodiment. 9 is a flowchart showing user side trace control information update processing executed by the computer system 1 according to the second embodiment. FIG. 6 is a configuration diagram of a computer system 1 according to a third embodiment. 10 is a flowchart showing system initialization processing executed by the computer system 1 according to the third embodiment. 10 is a flowchart showing kernel-side trace output processing executed by the computer system 1 according to the third embodiment. 10 is a flowchart showing user-side trace output processing executed by the computer system 1 according to the third embodiment. FIG. 6 is a configuration diagram of a computer system 1 according to a fourth embodiment. 10 is a flowchart showing kernel mode initialization processing executed by the computer system 1 according to the fourth embodiment. 15 is a flowchart showing user mode software initialization processing executed by the computer system 1 according to the fourth embodiment. 15 is a flowchart showing kernel-side trace data movement processing executed by the computer system 1 according to the fourth embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Computer system, 2 OS execution part, 3 User mode software execution part, 4 Kernel mode software execution part, 5 Kernel side trace buffer, 6 Kernel side trace control information, 7 User side trace control information, 8 Kernel side trace initialization part , 9 Trace control information map section, 10 Kernel side trace output section, 11 Kernel side trace control section, 12 User side trace output proxy section, 13 User side trace control section, 14 Trace control information address table, 15 Trace control information copy section , 16 Trace control information change unit, 17 Trace control information address registration unit, 18 User side trace initialization unit, 19 User side trace buffer, 20 User side trace output unit, 21 Trace data move unit, 22 Trace buffer add Register, 23 Trace buffer address table, 192 User side memory, 194, 195, 196 Kernel side memory, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 magnetic disk unit, 921 OS, 923 program Group, 924 file group.

Claims (12)

Indicates the operation history of the user mode software program that operates in the user mode that uses the function provided by the system, based on the kernel side trace control information stored in the kernel side memory that is used in the kernel mode that executes the function provided by the system. A computer system for storing user-side trace data;
A user side memory that is used in a user mode and stores a control information address indicating a storage area of the kernel side trace control information in the kernel side memory;
A kernel side trace output unit for storing user side trace data in the kernel side memory;
The kernel-side trace control information stored in the storage area in the kernel-side memory indicated by the control-information address stored in the user-side memory is referred to, and the accumulation necessity flag indicated by the referenced kernel-side trace control information is displayed. A user-side trace control unit that determines whether or not user-side trace data needs to be accumulated, and
A user-side trace output proxy unit that calls the kernel-side trace output unit when the user-side trace control unit determines that the user-side trace data needs to be accumulated;
The computer system wherein the kernel side trace output unit stores user side trace data in the kernel side memory when called from the user side trace output proxy unit. Indicates the operation history of the user mode software program that operates in the user mode that uses the function provided by the system, based on the kernel side trace control information stored in the kernel side memory that is used in the kernel mode that executes the function provided by the system. A computer system for storing user-side trace data;
A user-side memory that stores user-side trace control information that is used in user mode and that is a copy of the kernel-side trace control information stored in the kernel-side memory;
A kernel side trace output unit for storing user side trace data in the kernel side memory;
User-side trace control that refers to the user-side trace control information stored in the user-side memory and determines whether or not user-side trace data needs to be accumulated based on an accumulation necessity flag that is indicated by the referenced user-side trace control information And
A user-side trace output proxy unit that calls the kernel-side trace output unit when the user-side trace control unit determines that the user-side trace data needs to be accumulated;
The computer system wherein the kernel side trace output unit stores user side trace data in the kernel side memory when called from the user side trace output proxy unit. The computer system further includes:
The accumulation necessity indicated by the user side trace control information by copying the accumulation necessity flag indicated by the kernel side trace control information changed when the accumulation necessity flag indicated by the kernel side trace control information is changed. 3. The computer system according to claim 2, further comprising a trace control information copying unit for updating a flag. User showing the operation history of the kernel mode software program that operates in the kernel mode that executes the function provided by the system and the operation history of the user mode software program that operates in the user mode that uses the function provided by the system A computer system for storing side trace data,
A first kernel-side memory used in kernel mode and storing kernel-side trace data and user-side trace data;
A first user-side memory used in user mode and storing user-side trace data;
A user-side trace output unit for storing the user-side trace data generated when user-side trace data is generated in the first user-side memory;
A trace data moving unit that moves the user side trace data stored in the first user side memory by the user side trace output unit to the first kernel side memory when kernel side trace data is generated;
A kernel-side trace output unit for storing the kernel-side trace data generated when the kernel-side trace data is generated, after the user-side trace data moved by the trace data moving unit to the first kernel-side memory; A computer system comprising: User showing the operation history of the kernel mode software program that operates in the kernel mode that executes the function provided by the system and the operation history of the user mode software program that operates in the user mode that uses the function provided by the system A computer system for storing side trace data,
A first kernel-side memory used in kernel mode and storing kernel-side trace data and user-side trace data;
A first user-side memory used in user mode and storing user-side trace data;
A user-side trace output unit for storing the user-side trace data generated when user-side trace data is generated in the first user-side memory;
A trace data moving unit for moving the user side trace data stored in the first user side memory by the user side trace output unit to the first kernel side memory at the time of transition from the user mode to the kernel mode;
A kernel-side trace output unit for storing kernel-side trace data generated when kernel-side trace data is generated, after the user-side trace data moved by the trace data moving unit to the first kernel-side memory. A computer system characterized by that. The computer system further includes:
A second kernel-side memory that is used in the kernel mode and stores kernel-side trace control information indicating an accumulation necessity flag of user-side trace data;
A second user-side memory that is used in a user mode and stores a control information address indicating a storage area of the kernel-side trace control information in the second kernel-side memory;
The kernel-side trace control information stored in the storage area in the second kernel-side memory indicated by the control information address stored in the second user-side memory is referred to. A user-side trace control unit that determines whether or not user-side trace data needs to be accumulated based on the accumulation necessity flag shown,
The user side trace output unit
6. The user-side trace data is stored in the first user-side memory when the user-side trace control unit determines that user-side trace data needs to be stored. Computer system. The computer system further includes:
A second kernel-side memory that is used in the kernel mode and stores kernel-side trace control information indicating an accumulation necessity flag of user-side trace data;
A second user-side memory for storing user-side trace control information used in the user mode and copied from the kernel-side trace control information stored in the second kernel-side memory;
A user who refers to the user-side trace control information stored in the second user-side memory and determines whether or not user-side trace data needs to be accumulated based on an accumulation necessity flag indicated by the referenced user-side trace control information Side trace control unit,
The user side trace output unit
6. The user-side trace data is stored in the first user-side memory when the user-side trace control unit determines that user-side trace data needs to be stored. Computer system. Indicates the operation history of the user mode software program that operates in the user mode that uses the function provided by the system, based on the kernel side trace control information stored in the kernel side memory that is used in the kernel mode that executes the function provided by the system. A trace data accumulation method for a computer system for storing user side trace data,
A control information address storage process in which a user side memory used in the user mode stores a control information address indicating a storage area of the kernel side trace control information in the kernel side memory;
The user side trace control unit refers to the kernel side trace control information stored in the storage area in the kernel side memory indicated by the control information address stored in the user side memory, and the referenced kernel side trace control information is A user-side trace control process for determining whether or not user-side trace data needs to be accumulated based on an accumulation necessity flag shown;
A user side trace output proxy unit that calls the kernel side trace output unit when the user side trace control unit determines that the user side trace data needs to be stored; and
Trace data of a computer system for executing kernel-side trace output processing for storing user-side trace data in the kernel-side memory when a kernel-side trace output unit is called from the user-side trace output proxy unit Accumulation method. Indicates the operation history of the user mode software program that operates in the user mode that uses the function provided by the system, based on the kernel side trace control information stored in the kernel side memory that is used in the kernel mode that executes the function provided by the system. A trace data accumulation method for a computer system for storing user side trace data,
A user-side trace control information storage process for storing user-side trace control information obtained by copying the kernel-side trace control information stored in the kernel-side memory by a user-side memory used in the user mode;
The user-side trace control unit refers to the user-side trace control information stored in the user-side memory, and determines whether or not the user-side trace data needs to be accumulated based on the accumulation necessity flag indicated by the referenced user-side trace control information. User-side trace control processing to be determined;
A user side trace output proxy unit that calls the kernel side trace output unit when the user side trace control unit determines that the user side trace data needs to be stored; and
Trace data of a computer system for executing kernel-side trace output processing for storing user-side trace data in the kernel-side memory when a kernel-side trace output unit is called from the user-side trace output proxy unit Accumulation method. User showing the operation history of the kernel mode software program that operates in the kernel mode that executes the function provided by the system and the operation history of the user mode software program that operates in the user mode that uses the function provided by the system A trace data storage method of a computer system for storing side trace data,
A user-side trace output process in which the user-trace output unit stores the user-side trace data generated when the user-side trace data is generated in a first user-side memory;
Trace data moving process in which the user side trace output unit moves the user side trace data stored in the first user side memory to the first kernel side memory when the kernel side trace data is generated by the trace data moving unit When,
A kernel that stores the kernel-side trace data generated when kernel-side trace data is generated by the kernel-side trace output unit after the user-side trace data that the trace data moving unit has moved to the first kernel-side memory A trace data storage method for a computer system, characterized in that a side trace output process is executed. User showing the operation history of the kernel mode software program that operates in the kernel mode that executes the function provided by the system and the operation history of the user mode software program that operates in the user mode that uses the function provided by the system A trace data storage method of a computer system for storing side trace data,
A user side trace output process in which the user side trace output unit stores the user side trace data generated when the user side trace data is generated in a first user side memory; and
Trace data for moving the user-side trace data stored in the first user-side memory by the user-side trace output unit to the first kernel-side memory when the trace data moving unit makes a transition from the user mode to the kernel mode. Move processing,
The kernel side in which the kernel side trace output unit stores the kernel side trace data generated when the kernel side trace data is generated, after the user side trace data that the trace data moving unit has moved to the first kernel side memory. A trace data storage method for a computer system, characterized in that a trace output process is executed.   A trace data storage program for causing a computer system to execute the trace data storage method for a computer system according to any one of claims 8 to 11.

Images