JP7205110B2 - Information processing device, information processing method and information processing program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

2. Description of the Related Art A technology called MCTP (Management Component Transport Protocol) over PCIe is available as a technology in which devices mounted in an information processing apparatus directly communicate with each other via a PCIe (Peripheral Component Interconnect express) bus. In MCTP over PCIe, a node manager operating on a PCH (Platform Controller Hub) becomes a bus owner and performs processing for allocating an MCTP Endpoint ID (Identifier), which is an identifier for communication, to a device compatible with MCTP. A device compatible with MCTP is hereinafter referred to as an MCTP device. The process of allocating the MCTP Endpoint ID is called MCTP Discovery process, and is hereinafter referred to as discovery process. By using the MCTP Endpoint ID allocated by this discovery process, communication between MCTP devices becomes possible.

In recent years, information processing equipment has been equipped with a BMC (Baseboard Management Controller), which manages and controls the server, such as turning on the power and monitoring errors, independently of the CPU (Central Processing Unit) on the system board. There is The BMC monitors hardware using, for example, an interface conforming to the IPMI (Intelligent Platform Management Interface) standard. The BMC monitors MCTP devices registered in its own MCTP device list. The MCTP device list managed by the BMC is created by the MCTP agent inside the BMC periodically acquiring the MCTP device information list from the node manager, which is the bus owner. Specifically, the BMC acquires a list of MCTP devices including the BMC from the node manager, which is the bus owner, using the Get Routing Talbe Entries command, and creates an MCTP device list. An external management server or the like that acquires the devices of the apparatus from the BMC inquires of the BMC about valid MCTP devices, and collects information from the valid MCTP devices notified from the BMC.

When performing MCTP communication with a target MCTP device, the BMC acquires the MCTP Endpoint ID from the MVTP device list based on the PCIe address information as the PCIe device. The BMC then uses the obtained MCTP Endoint ID to communicate with the target MCTP device.

Here, discovery processing will be described. A node manager, which is a bus owner, issues an initialization start instruction to all the devices mounted on the information processing apparatus when the PCIe bus is initialized. After that, the node manager periodically repeats the following process. The node manager determines whether or not the information processing device is equipped with a PCIe device. If the PCIe device exists, the node manager issues an Endpoint Discovery command to that PCIe device. If the PCIe device responds to the Endpoint Discovery command, the Node Manager allocates an MCTP Endpoint ID to the PCIe device. A PCIe device that has already been discovered and assigned an MCTP Endpoint ID does not respond to the Endpoint Discovery command.

In order to match its own MCTP device list with the latest MCTP device list possessed by the node manager, the BMC periodically polls the node manager and acquires the latest MCTP device list. The BMC starts this polling process when its own MCTP Endpoint ID is determined by its own discovery process.

As a communication technique between PCIe devices, there is a conventional technique of configuring device information based on prestored configuration parameters and performing packet communication using the configured device information. In addition, as a technology for determining the work end time, the work start and end events are detected, the time spent on the work is calculated, the calculated time and the estimated time are used to calculate the delay rate, and the calculated delay rate There is a technique for estimating the end time of work using

Japanese Patent Publication No. 2017-503238 JP 2011-215977 A

However, in the method of obtaining the latest list of MCTP devices by polling, the BMC does not grasp the progress of the discovery process performed between the node manager, which is the bus owner, and MCTP devices other than itself. Therefore, it is difficult for the BMC to grasp when the node manager has completed the discovery processing for all PCIe devices after completing the self-discovery processing. That is, the BMC has difficulty determining the completion of the MCTP device list. Therefore, the BMC continues to periodically request the list of MCTP devices from the node manager, and communication occurs periodically from the BMC to the node manager on the PCIe bus. Since the node manager operates on the PCH, which is closely related to the CPU, periodic communication may reduce the processing performance of the information processing apparatus.

In addition, the conventional technology that performs packet communication using device information configured based on configuration parameters does not consider discovery processing, and even with this conventional technology, it is difficult to improve the processing performance of the information processing apparatus. is. Furthermore, it is difficult to grasp the completion time of the discovery process even using the conventional technology that predicts the end time by obtaining the delay rate from the work start and end events, so it is difficult to improve the processing performance of the information processing apparatus. Have difficulty.

The disclosed technology has been made in view of the above, and aims to provide an information processing device, an information processing method, and an information processing program that improve the processing performance of the information processing device.

In one aspect of the information processing apparatus, information processing method, and information processing program disclosed in the present application, the identification unit acquires information on one or more mounted devices from the BIOS, and uses MCTP from among the mounted devices to Identify one or more devices with communication capabilities with which to communicate. The assigning unit detects one or more devices having a communication function for communicating using MCTP from among the mounted devices, and sequentially assigns communication information used for communication using MCTP to the detected devices. do. The obtaining unit repeats obtaining the communication information from the assigning unit until the communication information assigned to all of the devices included in the device list identified by the identifying unit is obtained.

In one aspect, the present invention can improve the processing performance of an information processing device.

FIG. 1 is a block diagram of an information processing device. FIG. 2 is a diagram of an example of PCIe device information. FIG. 3 is a diagram showing an example of the MCTP support status database. FIG. 4 is a diagram showing an example of a predicted MCTP device list. FIG. 5 is a sequence diagram illustrating a process of acquiring an MCTP device list according to the first embodiment; FIG. 6 is a sequence diagram showing the MCTP device list acquisition process when the discovery process is not completed within the expected completion time. FIG. 7 is a flowchart of an MCTP device list acquisition process according to the first embodiment. FIG. 8 is a sequence diagram illustrating an MCTP device list acquisition process according to the second embodiment. FIG. 9 is a flowchart of an MCTP device list acquisition process according to the second embodiment. FIG. 10 is a hardware configuration diagram of an information processing apparatus.

Hereinafter, embodiments of an information processing apparatus, an information processing method, and an information processing program disclosed in the present application will be described in detail based on the drawings. The information processing apparatus, information processing method, and information processing program disclosed in the present application are not limited to the following embodiments.

FIG. 1 is a block diagram of an information processing device. The information processing device 1 has a CPU 11 , a PCH 12 , a PCIe slot 14 , a PCIe device 140 and a BMC 15 .

The PCIe device 140 is an IO (Input Output) device conforming to the PCIe standard, and is attached to the PCIe slot 14 . The PCIe devices 140 include devices that support MCTP and devices that do not support MCTP. All of the PCIe devices 140 connected to each PCIe slot 14 may support MCTP, may not support MCTP, or may be compatible with both MCTP and non-MCTP. A data bus connected to the PCIe slot 14 is hereinafter referred to as a PCIe bus. Also, the PCIe device 140 that supports MCTP may be called an MCTP device. This PCIe device 140 corresponds to an example of a “mounted device”. A function of performing MCTP communication corresponds to an example of the "predetermined communication function". Also, the MCTP device corresponds to an example of the "identified device".

The CPU 11 executes and operates a BIOS (Basic Input Output System) 110 when the information processing apparatus 1 is activated. BIOS 110 configures and manages peripherals including PCIe device 140 connected to PCIe slot 14 .

The BIOS 110 also recognizes peripheral devices including the PCIe device 140 connected to each PCIe slot 14 when the information processing apparatus 1 is activated. The BIOS 110 then transmits PCIe device information including various types of information about the recognized PCIe device 140 to the BMC 15 . For example, the BIOS 110 transmits PCIe device information to the BMC 15 using the IPMI command Set PCI Device Info.

The CPU 11 also operates an OS (Operating System). An agent operates on the OS. An agent operating on the OS and managing the PCIe slot 14 transmits PCIe device information to the BMC 15 when a hot-pluggable PCIe device 140 is connected to the PCIe slot 14 .

The PCIe device information includes, for example, information shown in format 201 shown in FIG. FIG. 2 is a diagram of an example of PCIe device information. The numbers on the left side of FIG. 2 represent the size of each piece of information in bytes. The PCIe device information transmitted by the BIOS 110 in this embodiment includes a PCI Vendor ID that is a vendor ID and a PCI Device ID that is a device ID, as shown in the format 201 of FIG. Furthermore, the PCIe device information includes the PCI physical address, which is the PCIe address, the firmware version of the PCIe device 140, and the firmware version length, as shown in the format 201 of FIG. For example, the PCIe device 140 includes a network adapter card.

The PCH 12 manages various data buses including the PCIe bus connected to the PCIe slot 14 . PCH 12 operates node manager 120 . PCH 12 communicates with CPU 11 regarding data bus management. This PCH 12 corresponds to an example of a "communication information management device".

The node manager 120 manages the PCIe bus, for example. The node manager 120 detects MCTP-compliant PCIe devices 140 among the PCIe devices 140 connected to the PCIe slots 14 connected to the PCIe bus. The node manager 120 obtains a device address representing the PCIe address of the PCIe slot 14 to which the detected MCTP device is connected. Then, the node manager 120 performs discovery processing to allocate communication identifiers used for direct communication between MCTP devices to the detected MCTP devices. The communication identifier is, for example, Endpoint ID. Then, the node manager 120 associates and stores each device address with the communication identifier assigned to the MCTP device having that device address. This communication identifier corresponds to an example of "communication information".

Further, the node manager 120 receives an MCTP device list acquisition request from the MCTP device list generator 154 . Then, the node manager 120 transmits to the MCTP device list generation unit 154 as an MCTP device list correspondence information between each held device address and the communication identifier assigned to the MCTP device having that device address. Here, the node manager 120 transmits the correspondence information it holds when receiving the request to acquire the MCTP device list. Therefore, if there is an MCTP device that has not undergone discovery processing, the information about that MCTP device is included in the MCTP device list. is not included. This node manager 120 corresponds to an example of an "allocation unit" and a "communication information management process."

The BMC 15 performs basic operations of the information processing apparatus 1 such as power management and status monitoring independently of the CPU 11 . For example, the BMC 15 performs MCTP communication with a PCIe device 140, which is an MCTP device, and collects data from the PCIe device 140. FIG. The BMC 15 according to this embodiment includes a predicted MCTP device list generation unit 151, a completion time calculation unit 152, an MCTP support status database 153, an MCTP device list generation unit 154, a process completion determination unit 155, a device management unit 156, and a delay timer 157. have. This BMC 15 corresponds to an example of a "management device". Also, various processes executed by the BMC 15 correspond to an example of a "management process".

The MCTP compatibility database 153 stores information for identifying MCTP devices. The MCTP compliance status database 153 includes, for example, specific information 202 shown in FIG. FIG. 3 is a diagram showing an example of the MCTP support status database. The MCTP compatibility database 153 has vendor IDs representing manufacturers of MCTP devices included in the specific information 202, PCI device IDs that are identification information of the MCTP devices, and information on firmware versions compatible with MCTP. If the vendor ID, PCI device ID, and firmware version of a given PCIe device 140 are registered in the MCTP support status database 153, that PCIe device 140 is an MCTP device. If the firmware version is "null", it means that there is no firmware version information, and that the PCIe device 140 supports MCTP regardless of the firmware version.

The predictive MCTP device list generation unit 151 receives input of PCIe device information of each PCIe device 140 connected to each PCIe slot 14 from the BIOS 110 after the information processing apparatus 1 is started. Specifically, the predictive MCTP device list generator 151 receives input of each information shown in the format 201 shown in FIG. 2 for each PCIe device 140 .

Next, the predicted MCTP device list generator 151 determines the PCIe slot 14 to which each PCIe device 140 is connected from the PCI physical address information included in the acquired PCIe device information. Furthermore, the predicted MCTP device list generation unit 151 acquires the vendor ID, device ID, and firmware version of each PCIe device 140 from the PCIe device information.

Next, the predicted MCTP device list generation unit 151 refers to the MCTP support status database 153, checks whether each PCIe device 140 supports MCTP, and identifies the MCTP device that is the PCIe device 140 that supports MCTP. . Then, the predicted MCTP device list generation unit 151 generates information representing the correspondence between the communication identifier and the physical address.

In this embodiment, the predicted MCTP device list generator 151 generates a predicted MCTP device list 203 as shown in FIG. 4, for example. FIG. 4 is a diagram showing an example of a predicted MCTP device list. MCTP Endpoint ID in the predicted MCTP device list 203 in FIG. 4 corresponds to a communication identifier. Also, the device address in the predicted MCTP device list 203 corresponds to the physical address of each MCTP device. Here, in this embodiment, the information of the PCH 12 on which the node manager 120 operates is registered in the No. 1 registration field in the predicted MCTP device list 203 . Since the PCH 12 MCTP Endpoint ID is fixed, it has already been registered in the initial state of the expected MCTP device list 203 . Further, in this embodiment, the information of the BMC 15 itself is registered in the second registration field in the predicted MCTP device list 203 . Since the discovery process for the BMC 15 has not been completed at the stage of generating the predicted MCTP device list 203, the MCTP Endpoint ID of the BMC 15 is unregistered.

A specific flow of processing for creating the predicted MCTP device list 203 will be described. The predicted MCTP device list generation unit 151 initializes the predicted MCTP device list 203 when the information processing apparatus 1 is activated. At the time of initialization, the predicted MCTP device list generator 151 may leave information about the PCH 12 . After that, the predicted MCTP device list generation unit 151 completes the predicted MCTP device list 203 by sequentially registering the device address of each MCTP device obtained from the BIOS 110 in the predicted MCTP device list 203 .

Predicted MCTP device list generation section 151 then outputs the generated predicted MCTP device list 203 to MCTP device list generation section 154 and completion time calculation section 152 . Here, predictive MCTP device list generating section 151 may notify completion time calculating section 152 of the number of MCTP devices registered in predictive MCTP device list 203 without transmitting predictive MCTP device list 203 . The predicted MCTP device list generation unit 151 corresponds to an example of the "specification unit".

Completion time calculator 152 receives input of predicted MCTP device list 203 from predicted MCTP device list generator 151 . The completion time calculator 152 obtains the number of MCTP devices installed in the information processing apparatus 1 excluding the PCH 12 from the obtained predicted MCTP device list 203 . Here, the completion time calculator 152 has in advance a predicted processing time that is predicted to be required for the discovery processing of one device. Therefore, the completion time calculator 152 multiplies the predicted processing time by the number of devices to obtain the predicted completion time from the completion of the discovery processing of the BMC 15 to the completion of the discovery processing of all remaining MCTP devices. After that, the completion time calculator 152 outputs the calculated estimated completion time to the process completion determination unit 155 . The completion time calculator 152 corresponds to an example of a "calculator". The predicted completion time corresponds to an example of "allocation time".

The processing completion determination unit 155 activates the delay timer 157 when the information processing apparatus 1 is activated. The delay timer 157 is a timer that measures the time that has elapsed since its activation. After that, the process completion determination unit 155 receives input of the estimated completion time from the completion time calculation unit 152 . Then, the process completion determination unit 155 acquires the elapsed time from the delay timer 157 as needed, and when the elapsed time reaches the estimated completion time, notifies the MCTP device list generation unit 154 of the elapse of the estimated completion time. The processing completion determination unit 155 corresponds to an example of a "determination unit".

The MCTP device list generator 154 receives input of the predicted MCTP device list 203 from the predicted MCTP device list generator 151 . Then, the MCTP device list generation section 154 waits until it receives from the MCTP device list generation section 154 notification that the estimated completion time has elapsed.

After that, upon receiving the notification that the estimated completion time has elapsed, the MCTP device list generation unit 154 transmits an MCTP device list acquisition request to the node manager 120 . After that, the MCTP device list generator 154 receives the MCTP device list from the node manager 120 .

Next, the MCTP device list generator 154 registers the communication identification information corresponding to the device address included in the received MCTP device list in the column of the same device address in the predicted MCTP device list 203 . Then, the MCTP device list generation unit 154 determines whether all the MCTP devices registered in the predicted MCTP device list 203 are present in the MCTP device list. When all the MCTP devices registered in the predicted MCTP device list 203 are present in the MCTP device list, the MCTP device list generation unit 154 acquires the registered predicted MCTP device list 203 as an MCTP device list. When the generation of the MCTP device list is completed, MCTP device list generation section 154 outputs the acquired MCTP device list to device management section 156 .

On the other hand, if there is an MCTP device registered in the predicted MCTP device list 203 that does not exist in the MCTP device list, the MCTP device list generation unit 154 sends an MCTP device list acquisition request to the node manager 120 again. Send. The MCTP device list generation unit 154 repeats the MCTP device list generation process until it acquires an MCTP device list in which all MCTP devices registered in the predicted MCTP device list 203 are present.

When repeating the MCTP device list generation process, the MCTP device list generation unit 154 acquires the number of retries. Also, the MCTP device list generation unit 154 uses its own clock to obtain the elapsed time from the initial acquisition of the MCTP device list. Here, the MCTP device list generation unit 154 has in advance a retry threshold value and a recoverable time that serve as criteria for error occurrence determination.

The MCTP device list generator 154 determines whether the number of retries exceeds the retry threshold. In addition, the MCTP device list generation unit 154 determines whether the elapsed time from acquisition of the first MCTP device list has exceeded the recoverable time. If the retry count does not exceed the retry threshold and the elapsed time does not exceed the recoverable time, the MCTP device list generation unit 154 repeats the MCTP device list generation processing.

On the other hand, if the number of retries exceeds the retry threshold or the elapsed time exceeds the recoverable time, the MCTP device list generation unit 154 determines that acquisition of the MCTP device list has failed, and starts the MCTP device list acquisition process. finish.

The device management section 156 receives input of the MCTP device list from the MCTP device list generation section 154 . After that, the device management unit 156 receives an inquiry about the PCIe device 140 for which MCTP communication is valid from the external management server 2 . Then, the device management unit 156 communicates with the MCTP devices registered in the MCTP device list using the communication identification information registered in the MCTP device list, and collects the information of each MCTP device. After that, the device management unit 156 transmits the collected information of each MCTP device to the management server 2 . This device management unit 156 corresponds to an example of a "control unit".

Next, the timing of the MCTP device list acquisition process by the BMC will be described with reference to FIG. FIG. 5 is a sequence diagram illustrating a process of acquiring an MCTP device list according to the first embodiment; Here, a case where MCTP devices #1 to #3 exist as MCTP devices will be described.

The BMC 15 undergoes discovery processing by the node manager 120 after the information processing device 1 is activated (step S101). As a result, the BMC 15 is assigned communication identification information.

Also, the BMC 15 receives the PCIe device information from the BIOS 110 (step S102).

After that, the BMC 15 calculates the predicted completion time and waits until the calculated predicted completion time to wait for the completion of the discovery process (step S103).

While the BMC 15 is waiting, the node manager 120 performs discovery processing for the MCTP device #1 and allocates and stores a communication identifier to the MCTP device #1 (step S104). The node manager 120 also performs discovery processing for MCTP device #2, and assigns and stores a communication identifier to MCTP device #2 (step S105). Further, the node manager 120 performs discovery processing for MCTP device #3, and assigns and stores a communication identifier to MCTP device #3 (step S106).

After that, the BMC 15 transmits an MCTP device list acquisition request to the node manager 120 (step S107).

The node manager 120 receives the MCTP device list acquisition request, and transmits to the BMC 15 the MCTP device list including the correspondence between the device addresses and communication identifiers of the stored MCTP devices #1 to #3 (step S108). The BMC 15 receives from the node manager 120 an MCTP device list in which information on all of the MCTP devices #1 to #3 installed in the information processing apparatus 1 is registered. After that, the MCTP device list generation unit 154 stops requesting the node manager 120 to acquire the MCTP device list.

On the other hand, there may be MCTP devices that are not registered in the MCTP device list acquired by the BMC 15 . Therefore, next, with reference to FIG. 6, the process of acquiring the MCTP device list when the discovery process is not completed during completion prediction will be described. FIG. 6 is a flowchart showing the MCTP device list acquisition process when the discovery process is not completed within the expected completion time. Here, too, the case where MCTP devices #1 to #3 exist as MCTP devices will be described.

The BMC 15 undergoes discovery processing by the node manager 120 after the information processing device 1 is activated (step S111).

Also, the BMC 15 receives the PCIe device information from the BIOS 110 (step S112).

After that, the BMC 15 calculates the predicted completion time and waits until the calculated predicted completion time to wait for the completion of the discovery process (step S113).

While the BMC 15 is waiting, the node manager 120 performs discovery processing for the MCTP device #1 and allocates and stores a communication identifier to the MCTP device #1 (step S114). The node manager 120 also performs discovery processing for MCTP device #2, and assigns and stores a communication identifier to MCTP device #2 (step S115). Furthermore, the node manager 120 performs discovery processing for MCTP device #3. However, in this case, an error occurs and the discovery process for MCTP device #3 is not completed (step S116).

After that, the BMC 15 transmits an MCTP device list acquisition request to the node manager 120 (step S117).

The node manager 120 receives the MCTP device list acquisition request, and transmits to the BMC 15 the MCTP device list including the stored correspondence between the device addresses and communication identifiers of the MCTP devices #1 and #2 (step S118). The BMC 15 receives from the node manager 120 an MCTP device list in which information on the MCTP devices #1 and #2 installed in the information processing apparatus 1 is registered.

However, at this stage, information about MCTP device #3 is not registered in the MCTP device list. Therefore, the BMC 15 detects that the MCTP device #3 registered in the expected MCTP device list 203 does not exist in the MCTP device list. Therefore, the BMC 15 retransmits the MCTP device list acquisition request to the node manager 120 (step S119).

The node manager 120 receives the MCTP device list acquisition request. Even at this timing, the node manager 120 has not completed the discovery process for MCTP device #3. Therefore, the node manager 120 transmits to the BMC 15 the MCTP device list including the stored correspondence between the device addresses and communication identifiers of the MCTP devices #1 and #2 (step S120). The BMC 15 receives from the node manager 120 an MCTP device list in which information on the MCTP devices #1 and #2 installed in the information processing apparatus 1 is registered.

Thereafter, the node manager 120 performs discovery processing for MCTP device #3, allocates and stores a communication identifier to MCTP device #3, and completes discovery processing for MCTP device #3 (step S121).

The BMC 15 detects again that the MCTP device #3 registered in the predicted MCTP device list 203 does not exist in the received MCTP device list. Therefore, the BMC 15 retransmits a request to obtain the MCTP device list to the node manager 120 (step S122).

The node manager 120 receives the MCTP device list acquisition request, and transmits the MCTP device list including the correspondence between the device addresses and communication identifiers of the stored MCTP devices #1 to #3 to the BMC 15 (step S123). The BMC 15 receives from the node manager 120 an MCTP device list in which information on all of the MCTP devices #1 to #3 installed in the information processing apparatus 1 is registered. After that, the MCTP device list generation unit 154 stops requesting the node manager 120 to acquire the MCTP device list.

Next, the flow of the MCTP device list acquisition process according to the first embodiment will be described with reference to FIG. FIG. 7 is a flowchart of an MCTP device list acquisition process according to the first embodiment.

When the information processing apparatus 1 is activated, the process completion determination unit 155 activates the delay timer 157 (step S201).

Next, the predicted MCTP device list generator 151 initializes the predicted MCTP device list 203 (step S202).

Next, the predicted MCTP device list generation unit 151 determines whether or not PCIe device information regarding all PCIe devices 140 has been acquired (step S203). If the PCIe device information about all the PCIe devices 140 has not been obtained (step S203: No), the predicted MCTP device list generation unit 151 continues obtaining the PCIe device information until the PCIe device information about all the PCIe devices 140 is obtained. repeat.

On the other hand, when PCIe device information on all PCIe devices 140 has been obtained (step S203: Yes), the predicted MCTP device list generation unit 151 selects one unselected one from among the PCIe devices 140 ( step S204).

Next, the predicted MCTP device list generation unit 151 determines whether information on the selected PCIe device 140 exists in the MCTP support status database 153 (step S205). If information on the selected PCIe device 140 does not exist (step S205: No), the predicted MCTP device list generation unit 151 determines that the selected PCIe device 140 does not support MCTP, and proceeds to step S209.

On the other hand, if information about the selected PCIe device 140 exists (Yes at step S205), the predicted MCTP device list generation unit 151 determines whether information about the firmware version exists in the predicted MCTP device list 203 (step S206).

If the firmware version information does not exist in the predicted MCTP device list 203 (step S206: NO), the predicted MCTP device list generator 151 determines that the selected PCIe device 140 supports MCTP. The predicted MCTP device list generation unit 151 then adds information about the selected PCIe device 140 to the predicted MCTP device list 203 (step S208).

On the other hand, if the firmware version information exists in the predicted MCTP device list 203 (step S206: YES), the predicted MCTP device list generator 151 regards that firmware version as the corresponding version. Then, the predicted MCTP device list generation unit 151 determines whether or not the firmware version of the selected PCIe device 140 is newer than the corresponding version (step S207).

If the firmware version of the selected PCIe device 140 is older than the supported version (step S207: No), the predicted MCTP device list generation unit 151 determines that the selected PCIe device 140 does not support MCTP, and proceeds to step S209. move on.

On the other hand, if the firmware version of the selected PCIe device 140 is newer than the supported version (step S207: Yes), the predicted MCTP device list generator 151 determines that the selected PCIe device 140 supports MCTP. . The predicted MCTP device list generation unit 151 then adds information about the selected PCIe device 140 to the predicted MCTP device list 203 (step S208).

After that, the predicted MCTP device list generation unit 151 determines whether or not the determination of the MCTP support status has been completed for all the PCIe devices 104 mounted on the information processing apparatus 1 (step S209). If there is an undetermined PCIe device 140 (step S209: NO), the predicted MCTP device list generation unit 151 returns the process to step S204.

On the other hand, when determination of all PCIe devices 140 is completed (Yes at step S209), the predicted MCTP device list generation unit 151 generates the predicted MCTP device list 203 as the MCTP device list generation unit 154 and the completion time calculation unit 152. Output to Completion time calculation unit 152 calculates the expected completion time of discovery processing for all MCTP devices using expected MCTP device list 203 (step S210). Thereafter, the completion time calculator 152 outputs the predicted completion time to the process completion determination unit 155 .

The processing completion determination unit 155 receives input of the estimated completion time from the completion time calculation unit 152 . Then, the processing completion determination unit 155 determines whether or not the delay timer 157 has exceeded the estimated completion time (step S211). 152 waits until the delay timer 157 exceeds the expected completion time. Also, the MCTP device list generation unit 154 receives input of the predicted MCTP device list 203 from the predicted MCTP device list generation unit 151 . After that, the MCTP device list generator 154 waits until it receives notification that the estimated completion time has elapsed.

If the estimated completion time has been exceeded (step S211: affirmative), the completion time calculation unit 152 notifies the MCTP device list generation unit 154 that the estimated completion time has elapsed. Upon receiving the notification of the estimated completion time from the process completion determination unit 155, the MCTP device list generation unit 154 requests the MCTP device list from the node manager 120 (step S212).

Upon receiving the MCTP device list acquisition request, the node manager 120 transmits the MCTP device list including the device addresses and communication identification information of the MCTP devices held at that time to the MCTP device list generator 154 . The MCTP device list generation unit 154 determines whether all MCTP devices in the predicted MCTP device list 203 are present in the MCTP device list (step S213). If all MCTP devices in the expected MCTP device list 203 are present in the MCTP device list (step S213: Yes), the MCTP device list generator 154 determines that the discovery process has been completed. Then, the MCTP device list generation unit 154 registers the communication identification information in the predicted MCTP device list 203 to generate and acquire the MCTP device list. After that, the MCTP device list generation unit 154 stops requesting the node manager 120 to acquire the MCTP device list.

On the other hand, if there is an MCTP device that does not exist in the MCTP device list (step S213: NO), the MCTP device list generator 154 acquires the number of retries and the elapsed time since the initial acquisition of the MCTP device list. The MCTP device list generation unit 154 then determines whether the number of retries exceeds the retry threshold or the elapsed time exceeds the recoverable time (step S215). If the number of retries does not exceed the retry threshold and the elapsed time does not exceed the recoverable time (step S215: No), the MCTP device list generator 154 returns the process to step S212.

On the other hand, if the number of retries exceeds the retry threshold or the elapsed time exceeds the recoverable time (step S215: Yes), the MCTP device list generation unit 154 determines that an MCTP device list acquisition error has occurred. (step S216). Then, the MCTP device list generation unit 154 ends the MCTP device list acquisition process.

As described above, the BMC of the information processing apparatus according to the present embodiment acquires information on the MCTP device installed in the information processing apparatus from the BIOS at startup. Then, the BMC predicts the MCTP device for which the node manager performs the discovery process using the acquired information of the MCTP device. After that, the BMC determines whether or not all the discovery processing has been completed by checking whether or not all the predicted MCTP devices are included in the MCTP devices notified by the node manager that have completed the discovery processing. If the discovery process is complete, the BMC can stop polling the MCTP device for requests to obtain information as it does not need to obtain any more information about the MCTP device from the node manager. Therefore, communication on the PCIe bus can be reduced, and the processing performance of the information processing device can be improved.

Next, Example 2 will be described. The information processing apparatus according to the present embodiment executes the MCTP device list acquisition process even when a PCIe device is added to a hot-pluggable PCIe slot after startup. The information processing apparatus according to this embodiment is also represented in FIG. In the following description, the description of the operation of each unit similar to that of the first embodiment will be omitted. In the following, a case where the PCIe device 140 is newly added in the activated state will be described. The PCIe slot 14 of the information processing device 1 supports hot plugging.

When a new PCIe device 140 is connected to the hot-pluggable PCIe slot 14 of the information processing apparatus 1 in operation, an agent that manages the PCIe slot 14 running on the OS executed by the CPU 11 receives the PCIe device information. Send to BMC15.

When a new PCIe device 104 is connected to the hot-pluggable PCIe slot 14, the predictive MCTP device list generation unit 151 receives input of PCIe device information of each PCIe device 140 connected to each PCIe slot 14 on the OS. received from agents working in

Next, the predicted MCTP device list generation unit 151 determines to which PCIe slot 14 each PCIe device 140 is connected from the PCI physical address information included in the acquired PCIe device information. Furthermore, the predicted MCTP device list generation unit 151 acquires the vendor ID, device ID, and firmware version of each PCIe device 140 from the acquired PCIe device information.

Next, the predicted MCTP device list generator 151 creates a predicted MCTP device list 203 by duplicating the MCTP device list. Next, the predicted MCTP device list generator 151 refers to the MCTP support status database 153 to check whether each PCIe device 140 supports MCTP, and identifies the MCTP device. The predicted MCTP device list generator 151 then refers to the predicted MCTP device list 203 to determine whether a new MCTP device has been added. If there is no newly added MCTP device, the predicted MCTP device list generation unit 151 finishes generating the predicted MCTP device list 203 . The BMC 15 ends the MCTP device list acquisition process.

On the other hand, if there is a newly added MCTP device, the predicted MCTP device list generation unit 151 registers correspondence information between the communication identifier and the physical address of the newly added MCTP device in the predicted MCTP device list 203. do. Then, predicted MCTP device list generation section 151 outputs updated predicted MCTP device list 203 to MCTP device list generation section 154 and completion time calculation section 152 .

The completion time calculation unit 152 holds the predicted MCTP device list 203 most recently acquired after the information processing apparatus 1 was started and before the addition of the MCTP device this time. Further, the completion time calculation unit 152 receives from the expected MCTP device list generation unit 151 input of the expected MCTP device list 203 updated by the addition of the MCTP device this time. Next, the completion time calculator 152 identifies the number of newly added MCTP devices. Completion time calculation section 152 then multiplies the number of newly added MCTP devices by the estimated processing time to calculate the estimated completion time for completing the discovery processing of all the newly added MCTP devices. After that, the completion time calculator 152 outputs the calculated estimated completion time to the process completion determination unit 155 .

The processing completion determination unit 155 activates the delay timer 157 when the PCIe device 140 is newly connected to the hot-pluggable PCIe slot 14 . After that, the process completion determination unit 155 receives input of the estimated completion time from the completion time calculation unit 152 . Then, when the time measured by the delay timer 157 reaches the estimated completion time, the process completion determination unit 155 notifies the MCTP device list generation unit 154 of the elapse of the estimated completion time.

The MCTP device list generator 154 receives from the predicted MCTP device list generator 151 input of the predicted MCTP device list 203 updated by adding a new MCTP device. After that, the predicted MCTP device list 203 waits until it receives notification from the process completion determination unit 155 that the predicted completion time has elapsed.

Upon receiving notification that the estimated completion time has elapsed from the process completion determination unit 155 , the MCTP device list generation unit 154 transmits an MCTP device list acquisition request to the node manager 120 . After that, the MCTP device list generator 154 receives the MCTP device list from the node manager 120 . Next, the MCTP device list generator 154 compares the acquired MCTP device list with the expected MCTP device list 203 . Then, the MCTP device list generation unit 154 determines whether information on all newly added MCTP devices exists in the MCTP device list.

When all the information of the newly added MCTP device exists in the MCTP device list, the MCTP device list generation unit 154 registers the communication identifier of the newly added MCTP device in the expected MCTP device list 203 . Then, the MCTP device list generation unit 154 acquires the registered predicted MCTP device list 203 as an MCTP device list. After that, MCTP device list generation section 154 outputs the MCTP device list to device management section 156 .

On the other hand, if there is a newly added MCTP device that does not exist in the MCTP device list, the MCTP device list generation unit 154 transmits an MCTP device list acquisition request to the node manager 120, and performs MCTP device list acquisition processing. repeat. At this time, if the number of retries exceeds the retry threshold or the elapsed time exceeds the recoverable time, the MCTP device list generation unit 154 determines that an error has occurred in the MCTP device list acquisition processing, and executes the processing. finish.

Next, with reference to FIG. 8, a process of acquiring an MCTP device list by the BMC 15 according to the second embodiment will be described. FIG. 8 is a sequence diagram illustrating an MCTP device list acquisition process according to the second embodiment. Here, a case will be described in which MCTP devices #1 to #3 exist as MCTP devices from the time the information processing apparatus 1 is started, and MCTP device #4 is added after the start.

The BIOS 110, BMC 15, node manager 120, and MCTP devices #1 to #3 execute various processes related to the MCTP device list acquisition process by the BMC 15 at startup (step S301).

Next, when the MCTP device #4 is newly connected to the hot-pluggable PCIe slot 14, the agent operating on the OS outputs PCIe device information to the BMC 15 (step S302).

After that, the BMC 15 calculates the predicted completion time and waits until the calculated predicted completion time to wait for the completion of the discovery process (step S303).

While the BMC 15 is waiting, the node manager 120 performs discovery processing for the MCTP device #4 and allocates and stores a communication identifier to the MCTP device #4 (step S304).

After that, the BMC 15 transmits an MCTP device list acquisition request to the node manager 120 (step S305).

The node manager 120 receives the MCTP device list acquisition request, and transmits to the BMC 15 the MCTP device list including the correspondence between the device addresses and communication identifiers of the stored MCTP devices #1 to #4 (step S306). The BMC 15 receives from the node manager 120 an MCTP device list in which all the information of the MCTP devices #1 to #4 installed in the information processing apparatus 1 are registered. After that, the MCTP device list generation unit 154 stops requesting the node manager 120 to acquire the MCTP device list.

Next, the flow of the MCTP device list acquisition process according to the second embodiment will be described with reference to FIG. FIG. 9 is a flowchart of an MCTP device list acquisition process according to the second embodiment.

When a new PCIe device 140 is connected to the hot-pluggable PCIe slot 14, the predicted MCTP device list generator 151 acquires the PCIe device information of the added PCIe device from the BIOS 110 (step S401).

Also, when a new PCIe device 140 is connected to the hot-pluggable PCIe slot 14, the processing completion determining unit 155 activates the delay timer 157 (step S402).

Next, the predicted MCTP device list generation unit 151 copies the MCTP device list to create the predicted MCTP device list 203 (step S403).

Next, the predicted MCTP device list generator 151 selects one unselected one from the added PCIe devices 140 (step S404).

Next, the predicted MCTP device list generation unit 151 determines whether or not information on the selected PCIe device 140 exists in the MCTP support status database 153 (step S405). If information on the selected PCIe device 140 does not exist (step S405: No), the predicted MCTP device list generation unit 151 determines that the selected PCIe device 140 does not support MCTP, and proceeds to step S409.

On the other hand, if information about the selected PCIe device 140 exists (Yes at step S405), the predicted MCTP device list generation unit 151 determines whether information about the firmware version exists in the predicted MCTP device list 203 (step S406).

If the firmware version information does not exist in the predicted MCTP device list 203 (step S406: NO), the predicted MCTP device list generator 151 determines that the selected PCIe device 140 supports MCTP. The predicted MCTP device list generation unit 151 then adds information about the selected PCIe device 140 to the predicted MCTP device list 203 (step S408).

On the other hand, if the firmware version information exists in the predicted MCTP device list 203 (step S406: YES), the predicted MCTP device list generator 151 regards that firmware version as the corresponding version. Then, the predicted MCTP device list generation unit 151 determines whether or not the firmware version of the selected PCIe device 140 is newer than the corresponding version (step S407).

If the firmware version of the selected PCIe device 140 is older than the supported version (step S407: No), the predicted MCTP device list generation unit 151 determines that the selected PCIe device 140 does not support MCTP, and proceeds to step S409. move on.

On the other hand, if the firmware version of the selected PCeI device 140 is newer than the supported version (step S407: Yes), the predicted MCTP device list generator 151 determines that the selected PCIe device 140 supports MCTP. . The predicted MCTP device list generation unit 151 then adds information about the selected PCIe device 140 to the predicted MCTP device list 203 (step S408).

After that, the predicted MCTP device list generation unit 151 determines whether or not the determination of the MCTP support status has been completed for all the PCIe devices 140 mounted on the information processing apparatus 1 (step S409). If there is an undetermined added PCIe device 140 (step S409: NO), the predicted MCTP device list generation unit 151 returns the process to step S404.

On the other hand, when the determination of all the added PCIe devices 140 is completed (step S409: YES), the predicted MCTP device list generation unit 151 updates the predicted MCTP device list 203 by adding a new MCTP device. (step 410). If the predicted MCTP device list 203 has not been updated (step S410: NO), the BMC 15 terminates the MCTP device list acquisition process.

On the other hand, if the predicted MCTP device list 203 has been updated (Yes at step S410), the predicted MCTP device list generator 151 sends the predicted MCTP device list 203 to the MCTP device list generator 154 and the completion time calculator 152. Output. The completion time calculation unit 152 compares the retained predictive MCTP device list 203 with the updated predictive MCTP device list 203 to obtain the number of added MCTP devices. Then, the completion time calculation unit 152 calculates the expected completion time of the discovery process for the added MCTP device using the number of added MCTP devices (step S411). Thereafter, the completion time calculator 152 outputs the predicted completion time to the process completion determination unit 155 .

The processing completion determination unit 155 receives input of the estimated completion time from the completion time calculation unit 152 . Then, the process completion determination unit 155 determines whether or not the delay timer 157 has exceeded the estimated completion time (step S412). If the predicted completion time has not been exceeded (step S412: No), the completion time calculator 152 waits until the delay timer 157 exceeds the predicted completion time. Also, the MCTP device list generation unit 154 receives input of the predicted MCTP device list 203 from the predicted MCTP device list generation unit 151 . After that, the MCTP device list generator 154 waits until it receives notification that the estimated completion time has elapsed.

If the estimated completion time has been exceeded (step S412: affirmative), the completion time calculator 152 notifies the MCTP device list generator 154 of the elapse of the estimated completion time. Upon receiving the notification of the estimated completion time from the process completion determination unit 155, the MCTP device list generation unit 154 requests the MCTP device list from the node manager 120 (step S413).

Upon receiving the MCTP device list acquisition request, the node manager 120 transmits the MCTP device list including the device addresses and communication identification information of the MCTP devices held at that time to the MCTP device list generator 154 . The MCTP device list generation unit 154 determines whether all the added MCTP devices in the predicted MCTP device list 203 are present in the MCTP device list (step S414).

If all the added MCTP devices are present in the MCTP device list (step S414: Yes), the MCTP device list generator 154 determines that the discovery process has been completed. Then, the MCTP device list generation unit 154 generates an MCTP device list by registering the communication identification information of the MCTP device added to the predicted MCTP device list 203 (step S415). After that, the MCTP device list generation unit 154 stops requesting the node manager 120 to acquire the MCTP device list.

On the other hand, if there is an added MCTP device that does not exist in the MCTP device list (step S414: NO), the MCTP device list generator 154 acquires the number of retries and the elapsed time since the initial acquisition of the MCTP device list. do. The MCTP device list generator 154 then determines whether the number of retries exceeds the retry threshold or the elapsed time exceeds the recoverable time (step S416). If the retry count does not exceed the retry threshold and the elapsed time does not exceed the recoverable time (step S416: No), the MCTP device list generator 154 returns the process to step S413.

On the other hand, if the number of retries exceeds the retry threshold or the elapsed time exceeds the recoverable time (step S416: Yes), the MCTP device list generation unit 154 determines that an MCTP device list acquisition error has occurred. (step S417). Then, the MCTP device list generation unit 154 ends the MCTP device list acquisition process.

Although the information processing apparatus 1 having the hot-pluggable PCIe slot 4 has been described in this embodiment, the configuration of the PCIe device 140 is basically unchanged. Therefore, in the case of the information processing apparatus 1 that does not have the hot-pluggable PCIe slot 4, the BMC 15 does not need to update the MCTP device list afterward if the acquisition of the MCTP device list is completed at the time of startup.

As described above, the BMC of the information processing apparatus according to the present embodiment acquires PCIe device information from the agent operating on the OS when a new PCIe device is added to the hot-pluggable PCIe slot. . Then, based on the obtained PCIe device information, the BMC predicts the MCTP devices whose communication identification information is notified from the node manager, and determines whether or not discovery processing for all newly added MCTP devices has been completed. do. When confirming the completion of the discovery process, the BMC can stop polling for requests to obtain information about the MCTP devices since it does not need to obtain any more information about the MCTP devices from the node manager. Therefore, even in the update process of the MCTP device list in which a new MCTP device is added to the hot plug, the processing performance of the information processing apparatus can be improved by reducing the communication on the PCIe bus.

(Hardware configuration)
Next, a hardware configuration of the information processing apparatus 1 according to each embodiment will be described with reference to FIG. FIG. 10 is a hardware configuration diagram of an information processing apparatus.

The information processing apparatus 1 has a CPU 11, a PCH 12, a BMC 15, a memory 16, a NIC (Network Interface Card) 161 and an SSD (Solid State Drive) 162, as shown in FIG. The CPU 11 and memory 16 are connected via a channel 22 . The CPU 11 is also connected to the PCH 12 , BMC 15 , NIC 161 and SSD 162 via the PCIe bus 21 .

The NIC 161 is an interface for communicating with external devices such as the management server 2 . The SSD 162 is an auxiliary storage device. The NIC 161 and SSD 162 are actually connected to the PCIe bus 21 by being connected to the PCIe slot 14 shown in FIG. Also, the SSD 162 stores various programs that implement functions such as the BIOS 110 and an OS (Operating System).

The CPU 11 develops various programs stored in the SSD 162 in the memory 16 and executes them, thereby realizing functions of the BIOS 110 and the OS.

The PCH 12 has a processor and memory inside. A program for operating the node manager 120 is stored in the internal memory of the PCH 12 . The processor inside the PCH 12 implements the functions of the node manager 120 by executing a program that is stored in the internal memory and causes the node manager 120 to operate.

The BMC 15 has a processor and memory inside. The functions of the predictive MCTP device list generation unit 151, the completion time calculation unit 152, the MCTP device list generation unit 154, the processing completion determination unit 155, and the device management unit 156 illustrated in FIG. 1 are realized in the memory inside the BMC 15. Various programs are stored, including programs that Also, the internal memory of the BMC 15 implements the functions of the MCTP compatibility status database 153 illustrated in FIG. A processor inside the BMC 15 executes various programs stored in an internal memory to generate a predicted MCTP device list generation unit 151, a completion time calculation unit 152, an MCTP device list generation unit 154, a process completion determination unit 155, and a device management unit. The function of the part 156 is realized. In this way, the programs that implement the functions of the predicted MCTP device list generation unit 151, the completion time calculation unit 152, the MCTP device list generation unit 154, the processing completion determination unit 155, and the device management unit 156 are stored in the storage medium and executed. By doing so, the function is realized. More specifically, the process of receiving device information from the BIOS 110 by the predicted device list generator 151 is the IPMI management process executed by the BMC 15 . The MCTP management process performed by the predictive MCTP device list generation unit 151, the completion time calculation unit 152, the MCTP device list generation unit 154, and the processing completion determination unit 155 is an MCTP agent process.

1 information processing device 2 management server 11 CPU
12PCH
14 PCIe slot 15 BMC
140 PCIe device 151 Predicted MCTP device list generation unit 152 Completion time calculation unit 153 MCTP support status database 154 MCTP device list generation unit 155 Processing completion determination unit 156 Device management unit 157 Delay timer 203 Predicted MCTP device list

Claims (6)

One or more devices having a communication function that acquires information on one or more on-board devices from the BIOS (Basic Input Output System) and communicates from among the on-board devices using MCTP (Management Component Transport Protocol) an identification part that identifies the
an allocation unit that detects one or more devices having a communication function for communicating using MCTP from among the mounted devices, and sequentially allocates communication information used for communication using the MCTP to the detected devices; ,
an acquiring unit that repeatedly acquires the communication information from the assigning unit until the communication information assigned to all of the devices included in the device list specified by the specifying unit is acquired. information processing equipment. an identification unit that acquires information on one or more mounted devices from the BIOS and identifies one or more devices having a predetermined communication function from among the mounted devices;
an allocation unit that detects one or more devices having a predetermined communication function from among the mounted devices and sequentially allocates communication information to the detected devices;
a calculation unit that calculates an allocation time required until allocation of the communication information by the allocation unit to all of the devices identified by the identification unit is completed;
a determination unit that determines whether the allocation time calculated by the calculation unit has elapsed;
When the determination unit determines that the allocation time has passed, acquisition of the communication information from the allocation unit is started, and all of the devices included in the list of the devices specified by the specification unit. and an acquisition unit that repeats acquisition of the communication information until the communication information assigned to is acquired. 3. The specifying unit according to claim 1 , wherein when the mounted device is added, the identification unit acquires information about the mounted device from an agent, which is a management application for the mounted device and runs on an OS (Operating System). information processing equipment. 4. The information according to any one of claims 1 to 3, further comprising a control unit that controls the device specified by the specifying unit using the communication information acquired by the acquiring unit. processing equipment. cause a management device to acquire information on one or more mounted devices from the BIOS, and identify one or more devices having a communication function for communicating using MCTP from among the mounted devices;
causing the communication information management apparatus to detect one or more devices having a communication function for communicating using MCTP from among the installed devices, and assigning communication information used for communication using the MCTP to the detected devices are executed sequentially,
causing the management device to repeatedly acquire the communication information from the communication information management device until the communication information assigned to all of the devices included in the specified device list is acquired. Processing method. cause a management process to acquire information of one or more on-board devices from the BIOS and specify one or more devices having a communication function to communicate using MCTP from among the on-board devices;
causing the communication information management process to detect one or more devices having a communication function for communicating using MCTP from among the installed devices, and assigning communication information used for communication using the MCTP to the detected devices are executed sequentially,
causing a computer to execute a process of causing the management process to repeatedly acquire the communication information from the communication information management process until the communication information assigned to all of the devices included in the identified device list is acquired; An information processing program characterized by:

Images