JP6834838B2 - Computer boot method and computer - Google Patents

Description

The present invention relates to a technique for generating a memory dump.

For example, if a computer malfunctions, a memory dump may be taken to analyze the program.

Malfunctions may occur in the startup process of the OS (Operating System). Even in this case, if a memory dump can be taken, it will be useful for investigating the cause and considering countermeasures.

Specifically, the contents of the memory are recorded in a file by starting the dump generation program loaded in the memory at the timing when the memory dump is to be taken during the boot processing of the OS. That is, the condition is that the dump generator is loaded into the memory first.

However, since the dump generator is loaded in the OS boot process, it is not possible to take a memory dump at an early stage when the dump generator is not loaded yet.

Japanese Unexamined Patent Publication No. 2000-137630 Japanese Unexamined Patent Publication No. 2011-232986

An object of the present invention is, on the one hand, to enable memory dump processing to be performed at an early stage of operating system startup processing.

The computer boot method according to one aspect is (A) in the boot loader process, the program that performs the memory dump process is loaded into the memory, the load position of the program is passed to the operating system, and (B) the operating system is being booted. At any timing, the process of starting the program based on the load position is included.

On the one hand, the memory dump process can be performed at an early stage of the operating system boot process.

FIG. 1 is a diagram showing a conventional example of a dump generation sequence at the time of starting a computer. FIG. 2 is a diagram showing a state of loading the boot loader. FIG. 3 is a diagram showing a state of loading the OS. FIG. 4 is a diagram showing how the dump generator is loaded. FIG. 5 is a diagram showing an example in which a dump file cannot be generated in the prior art. FIG. 6 is a diagram showing a dump generation sequence according to the present embodiment. FIG. 7 is a diagram showing a state of loading the boot loader. FIG. 8 is a diagram showing how the dump generator is loaded. FIG. 9 is a diagram showing a state of loading the OS. FIG. 10 is a diagram showing a module configuration example of the boot loader. FIG. 11 is a diagram showing a processing flow of the boot loader. FIG. 12 is a diagram showing a processing flow of the boot loader. FIG. 13 is a diagram showing a processing flow of the boot loader. FIG. 14 is a diagram showing an example of an OS module configuration. FIG. 15 is a diagram showing a processing flow of the OS. FIG. 16 is a diagram showing a creation processing flow. FIG. 17 is a diagram showing a processing flow of an interrupt handler. FIG. 18 is a diagram showing an error handling processing flow. FIG. 19 is a diagram showing a processing flow of the dump generation program. FIG. 20 is a functional block diagram of the computer.

FIG. 1 shows a conventional example of a dump generation sequence at the time of starting a computer. When the power of the computer is turned on, the BIOS (Basic Input / Output System) 101 starts processing. BIOS101 first initializes the device (S111). Subsequently, as shown in FIG. 2, the BIOS 101 loads the boot loader 103 stored in the hard disk drive 201 into the main memory 203 (S113). Then, the BIOS 101 starts the boot loader 103 (S115).

At the time when OS 105 is installed, the dump generation program 107 shown in FIG. 2 does not exist. When the OS 105 is first started, the dump generation program 107 is created by the OS 105 and stored in the hard disk drive 201.

Returning to the description of FIG. When the boot loader 103 starts processing (S121), as shown in FIG. 3, the boot loader 103 loads the OS 105 stored in the hard disk drive 201 in a file format into the main memory 203 (S123). Then, the boot loader 103 boots the OS 105 (S125).

OS105 starts the startup process (S131). The startup process may be the initialization process of the OS 105 or the initial process of the OS 105. In the startup process, OS 105 prepares a file system (S133).

The OS 105 creates the dump generation program 107 when the dump generation program 107 does not exist, that is, at the time of the first startup after the OS 105 is installed (S135). On the other hand, the OS 105 does not create the dump generation program 107 when the dump generation program 107 exists, that is, when it is started for the second time or later.

As shown in FIG. 4, the OS 105 loads the dump generation program 107 stored in the hard disk drive 201 in a file format into the main memory 203 (S137).

When the OS 105 detects an error occurrence or an external interrupt after the dump generation program 107 is loaded (S139), the OS 105 starts the dump generation program 107 (S141).

The dump generation program 107 starts the dump generation process (S151), and generates a dump file in which the data collected from the main memory 203 is recorded (S153).

As described above, in the prior art, the dump generation program 107 is read by the file system of the OS 105 and loaded into the main memory 203. Then, the OS 105 can start the dump generation program 107 while the dump generation program 107 is loaded.

In the above-mentioned conventional technique, the dump generation program 107 is not loaded when the file system is not ready. As shown in FIG. 5, when the OS 105 does not prepare the file system, even if an error occurs or an external interrupt is detected (S501), the OS 105 cannot start the dump generation program 107. That is, the memory dump cannot be performed at an early stage of the startup process in OS105. The processing of S111 to S131 shown in FIG. 5 is the same as that of FIG.

In the present embodiment, the boot loader 103 loads the dump generation program 107 so that the memory dump can be generated at an early stage of the boot process in the OS 105.

FIG. 6 shows a dump generation sequence according to the present embodiment. When the power of the computer is turned on, the BIOS 101 starts processing. BIOS101 first initializes the device (S611). Subsequently, as shown in FIG. 7, the BIOS 101 loads the boot loader 103 stored in the hard disk drive 201 into the main memory 203 (S613). Then, the BIOS 101 starts the boot loader 103 (S615).

In the present embodiment, as shown in FIG. 7, the path file 701 is also stored when the dump generation program 107 is stored. In the path file 701, a path for specifying the storage position of the dump generation program 107 in the file system is set.

When the boot loader 103 starts processing (S621), as shown in FIG. 8, the boot loader 103 loads the dump generation program 107 stored in the hard disk drive 201 in a file format into the main memory 203 (S623). At this time, the boot loader 103 refers to the path file 701.

After that, as shown in FIG. 9, the boot loader 103 loads the OS 105 stored in the hard disk drive 201 in a file format into the main memory 203 (S625). Then, the boot loader 103 boots the OS 105 (S627).

In the present embodiment, the called OS 105 executes a predetermined process (hereinafter, referred to as a preprocess) before executing the start process (S631). The pretreatment will be described later with reference to FIG.

When the preprocessing is completed, the OS 105 starts the startup process (S633). In this example, the OS 105 shall detect an error or an external interrupt before the file system is prepared (S635). The OS 105 starts the dump generation program 107 that has already been loaded at this stage (S637).

Then, the dump generation program 107 starts the dump generation process (S641) and generates a dump file (S643).

In the present embodiment, the OS 105 transmits the storage position of the dump generation program 107 in the hard disk drive 201 to the boot loader 103 via the path file 701. Further, the boot loader 103 transmits the load position of the dump generation program 107 in the main memory 203 to the OS 105 by using the memory map. The processing related to the memory map will be described later. This is the end of the outline of the present embodiment.

Subsequently, the operation of the boot loader 103 will be described. FIG. 10 shows a module configuration example of the boot loader 103. The boot loader 103 includes an acquisition module 1001, a load module 1003, a call module 1005, and a delivery module 1007. The acquisition module 1001, the load module 1003, the call module 1005, and the delivery module 1007 are all software modules.

The acquisition module 1001 includes a process of acquiring a memory map from the BIOS 101. An acquisition unit that is a functional element is realized by a hardware resource (for example, FIG. 20) and an acquisition module 1001 that causes a processor in the hardware resource to execute a process described later.

The load module 1003 includes a process of loading the dump generation program 107. A load unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and a load module 1003 that causes a processor in the hardware resource to execute a process described later.

The calling module 1005 includes a process of calling the OS 105. A calling unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and a calling module 1005 that causes a processor in the hardware resource to execute a process described later.

The delivery module 1007 includes a process of delivering the memory map to the OS 105. A delivery unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and a delivery module 1007 that causes a processor in the hardware resource to execute a process described later.

FIG. 11 shows the processing flow of the boot loader 103. The acquisition unit acquires a memory map from the BIOS 101 (S1101). The memory map includes a set of the name of the program or data loaded in the main memory 203 and the load position (including the start address of the load area).

The load unit reads the path file 701 stored in the predetermined storage position (S1103), and determines whether or not the storage destination path of the dump generation program 107 is set in the path file 701 (S1105). If the storage destination path of the dump generation program 107 is not set in the path file 701, the dump generation program 107 is not loaded. Therefore, the process proceeds to the process of S1201 shown in FIG. 12 via the terminal A. The processing of FIG. 12 will be described later.

On the other hand, when it is determined that the storage destination path of the dump generation program 107 is set in the path file 701, the load unit determines whether or not the file specified by the storage destination path exists (S1107). .. If the file specified by the storage destination path does not exist, the dump generator 107 is not loaded. Therefore, the process proceeds to the process of S1201 shown in FIG. 12 via the terminal A.

On the other hand, when it is determined that the file specified by the storage destination path exists, the load unit determines whether or not the file specified by the storage destination path is a genuine dump generation program 107 (S1109). For example, the load unit determines that the file is a genuine dump generator 107 when an identification code indicating that the file is a dump generator 107 is set at a predetermined position of the file specified by the storage destination path. judge. If the file specified by the storage destination path is not the genuine dump generator 107, the dump generator 107 is not loaded. Therefore, the process proceeds to the process of S1201 shown in FIG. 12 via the terminal A.

On the other hand, when it is determined that the file specified by the storage destination path is the genuine dump generation program 107, it is determined whether or not the OS 105 and the dump generation program 107 fit in the main memory 203.

Therefore, the load unit first specifies the size of the dump generation program 107 (S1111). Further, the load unit specifies the size of the OS 105 (S1113). Further, the load unit specifies the size of the free area of the memory (S1115).

Then, the load unit determines whether or not the free area size of the memory is equal to or larger than the sum of the size of the dump generation program 107 and the size of the OS 105 (S1117). If the size of the free memory area is less than the sum of the size of the dump generation program 107 and the size of the OS 105, the dump generation program 107 is not loaded. Therefore, the process proceeds to the process of S1201 shown in FIG. 12 via the terminal A.

On the other hand, when it is determined that the size of the free memory area is equal to or larger than the sum of the size of the dump generation program 107 and the size of the OS 105, the dump generation program 107 is loaded. Therefore, the process proceeds to the process of S1301 shown in FIG. 13 via the terminal B.

Next, the process when the dump generation program 107 is not loaded will be described with reference to FIG. The calling unit secures an area corresponding to the size of the OS 105 in the main memory 203, and loads the OS 105 stored in the hard disk drive 201 into the area (S1201). Then, the calling unit starts the loaded OS 105 (S1203).

Then, the delivery unit passes the memory map to the OS 105 (S1205). Since the dump generation program 107 is not loaded at this time, the load position of the dump generation program 107 is not included in the memory map. Then, the process of the boot loader 103 is finished.

Next, the process when the dump generation program 107 is loaded will be described with reference to FIG. The load unit secures an area corresponding to the size of the dump generation program 107 in the main memory 203, and loads the dump generation program 107 stored in the hard disk drive 201 into the area (S1301).

Next, the calling unit secures an area corresponding to the size of the OS 105 in the main memory 203, and loads the OS 105 stored in the hard disk drive 201 into the area (S1303). Then, the calling unit starts the loaded OS 105 (S1305).

The delivery unit adds the load position of the dump generation program 107 to the memory map (S1307), and passes the memory map to the OS 105 (S1309). Then, the process of the boot loader 103 is finished.

Subsequently, the operation of the OS 105 will be described. FIG. 14 shows an example of the module configuration of OS105. The OS 105 has a reception module 1401, a setting module 1403, a start module 1405, an interrupt handler 1411, and a parameter area 1413. The boot module 1405 includes a creation module 1407 and an error handling module 1409. The receiving module 1401, the setting module 1403, the starting module 1405, the creating module 1407, the error handling module 1409, and the interrupt handler 1411 are all software modules.

The receiving module 1401 includes a process of accepting a memory map from the boot loader 103. A receiving unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and a receiving module 1401 that causes a processor in the hardware resource to execute a process described later.

The setting module 1403 includes a process of setting the load position of the dump generation program 107 in the parameter area 1413. A setting unit that is a functional element is realized by a hardware resource (for example, FIG. 20) and a setting module 1403 that causes a processor in the hardware resource to execute a process described later.

The boot module 1405 includes a boot process of the OS 105. A hardware resource (for example, FIG. 20) and a startup module 1405 that causes a processor in the hardware resource to execute a process described later realize a startup unit that is a functional element.

The creation module 1407 includes a process of creating a dump generation program 107. A creation unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and a creation module 1407 that causes a processor in the hardware resource to execute a process described later.

The error handling module 1409 includes a process of starting the dump generation program 107 as error handling in the OS 105. An error handling unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and an error handling module 1409 that causes a processor in the hardware resource to execute a process described later.

The interrupt handler 1411 includes a process of invoking the dump generation program 107 in response to an interrupt event. An interrupt processing unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and an interrupt handler 1411 that causes a processor in the hardware resource to execute a process described later. Although external interrupts such as key presses, mouse clicks, and screen touches are assumed here, internal interrupts may be supported.

The parameter area 1413 is used to store the load position of the dump generation program 107, that is, the start address of the dump generation program 107 in the main memory 203.

FIG. 15 shows the processing flow of OS105. The receiving unit receives the memory map from the boot loader 103 (S1501). The receiving unit determines whether or not the load position of the dump generation program 107 is included in the memory map (S1503). If it is determined that the memory map does not include the load position of the dump generation program 107, the process proceeds to S1507.

On the other hand, when it is determined that the memory map includes the load position of the dump generation program 107, the setting unit sets the load position of the dump generation program 107 in the parameter area 1413 (S1505). The processing of S1501 to S1505 corresponds to the preprocessing shown in S631 of FIG.

Then, the startup unit executes the startup process of OS105 (S1507). When the startup process is completed, the OS 105 is ready to perform the resident process.

The OS 105 startup process includes a process of creating the dump generation program 107 (hereinafter referred to as a creation process) as described above. FIG. 16 shows a creation processing flow.

The creation unit determines whether or not the dump generation program 107 exists in the storage destination path (S1601). If it is determined that the dump generation program 107 exists in the storage destination path, the creation process ends.

On the other hand, if it is determined that the dump generation program 107 does not exist in the storage destination path, the creation unit creates the dump generation program 107 (S1603). The method of creating the dump generation program 107 is the same as that of the prior art. The creation unit stores the dump generation program 107 in the storage destination path (S1605).

The creation unit creates the path file 701 at a predetermined storage position in the file system (S1607). The creation unit stores the storage destination path of the dump generation program 107 in the path file 701 (S1609). Then, the creation process is completed.

Further, the OS 105 startup process described above includes a setting process for associating the interrupt handler 1411 with a predetermined interrupt event. When the setting process is executed, the interrupt handler 1411 is started at the timing when a predetermined interrupt event occurs.

Next, the processing of the interrupt handler 1411 set in the processing will be described. FIG. 17 shows the processing flow of the interrupt handler 1411.

The interrupt processing unit determines whether or not the load position of the dump generation program 107 is set in the parameter area 1413 (S1701). Specifically, the interrupt processing unit determines that the load position of the dump generation program 107 is not set when, for example, a code indicating that it has not been set is set in the parameter area 1413.

If it is determined that the load position of the dump generation program 107 is not set in the parameter area 1413, the processing of the interrupt handler 1411 is terminated as it is.

On the other hand, when it is determined that the load position of the dump generation program 107 is set in the parameter area 1413, the interrupt processing unit starts the dump generation program 107 (S1703). Specifically, the interrupt processing unit jumps to the load position in the main memory 203 and causes the processor to execute the instruction of the dump generation program 107. Then, the processing of the interrupt handler 1411 is completed.

Further, the OS 105 startup process described above includes an error occurrence detection process and an error handling process. In the error occurrence detection process, for example, the occurrence of an error is detected when an unexpected state occurs or an inconsistent situation occurs. Then, when the occurrence of an error is detected, the error handling process is executed. FIG. 18 shows an error handling processing flow.

The error response unit determines whether or not the load position of the dump generation program 107 is set in the parameter area 1413 (S1801). Specifically, the interrupt processing unit determines that the load position of the dump generation program 107 is not set when, for example, a code indicating that it has not been set is set in the parameter area 1413.

If it is determined that the load position of the dump generation program 107 is not set in the parameter area 1413, the error handling process is terminated as it is.

On the other hand, when it is determined that the load position of the dump generation program 107 is set in the parameter area 1413, the error response unit starts the dump generation program 107 (S1803). Specifically, the error response unit jumps to the load position in the main memory 203 and causes the processor to execute the instruction of the dump generation program 107. Then, the error handling process is completed.

Finally, the dump generation program 107 will be described. The dump generation program 107 includes a process of generating a dump file in which the contents of the main memory 203 are recorded. A dump generation unit, which is a functional element, is realized by a hardware resource (for example, FIG. 20) and a dump generation program 107 that causes a processor in the hardware resource to execute a process described later.

FIG. 19 shows a processing flow of the dump generation program 107. The dump generation unit opens a new dump file at a predetermined storage position (S1901). Then, the dump generation unit sequentially identifies one block of the main memory 203 (S1903).

The dump generation unit reads the data of the block from the main memory 203 (S1905), and sequentially writes the data of the read block to the dump file (S1907).

Then, the dump generation unit determines whether or not the final block has been reached (S1909). If it is determined that the final block has not been reached, the process returns to the process shown in S1903, and the above process is repeated.

On the other hand, when it is determined that the final block has been reached, the dump generation unit closes the dump file (S1911). Then, the processing of the dump generation program 107 is completed.

In the above example, the boot loader 103 passes the load position of the dump generation program 107 to the OS 105 by using the memory map, but the boot loader 103 may pass the load position to the OS 105 according to the boot parameter.

According to this embodiment, the memory dump process can be performed at an early stage of the OS 105 startup process.

Further, since the path file is provided, the dump generator 107 created by the OS 105 can be specified by the boot loader 103.

Further, since the dump generation program 107 is started in the interrupt processing, the memory dump can be performed at an arbitrary timing.

Further, since the dump generation program 107 is started as an error response, it is easy to secure the data used for the error analysis.

Although one embodiment of the present invention has been described above, the present invention is not limited thereto. For example, the functional block configuration described above may not match the program module configuration.

Further, the configuration of each storage area described above is an example, and does not have to be the configuration as described above. Further, also in the processing flow, if the processing result does not change, the order of the processing may be changed or a plurality of processing may be executed in parallel.

As shown in FIG. 20, the computer described above includes a memory 2501, a CPU (Central Processing Unit) 2503, a hard disk drive (HDD) 2505, and a display control unit 2507 connected to the display device 2509. The drive device 2513 for the removable disk 2511, the input device 2515, and the communication control unit 2517 for connecting to the network are connected by a bus 2519. The operating system (OS) and the application program for executing the processing in this embodiment are stored in the HDD 2505, and when executed by the CPU 2503, they are read from the HDD 2505 into the memory 2501. The CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 according to the processing contents of the application program to perform a predetermined operation. Further, although the data in the process of processing is mainly stored in the memory 2501, it may be stored in the HDD 2505. In the embodiment of the present invention, the application program for performing the above-described processing is stored and distributed on the computer-readable removable disk 2511 and installed from the drive device 2513 to the HDD 2505. It may be installed on the HDD 2505 via a network such as the Internet and a communication control unit 2517. Such a computer device realizes various functions as described above by organically collaborating with the hardware resources such as the CPU 2503 and the memory 2501 described above and the program such as the OS and the application program. To do.

The embodiments of the present invention described above can be summarized as follows.

In the computer boot method according to the present embodiment, in (A) boot loader processing, a program for performing memory dump processing is loaded into memory, the load position of the program is passed to the operating system, and (B) operating system boot processing. It includes a process of starting the program based on the load position at any of the timings.

In this way, the memory dump process can be performed at an early stage of the operating system boot process. Specifically, the memory dump process can be performed even before the preparation of the file system is completed.

Further, the computer booting method may include a process of creating the program and writing the storage position of the created program to a non-volatile storage medium in the booting process of the operating system. Further, the computer booting method may include a process of reading the storage position of the program from the storage medium in the process of the boot loader.

In this way, the program created by the operating system can be identified in the boot loader. The hard disk drive 201 is an example of a non-volatile storage medium.

Further, the above timing may be the time when the interrupt event occurs.

In this way, a memory dump can be obtained at an arbitrary timing.

Further, the above timing may be the time when an error is detected.

In this way, it is easy to secure the data used for the error analysis.

A program for causing a computer to perform the processing by the above method can be created, and the program can be a computer-readable storage medium such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, or a hard disk. It may be stored in a storage device. The intermediate processing result is generally temporarily stored in a storage device such as a main memory.

The following additional notes will be further disclosed with respect to the embodiments including the above embodiments.

(Appendix 1)
In the boot loader process, the program that performs the memory dump process is loaded into memory, and the load position of the program is passed to the operating system.
A computer booting method executed by a computer that includes a process of launching the program based on the load position at any timing during the booting process of the operating system.

(Appendix 2)
In addition
In the boot process of the operating system, the program is created, and the storage position of the created program is written to a non-volatile storage medium.
The computer booting method according to Appendix 1, which includes a process of reading the storage position of the program from the storage medium in the process of the boot loader.

(Appendix 3)
The timing is the time when the interrupt event occurs. The computer startup method according to Appendix 1 or 2.

(Appendix 4)
The timing is the time when an error is detected. The computer booting method according to Appendix 1 or 2.

(Appendix 5)
A boot loader that includes a process that loads a program that performs memory dump processing into memory and passes the load position of the program to the operating system.
A computer having a medium for storing the operating system including a process of starting the program based on the load position at any timing during its own startup process.

101 BIOS
103 Bootloader 105 OS
107 Dump generator 201 Hard disk drive 203 Main memory 701 Pass file 1001 Acquisition module 1003 Load module 1005 Call module 1007 Delivery module 1401 Accepting module 1403 Setting module 1405 Startup module 1407 Creation module 1409 Error response module 1411 Interrupt handler 1413 Parameter area

Claims (5)

In the boot loader process, the program that performs the memory dump process is loaded into memory, and the load position of the program is passed to the operating system.
A computer booting method executed by a computer that includes a process of launching the program based on the load position at any timing during the booting process of the operating system. In addition
In the boot process of the operating system, the program is created, and the storage position of the created program is written to a non-volatile storage medium.
The computer booting method according to claim 1, wherein in the boot loader process, a process of reading the storage position of the program from the storage medium is included. The computer startup method according to claim 1 or 2, wherein the timing is a time when an interrupt event occurs. The computer booting method according to claim 1 or 2, wherein the timing is the time when an error is detected. A boot loader that includes a process that loads a program that performs memory dump processing into memory and passes the load position of the program to the operating system.
A computer having a medium for storing the operating system including a process of starting the program based on the load position at any timing during its own startup process.

Images