JP4985483B2 - Computer system, network bootload system, and bootload method thereof - Google Patents

Description

  The present invention relates to a computer system, a network boot load system, and a boot load method thereof.

  A technique for bootloading an OS (Operating System) file to a computer system via a network is known.

  Conventionally, a ROM (Read Only Memory) in which a control program (BIOS) is stored in advance is mapped to a predetermined storage area of the main storage device, and a method in which this BIOS performs boot loading of an OS file or a diagnosis processor performs diagnosis A method of boot loading an OS file via a path is common.

As a prior art document disclosing a method for bootloading an OS file via a network, for example, there is Patent Document 1. The technique of Patent Document 1 requires NBP (Network Boot Program) as shown in FIG.
JP 2006-252168 A

  The conventional OS file bootloading via the network has a problem that NBP is required as disclosed in Patent Document 1, for example.

  Further, since boot loading of the conventional OS file is performed through the diagnostic path, there is a problem that it takes time. Because the purpose of use of the diagnostic path is limited processing such as hardware initialization of the computer system and is not for normal operation, it is required to be more stable and cheaper than performance, This is because the transfer speed is generally slower than the access path used in operation.

  Furthermore, generally, since the execution of boot is before the OS is running, the execution of boot is before the initial setting of the computer system by the OS is completed. Even in a computer system having a plurality of CPUs, the boot is executed, However, since only one CPU can operate until the input / output device can be used, there is a problem that the specifications of the computer system including a plurality of CPUs cannot be fully utilized.

  The present invention has been made to solve the above-described problems, and provides a computer system, a network bootload system, and a bootload method thereof capable of performing bootload without requiring an NBP. The purpose is to provide.

  In order to solve the above problems, a computer system according to the present invention includes a processor, a main storage device, and an input / output device, and is connected to an external server via a network. The computer system including a storage device and the input / output device includes a diagnostic processor that is connected via a diagnostic path to initialize each of the hardware constituting the computer system, and the computer system includes: A boot load execution function for executing boot load of an OS file; and a determination function immediately after initialization for determining whether or not the hardware constituting the computer system is immediately initialized. Is in a stage after initialization of the hardware and before completion of boot loading of the OS file The boot load execution function receives the OS file data transmitted from the external server in response to the boot load request from the computer system immediately after the initialization. The function is to write the received data in a predetermined storage area in the main storage device in accordance with predetermined address information, and the input / output device executes the boot load execution function.

  A network boot load system according to the present invention includes a computer system including a processor, a main storage device, and an input / output device, and an external server connected to the computer system via a network. The computer system includes: A diagnostic processor connected via a diagnostic path to each piece of hardware constituting the computer system including at least the processor, the main storage device, and the input / output device, and performing initialization of the hardware. The computer system includes a boot load execution function for executing boot load of an OS file, and a determination function immediately after initialization for determining whether or not hardware constituting the computer system is immediately initialized. The determination function immediately after initialization is performed after initialization of the hardware and the OS file. In the stage before the completion of the boot load, the boot load execution function is a function of determining whether the external server is in response to a boot load request from the computer system immediately after the initialization. The function is to receive OS file data transmitted from the OS and write the received data to a predetermined storage area in the main storage device according to predetermined address information, and the input / output device executes the boot load execution function It is characterized by doing so.

  The bootloading method of the present invention is a method of bootloading a computer system that includes a processor, a main storage device, and an input / output device and is connected to an external server via a network. A first step of initializing each of the hardware constituting the computer system including the storage device and the input / output device, and a stage after the initialization of the hardware and before completion of boot loading of the OS file In the case where the second process is determined to be immediately after the initialization and the second process is determined to be immediately after the initialization in the second process, the external process is performed in response to a boot load request from the computer system. The OS file data transmitted from the server is received in the third process that the input / output device receives and in the third process. The data of S file, the input-output device is characterized by and a fourth step of writing a predetermined storage area in the main memory in accordance with predetermined address information.

  According to the present invention, after initialization of each hardware in the computer system, the input / output device receives data of the OS file from the external server via the network, and the received data is stored in the main memory according to the predetermined address information. Since the data is written in a predetermined storage area in the apparatus, NBP is unnecessary.

  In addition, after initialization of each hardware in the computer system, the input / output device receives the data of the OS file from the external server via the network, and the received data is stored in the main storage device according to predetermined address information. Since it is written in the storage area, in the case of a computer system with a general configuration, the diagnostic processor performs an initial boot loader via the diagnostic path, or the diagnostic processor stores the OS file in the main storage device. The boot load can be completed at high speed.

  Embodiments according to the present invention will be described below with reference to the drawings.

[First Embodiment]
FIG. 1 is a block diagram showing a configuration of a network boot load system 100 including a computer system 1 according to the first embodiment.

  As shown in FIG. 1, a network bootload system 100 according to the first embodiment includes a computer system 1, an external server 8 provided outside the computer system 1, and a storage device attached to the external server 8. 12, and a diagnosis network 9 and an OS network 13 that connect the external server 8 and the computer system 1.

  The diagnosis network 9 and the OS network 13 are networks using TCP-IP (Transmission Control Protocol / Internet Protocol), for example, and may be Ethernet (registered trademark).

  As shown in FIG. 1, the computer system 1 includes a central processing unit (CPU) 2 as a processor, a main memory unit (MMU) 3, and a system control unit (SCU: System Control Unit). ) 4, an input / output device (IOP: I / O Processor) 5, a diagnostic processor 6, and a diagnostic path 7.

  The CPU 2 performs various operations by a SW program such as an OS after bootloading.

  In the case of this embodiment, the computer system 1 includes a plurality of CPUs 2, for example.

  The SCU 4 relays addressing between the devices 2, 3 and 5.

  The IOP 5 is connected to the external server 8 via the OS network 13.

  The diagnostic processor 6 is connected to each of the devices 2, 3, 4, and 5 in the computer system 1 via a dedicated diagnostic path 7, and is connected to the external server 8 via a diagnostic network 9.

  The storage device 12 stores an operating system (OS) file 11.

  The external server 8 has a function of accessing the storage device 12 to acquire the OS file 11 and sending the acquired OS file 11 to the computer system 1.

  FIG. 2 is a block diagram showing a detailed configuration of each component shown in FIG.

  As shown in FIG. 2, the IOP 5 includes, for example, a first control memory 50A composed of a ROM (Read Only Memory) and a second control memory 50B composed of a RAM (Random Access Memory).

  The first control memory 50A includes an IOP control program 51 that is an FW (Firmware) that controls the IOP 5, and an address table 52 that specifies an area in which data of the OS file 11 to be boot-loaded is written in the storage area of the MMU 3. Stored (stored).

  The second control memory 50B stores the post-initialization flag 10 (memory retention). The post-initialization flag 10 is a flag indicating whether or not the hardware of the computer system 1 including the devices 2, 3, 4, and 5 has been initialized.

  The diagnostic processor 6 also has a control memory 60 that stores a program for controlling the diagnostic processor 6.

  The programs stored in the control memory 60 include, for example, a CPU communication function program 61, a diagnostic path control function program 62, a device access function program 63, and an external server communication function program 64. It is.

  Among them, the CPU communication function program 61 is an FW that controls a function of interrupting the CPU 2 from the diagnostic processor 6 to be described later.

  The diagnostic path control function program 62 is an FW that controls a function of switching a device to be accessed from the diagnostic processor 6 (for example, any one of CPU2, MMU3, SCU4, and IOP5) by selecting the diagnostic path 7. is there.

  The device access function program 63 is an FW that controls the function of the diagnostic processor 6 accessing each of the devices 2, 3, 4, 5 via the diagnostic path 7 selected according to the diagnostic path control function program 62. is there.

  The external server communication function program 64 is an FW that controls the function of the diagnostic processor 6 to communicate with the external server 8.

  Next, the operation will be described.

  When the computer system 1 is powered on, the diagnostic processor 6 first initializes itself.

  When initialization of the diagnostic processor 6 itself is normally completed, the diagnostic processor 6 initializes all devices (except for the diagnostic processor 6) in the computer system 1.

  That is, the diagnostic processor 6 initializes each hardware in the computer system 1 including the CPU 2, MMU 3, SCU 4, and IOP 5.

  Since the initialization operation is well known to those skilled in the art, detailed description thereof is omitted.

  FIG. 3 is a flowchart showing an operation flow of the network boot load system 100 in the case of the first embodiment.

  The operation of FIG. 3 is started when initialization of each hardware in the computer system 1 including the CPU 2, MMU 3, SCU 4 and IOP 5 is completed by the diagnostic processor 6.

  That is, the diagnosis processor 6 monitors whether or not the initialization is completed. When the diagnosis processor 6 determines that the initialization is completed, the value indicating that the initialization is completed is indicated in the post-initialization flag 10 in the IOP 5 via the diagnosis path 7. (For example, “1”) is set (step S1).

  Subsequently, the diagnostic processor 6 transmits a boot load request to the external server 8 (step S2).

  The external server 8 that has received this boot load request sends the data of the OS file 11 in the storage device 12 to the IOP 5 via the OS network 13 (step S3).

  The external server 8 is configured to divide the OS file 11 into a plurality of data and sequentially transmit the data. In step S3, the plurality of data (hereinafter referred to as divided data) are converted from the first divided data. Send all in order.

  The method of dividing the OS file 11 and the order of transmission are determined in advance, and the address at which the divided data to be transmitted is stored in the MMU 3 is also determined in advance.

  Subsequently, the IOP 5 first receives the first divided data among the divided data sent by the external server 8 in the previous step S2 (step S4). When the IOP 5 receives data from the external server 8, the IOP 5 notifies the external server 8 that the data has been received.

  Subsequently, the IOP 5 checks the post-initialization flag 10 (step S5).

  If the setting content of the post-initialization flag 10 is not a value (for example, “1”) indicating after initialization (No in step S5), that is, a value indicating that it is not after initialization (for example, “0”). If so, the process of FIG. 3 is terminated.

  If the setting content of the post-initialization flag 10 is a value indicating post-initialization (eg, “1”) (Yes in step S5), the IOP 5 refers to the address table 52 (step S6).

  Here, the address table 52 designates each divided data of the OS file 11 sequentially transmitted from the external server 8 as described above, and which address storage area in the MMU 3 should be stored. Address information to be stored in association with each other.

  More specifically, the address table 52 has as many data entries as the number of divided data.

  For example, if the OS file 11 is transmitted in three divided data, the address table 52 includes three data entries.

  Each data entry is information indicating a correspondence between the transmission order of the corresponding divided data and address information indicating which address in the MMU 3 should store the divided data.

  Therefore, for example, every time the divided data of the OS file 11 is received from the external server 8, the IOP 5 refers to the data entry corresponding to the order in which the divided data is received, thereby obtaining the address information corresponding to the divided data. The divided data can be stored at a predetermined address in the MMU 3 according to the extracted address information. Therefore, for example, when the first divided data is received, the IOP 5 can extract the address information corresponding to the first divided data by referring to the first data entry in the address table 52. Therefore, the IOP 5 can recognize which address in the MMU 3 should store the divided data, and can store the divided data at the recognized address.

  Subsequently, the IOP 5 writes the divided data received in the previous step S3 to the address specified by the address table 52 in the storage area of the MMU 3 (step S7).

  As described above, in this embodiment, immediately after the initialization, the predetermined address in the MMU 3 specified by the address table 52 in the IOP 5 is used instead of the data transfer destination address set in the IOP 5 by the instruction from the CPU 2. Write the received data to the address.

  Here, every time the divided data is written to the MMU 3, the IOP 5 recognizes that the data entry in the address table 52 corresponding to the divided data has been processed. Therefore, the IOP 5 recognizes whether there is any divided data that has not been written to the MMU 3 by determining which of the data entries included in the address table 52 is not “processed”. Can be done.

  Note that as a technique for the IOP 5 to recognize that the data entry in the address table 52 has been processed, a “processed” flag is set for the processed data entry. In this case, the IOP 5 determines whether or not there is a data entry in which the “processed” flag is not yet set among the data entries included in the address table 52, so that writing to the MMU 3 is not completed. It is possible to recognize the presence or absence of data.

  That is, in step S8 following step S7, the IOP 5 determines whether or not there is a data entry in the address table 52 for which data writing to the MMU 3 has not been completed.

  If it exists (Yes in step S8), the data sent from the external server 8 is sequentially received (step S4), and the process of writing the data in the MMU 3 (steps S6 and S7) is repeated.

  In this case, the external server 8 once transmits all the divided data of the OS file 11 sequentially to the IOP 5 side (regardless of whether the divided data is received on the IOP 5 side). As described above, the IOP 5 notifies the external server 8 that the received divided data has been received. If the external server 8 does not receive a notification of data reception from the IOP 5 within a predetermined time after sending each piece of divided data, the external server 8 determines that the divided data has been sent and returns the divided data to the IOP 5 again. Send it.

  If there is no data entry in the address table 52 that has not yet been written to the MMU 3, that is, when all the divided data of the OS file 11 has been written to the MMU 3 (No in step S8). The IOP 5 notifies the diagnosis processor 6 to that effect (table completion) (step S9).

  When the diagnosis processor 6 receives notification from the IOP 5 that the table is completed, the diagnostic processor 6 resets the post-initialization flag 10 in the IOP 5. That is, the IOP 5 rewrites the value of the post-initialization flag 10 from a value indicating that it is after initialization to a value (for example, “0”) indicating that it is not after initialization (step S10).

  Subsequently, the diagnostic processor 6 determines that the boot load is completed by resetting the post-initialization flag 10, and interrupts the CPU 2 (step S11).

  In response to this interruption, the control subject passes from the diagnostic processor 6 to the CPU 2, and the CPU 2 activates the OS file 11 loaded in the MMU 3. Thereby, normal processing is started.

  That is, first, initialization (not initialization) for enabling the OS to use hardware such as the CPU 2 and the IOP 5 is performed according to the OS file 11 loaded in the MMU 3.

  Then, since the search and installation processing of the input / output devices after setting the memory space and process information by the initial setting can be executed by the plurality of CPUs 2, the multiprocessor can be quickly executed before the OS becomes ready. Therefore, the specifications of the computer system 1 having a plurality of CPUs 2 can be utilized.

  It should be noted that functions such as IOP5 in a state where the boot load is not being performed are well known to those skilled in the art and are not directly related to the present embodiment, and thus detailed description thereof is omitted.

  According to the first embodiment as described above, after initialization of each hardware (CPU2, MMU3, SCU4, IOP5, etc.) included in the computer system 1, the IOP5 receives the data of the OS file 11 from the external server 8. Then, since the IOP5 directly bootloads the received data to the MMU 3, no NBP is required. Therefore, it is possible to solve the problem that “the execution speed of the computer is slow due to the processing by NBP execution, and the development cost increases for the vendor”.

  In addition, after initialization of each hardware (CPU2, MMU3, SCU4, IOP5, etc.) included in the computer system 1, the IOP5 receives the data of the OS file 11 from the external server 8, and the IOP5 directly receives the received data from the MMU3. Therefore, in the case of the computer system 1 having a general configuration, the boot load is faster than the diagnosis processor 6 performs the initial boot loader via the diagnosis path 7 or stores the OS file 11 in the MMU 3. Can be completed. This is because the purpose of use of the diagnostic path 7 is limited processing such as initialization of the hardware provided in the computer system 1 and is not for normal operation, so it is required to be more stable and cheaper than performance. This is because the transfer speed is generally slower than the access path used in operation.

  In addition, after completing the initial setting of each hardware including the CPU 2 and the IOP 5 in accordance with the OS file 11 expanded on the MMU 3, a plurality of CPUs 2 search for input / output devices that are connected first from the IOP 5 and incorporate them. Can be executed (can be executed by multiprocessor). For this reason, before the OS becomes ready, there is an effect that the specification of the computer system 1 having a plurality of CPUs 2 can be utilized by quickly shifting to execution by a multiprocessor.

[Second Embodiment]
In the first embodiment, the example in which the address table 52 is stored in the IOP 5 in advance has been described. In the second embodiment, an example in which the address table 52 is written in the IOP 5 at the time of initialization will be described.

  4 and 5 are block diagrams showing the configuration of the network boot load system 100 including the computer system 1 in the case of the second embodiment, in which FIG. 4 shows before writing the address table 52 to the IOP 5. FIG. 5 shows a state after the address table 52 is written to the IOP 5.

  In the present embodiment, an address table 81 is stored and held in the storage device 12 of the server 8.

  In this embodiment, when boot load after initialization is performed, the address table 81 is written as the address table 52 in the second control memory 50B of the IOP 5 (as described above, for example, composed of RAM).

  In this embodiment, after the writing, the network boot load system 100 operates so as to store each data of the OS file 11 in the MMU 3 according to the written address table 52.

  Therefore, in the case of this embodiment, initially, as shown in FIG. 4, the address table 52 is not stored and held in the IOP 5.

  Then, when the boot load after initialization is performed, the address table 81 is written in the second control memory 50B of the IOP5 as the address table 52 so that the address table 52 is stored in the second control memory 50B as shown in FIG. It is in a state of being stored and held.

  Next, the operation in this embodiment will be described.

  Also in this embodiment, when the computer system 1 is powered on, the diagnostic processor 6 initializes itself. When the initialization of the diagnostic processor 6 is normally completed, the diagnostic processor 6 initializes all the devices (except for the diagnostic processor 6) in the computer system 1.

  FIG. 6 is a flowchart showing an operation flow of the network bootload system 100 in the case of the second embodiment.

  Also in this embodiment, the operation of FIG. 6 is started when the diagnosis processor 6 completes initialization of each hardware in the computer system 1 including the CPU 2, MMU 3, SCU 4, and IOP 5.

  That is, the diagnosis processor 6 monitors whether or not the initialization is completed. When the diagnosis processor 6 determines that the initialization is completed, the diagnosis processor 6 sets a value (for example, indicating that it is after initialization in the post-initialization flag 10 of the IOP 5 via the diagnosis path 7). , “1”) is set (step S1).

  Subsequently, the diagnostic processor 6 transmits a boot load request to the external server 8 (step S2).

  In this embodiment, the external server 8 that has received this boot load request sends the data in the address table 81 in the storage device 12 to the IOP 5 via the OS network 13 (step S21).

  Subsequently, the IOP 5 receives the data in the address table 81 sent from the external server 8 (step S22).

  Subsequently, the IOP 5 checks the post-initialization flag 10 (step S23).

  If the setting content of the post-initialization flag 10 is not a value (for example, “1”) indicating post-initialization (No in step S23), the process of FIG.

  If the setting content of the post-initialization flag 10 is a value indicating post-initialization (for example, “1”) (Yes in step S23), the IOP5 stores the address table 81 received in the previous step S22. Data is written in the second control memory 50B as the address table 52 (step S24).

  Subsequently, the external server 8 sends the data of the OS file 11 in the storage device 12 to the IOP 5 via the OS network 13 as in the first embodiment (step S3).

  Since the process after step S3 is the same as that of said 1st Embodiment, description is abbreviate | omitted.

  According to the second embodiment as described above, the address table 52 is not stored in the IOP 5 in advance, but is received from the external server 8 when the boot load is executed after the initialization. Since writing is performed in the memory 50B, the address table written in the IOP 5 can be appropriately changed by appropriately changing the address table stored in the storage device 12 of the external server 8.

  Specifically, for example, the address table 52 not only specifies the storage area of the OS file 11 in the MMU 3, but also specifies in which storage area in the MMU 3 the test diagnosis program or the like should be stored. You can do that. Therefore, various programs can be boot loaded into the MMU 3.

  Specifically, for example, when only the OS file 11 is boot-loaded, an address table 81 that specifies only the storage area of the OS file 11 may be stored in the storage device 12 of the external server 8. 11, in addition to the OS file 11 and the address table 81 that designates only the storage area of the OS file 11, a file storing the test diagnosis program and a storage of the test diagnosis program Another address table for designating the area may be stored in the storage device 12 of the external server 8.

  In each of the above embodiments, an example in which the computer system 1 includes a plurality of CPUs 2 has been described. However, the present invention is not limited to this example, and can be applied to a configuration in which the computer system 1 includes only one CPU 2.

  In each of the above-described embodiments, the example in which the network connecting the IOP 5 and the external server 8 is Ethernet has been described. However, the present invention is not limited to this example, and the diagnostic network 9 and the OS network 13 include infinite bands and interconnects. It may be applied.

  In the second embodiment, the example in which the IOP 5 stores the address table 52 therein has been described. However, the diagnostic processor 6 receives the address table 81 from the external server 8, and the received address table 81 is stored. The diagnostic processor 6 may write the address table 52 in the second control memory 50B of the IOP5.

  Also, an example has been described in which the address table (address table 81) is received from the external server 8 when the address table 52 is written at initialization. However, the diagnostic processor 6 stores the address table 81 in advance and stores the address table 81. The table 81 may be written into the second control memory 50B of the IOP5 as the address table 52 at initialization.

  In each of the above embodiments, the example in which the address information is stored in the IOP 5 as the address table 52 has been described. However, the address table 52 may be stored in the SCU 4. In this case, the IOP 5 performs an operation of storing the data of the OS file 11 received from the external server 8 in a predetermined storage area in the MMU 3 according to the address table 52 stored in the SCU 4.

  Further, in each of the embodiments described above, the example in which the address information is stored in the IOP 5 as the address table 52 has been described. It may be described in the header. In this case, the IOP 5 recognizes in which storage area in the MMU 3 the data should be stored by referring to the address information described in the header portion of the data of the OS file 11 sent from the external server 8. Data can be written to the recognized storage area. In this case, the address table 52 in the IOP 5 is not necessary.

  In the above-described embodiment, the example in which the computer system 1 includes the SCU 4 has been described. However, in the case of the computer system 1 configured without the SCU 4, the initialization thereof is naturally not necessary.

  In each of the embodiments described above, an example in which the processor is a CPU has been described. However, the processor may be another type such as a DSP (Digital Signal Processor).

  In each of the above embodiments, the example in which the OS file 11 is divided into a plurality of divided data and sent from the external server 8 and each divided data is stored in the MMU 3 according to the address information has been described. If the amount of data is small or the processing capability of IOP5 or the like is large, the entire data of the OS file 11 may be sent from the external server 8 and stored in the MMU 3 according to the address information.

  Further, in each of the above embodiments, the example in which the storage device 12 is provided outside the external server 8 has been described, but the storage device 12 may of course have an internal configuration of the external server 8.

It is a block diagram which shows the structure of the network boot load system containing the computer system which concerns on 1st Embodiment. It is a block diagram which shows the detailed structure of each component shown in FIG. It is a flowchart which shows the flow of operation | movement of the network boot load system in the case of 1st Embodiment. It is a block diagram of the structure of the network boot load system containing the computer system in the case of 2nd Embodiment, and shows the state before writing an address table in IOP especially. It is a block diagram of the structure of the network boot load system containing the computer system in the case of 2nd Embodiment, and shows the state after writing an address table in IOP especially. It is a flowchart which shows the flow of operation | movement of the network boot load system in the case of 2nd Embodiment.

Explanation of symbols

1 Computer system 2 Central processing unit (CPU)
3 Main memory (MMU)
4 System control unit (SCU)
5 Input / output devices (IOP)
6 Diagnostic Processor 7 Diagnostic Path 8 External Server 9 Diagnostic Network 10 Post-initialization Flag in IOP 11 Operating System File 12 Storage Device 13 OS Network 50A for Connecting Computer System to External Server First Control Memory 50B in IOP Second control memory 51 in IOP FW for controlling IOP
52 Address table (address information) stored in the IOP control memory
60 Control memory 61 for storing diagnostic processor FW 61 CPU communication function program 62 Diagnostic path control function program 63 Device access function program 64 Server communication function program 81 Address table (address information for designating boot load area) ) File 100 Network Bootload System

Claims (19)

Is connected to an external server via a network, a computer system comprising a central processing unit, a main storage device, including at least a plurality of hardware and input and output devices,
Via said diagnostic path is connected to each hardware, further comprising a diagnostic processor for initialization of each hardware,
The input / output device is
After the initialization of each hardware and, in the case of a boot load before the completion stage of the OS file, the an initialization immediately determining function determines that immediately after the initialization of each hardware,
When the initialization immediately after the decision function is determined to be immediately after the initialization, the data of the OS file transmitted from the external server in response to the boot load request from the computer system, said main memory in accordance with predetermined address information Nde written to a predetermined storage area in the device, and boot load execution function for executing a boot loading of the OS file
Have
The diagnostic processor interrupts the central processing unit when the bootload is complete,
The central processing unit is a computer system that activates an OS file loaded in the main storage device in response to an interrupt given by the diagnostic processor . The diagnostic processor is
A flag setting function for setting a post-initialization flag of a value indicating that it is after the initialization after the initialization of the hardware;
Change when the boot load execution function has completed the writing of the OS file to said main memory, resets the value of the initialization after flag the flag setting function is set to a value indicating that only after initialization And a reset function to
Said initialization immediately determining function, when the post-initialization flag is a value indicating that after initialization, the computer system according to claim 1 determines that immediately after the initialization. The input / output device is
The computer system according to claim 2, further comprising a storage area for the post-initialization flag. The boot load execution function, the data of the OS file received from the external server according to the address information in which the input device is held, any one of claims 1 to 3 is written in a predetermined storage area in the main storage device The computer system according to one item. The output device is a computer system of claim 4, the address information, and stores and holds beforehand. The computer system according to claim 4 , wherein the input / output device retains the address information at a stage after the initialization and before the start of boot loading of the OS file. The output device is a computer system according to claim 6 which receives the address information from the external server, to hold the person the received address information. The boot load execution function receives OS file data including the address information ;
The boot load execution function, the data of the OS file received from the external server according to the address information contained in those the data, any one of claims 1-3 to be written in a predetermined storage area in the main storage device The computer system described in 1. The diagnostic processor is
The computer system according to any one of claims 1 to 8 , wherein the boot load request is transmitted to the external server. The computer system according to any one of claims 1 to 9 , comprising a plurality of the central processing units . A computer system comprising a plurality of hardware including at least a central processing unit , a main storage device, and an input / output device;
And an external server connected to the computer system via a network,
The computer system is
Via said diagnostic path is connected to each hardware, further comprising a diagnostic processor for initialization of each hardware,
The input / output device is
After the initialization of each hardware and, in the case of a boot load before the completion stage of the OS file, and the initialization immediately after determining function determines that immediately after the initialization of the hardware,
When the initialization immediately after the decision function is determined to be immediately after the initialization, the data of the OS file transmitted from the external server in response to the boot load request from the computer system, said main memory in accordance with predetermined address information Nde written to a predetermined storage area in the device, and boot load execution function for executing a boot loading of the OS file
Have
The diagnostic processor interrupts the central processing unit when the bootload is complete,
The central processing unit is a network boot loading system that activates an OS file loaded in the main storage device in response to an interrupt applied by the diagnostic processor . The diagnostic processor is
A flag setting function for setting a post-initialization flag of a value indicating that it is after the initialization after the initialization of the hardware;
When the writing of the OS file for the main storage device has been completed, the flag setting function resets the flag after the initialization set, and a reset function to change to a value indicating that only after initialization,
Said initialization immediately determining function, when the state indicating that the post-initialization flag is after initialization, network boot loading system of claim 1 1 determines that immediately after the initialization. The input / output device is
Network bootload system of claim 1 2 further comprising a storage area of the post-initialization flag. The boot load execution function, the data of the OS file received from the external server according to the address information in which the input device is held claims 1 1 1 3 written in a predetermined storage area in the main storage device The network boot load system according to any one of the above. The output device is a network boot loading system according to the address information, to claim 1 4 stored beforehand held. The boot load execution function receives OS file data including the address information ;
The boot load execution function, the data of the OS file received from the external server according to the address information contained in those the data, any of claims 1 1 to 1 3 to be written to a predetermined storage area in the main storage device The network boot load system according to one item. The network boot load system according to any one of claims 1 to 16 , comprising a plurality of the central processing units . A bootload method in which a computer system connected to an external server via a network and having a plurality of hardware including at least a central processing unit, a main storage device, and an input / output device performs bootloading,
A first stage of initializing each hardware;
A second stage in which it is determined immediately after the initialization when each hardware is initialized and before the OS file boot load is completed;
A third stage in which the input / output device receives data of an OS file transmitted from the external server in response to a bootload request from the computer system;
When it is determined in the second stage that it is immediately after the initialization, the OS file data received in the third stage is stored in the main storage device according to predetermined address information by the input / output device. A fourth stage of writing to the area and performing a bootload of the OS file;
A fifth stage in which a diagnostic processor interrupts the central processing unit when bootloading is completed in the fourth stage;
A boot loading method comprising: a sixth stage in which the central processing unit activates an OS file loaded in the main storage device in response to an interrupt given by the diagnostic processor in the fifth stage. After the hardware is initialized at the first step, a seventh step of setting the initialization after flag value indicating that a post-initialization,
When the writing of the OS file for the main storage device is complete, reset the value of the seventh post-initialization flag set at the stage of, the eighth to change to a value indicating that only after initialization And further comprising steps
Wherein in the second stage, when the post-initialization flag is a value indicating that after initialization, the boot loading process according to judges claim 18 as it is immediately after the initialization.

Images