JP2024015747A - Information processing device, bios log management program and bios log management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce computer startup time.

SOLUTION: An information processing device 1 includes a plurality of partial storage areas obtained by dividing a storage area for storing logs of a BIOS, changes a partial storage area for recording the logs of the BIOS each time the BIOS is started, records the logs of the BIOS in the changed partial storage area, and secures, if it is determined that there is no partial storage area, in which the logs can be recorded without erasing the logs, among the plurality of partial storage areas after the BIOS is started and while an OS is operating, a new partial storage area by erasing the logs in a partial storage area with an old log record.

SELECTED DRAWING: Figure 2

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to an information processing device and the like.

BIOS (Basic Input/Output System) is firmware built into a computer's motherboard or system board. When the computer is powered on, the BIOS initializes the CPU (Central Processing Unit), memory, etc., and then starts and operates the OS (Operating System). Additionally, during this time, the BIOS can save the computer status and the like as a log.

Further, BMC (Baseboard Management Controller) is firmware for remotely managing computers. BMC manages BIOS logs as one of its functions. In recent years, there are computer models that are not equipped with a BMC in order to keep prices down. In the case of a model that is not equipped with a BMC, the BIOS must manage logs.

However, the storage area that the BIOS can access is limited, and currently only a portion of the BIOS log can be stored. BIOS logs are used for fault investigation such as identifying the cause of errors, so if only a portion of them can be saved, analysis will take time.

Since the storage area for BIOS logs is limited, the BIOS logs are erased. That is, the BIOS log is written to the flash memory, but due to the characteristics of the flash memory, it cannot be overwritten during writing, and if it is to be overwritten, it must be erased. Since erasing logs takes time, currently, the erasure process is often performed when the BIOS is started.

Japanese Patent Application Publication No. 2001-067229 Japanese Patent Application Publication No. 2016-181106

However, even in a computer without a BMC, it is necessary to manage all BIOS logs. Therefore, the amount of log writing increases. Therefore, it is necessary to erase old logs each time the BIOS is started, and the BIOS startup time increases compared to the case where only a portion of the log is written. As a result, there is a problem in that the startup time of the computer increases.

One aspect of the present invention is to reduce the startup time of a computer that does not include a BMC.

In one aspect, the information processing device includes a plurality of partial storage areas obtained by dividing a storage area for storing BIOS logs, and a changing unit that changes the partial storage area for recording the BIOS logs each time the BIOS is started. , a recording unit that records the log of the BIOS in the partial storage area changed by the changing unit; and a recording unit that records the log of the BIOS in the partial storage area changed by the changing unit; If it is determined that there is no partial storage area in which logs can be recorded, the erasing unit erases the log of the partial storage area with old log records to secure a new partial storage area.

According to one aspect, the computer startup time can be shortened in a computer not equipped with a BMC.

FIG. 1 is a diagram illustrating an example of the flow of BIOS log management processing according to the embodiment. FIG. 2 is a block diagram showing the functional configuration of an information processing device including a BIOS log management unit according to an embodiment. FIG. 3A is a diagram (1) showing the concept of write management according to the embodiment. FIG. 3B is a diagram (2) showing the concept of write management according to the embodiment. FIG. 4 is a diagram illustrating an example of the configuration of a management table according to the embodiment. FIG. 5 is a diagram illustrating an example of the configuration of an area management table according to the embodiment. FIG. 6 is a diagram illustrating an example of the flow of log deletion processing during OS operation according to the embodiment. FIG. 7 is a diagram illustrating an example of a flowchart of processing at the time of starting the BIOS according to the embodiment. FIG. 8 is a diagram illustrating an example of a flowchart of deletion processing during OS operation according to the embodiment. FIG. 9 is a diagram illustrating an example of a flowchart of processing when an error occurs according to the embodiment. FIG. 10 is a diagram illustrating an example of a computer that executes a BIOS log management program.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Examples of an information processing apparatus, a BIOS log management program, and a BIOS log management method disclosed in the present application will be described in detail below with reference to the drawings. Note that this invention is not limited to the examples.

[Flow of BIOS log management processing]
FIG. 1 is a diagram illustrating an example of the flow of BIOS log management processing according to the embodiment. As shown in FIG. 1, the information processing device 1 includes Firmware 10, an OS 20, a CPU/Chip Set 30, and an SPI Flash 40. Firmware 10 includes a BIOS log management section 11. The CPU/Chip Set 30 includes an SMM (System Management Mode) management section 31 . The SPI Flash 40 includes a BIOS log area 41. The BIOS log area 41 is a storage area for storing BIOS logs, and is divided into a plurality of areas. Hereinafter, each area into which the log area 41 is divided may be referred to as a log partial area.

When the BIOS is started, the BIOS instructs the SMM management unit 31 to initialize once at boot time (<1>), and the SMM management unit 31 accepts the initialization instruction. Initialization here refers to erasing data in the log area 41. Further, when an error occurs, the SMM management unit 31 accepts that an error has occurred (<2>). The SMM referred to here is a mode that can be used only by the BIOS, and is also a mode that can provide an environment independent from the OS. Upon receiving the initialization instruction and the error occurrence, the SMM management unit 31 issues an SMI (System Management Interrupt) indicating a hardware interrupt with the highest priority (<3>), and the BIOS mode becomes SMM. The BIOS (SMM) whose mode has become SMM instructs the log management unit 11 to initialize and write an error log (<4>). The log management unit 11 writes the initialization data or the error log to a designated writing location (log partial area) in the divided log area 41 (<5>).

Regarding logs other than error logs, the BIOS instructs the log management unit 11 to write all logs at boot or runtime (<1'>), and the log management unit 11 writes all logs. Accepts writing. The log management unit 11 that has received the writing of all logs writes the logs to the designated writing location (partial log area) in the divided log area 42 (<2'>). That is, when the log management unit 11 receives a log write instruction from the BIOS (Boot, Runtime) or the BIOS (SMM), the log management unit 11 writes the log in a specified partial log area space of the divided log area 41. Write.

Further, the BIOS processes according to the BIOS Menu at the time of booting (<11>). The BIOS Menu refers to a BIOS setting screen, and is a Menu in which, for example, a corresponding location (partial log area) for initializing the log area 41 can be specified. According to the BIOS Menu, the log management unit 11 erases (initializes) the corresponding part (partial log area) of the log area 41 if necessary (<12>). In other words, the BIOS log is written to flash memory (for example, SPI (Serial Peripheral Interface) Flash), but due to the characteristics of flash memory, it cannot be overwritten when writing, and when it is overwritten, it must be erased (initialized). There is a need to. Since erasing takes time, if there is no partial log area where logs can be recorded without erasing them when booting the BIOS, the corresponding part of the log area 41 (partial log area) should be erased. do.

In addition, if there is no partial log area in which logs can be recorded without erasing them after startup and while the OS is running (operation), the BIOS stores the data in the oldest log partial area. to create new space for recording logs. Since erasing takes time, the BIOS erases data in any partial log area of the log area 41 after startup and while the OS is in operation. Note that the flow of the erasing process performed after the BIOS is started and while the OS is in operation will be described later.

[Functional configuration of BIOS log management section]
Here, the functional configuration of the information processing device 1 including the BIOS log management section 11 will be described with reference to FIG. 2. FIG. 2 is a block diagram showing the functional configuration of an information processing device including a BIOS log management unit according to an embodiment. As shown in FIG. 2, the information processing device 1 includes a BIOS log management section 11, a storage section 12, and an SPI Flash 40.

A BIOS log area 41 is secured in the SPI Flash 40. The BIOS log area 41 includes a plurality of divided partial log areas. Note that in FIG. 2, the BIOS log area 41 is divided into four parts, but is not limited to this, and may be divided into a plurality of partial log areas.

The storage unit 12 has a management table 121 and an area management table 122. The management table 121 is a table used to manage the BIOS log area 41 within the SPI Flash 40. Further, the area management table 122 is a table for managing each partial log area obtained by dividing the log area 41 of the BIOS. Note that the partial log area is an example of a partial storage area. Further, an example of each configuration of the management table 121 and the area management table 122 will be described later.

The log management section 11 includes a distribution processing section 111 , a compression management section 112 , a cryptographic compression processing section 113 , a compression processing section 114 , a write management section 115 , and a write processing section 116 . Note that the write management section 115 is an example of a changing section, a recording section, and an erasing section. The write processing unit 116 is an example of a recording unit.

The distribution processing unit 111 distributes the BIOS logs. The BIOS log contains information that cannot be made public. Therefore, when the distribution processing unit 111 receives a log write instruction from the BIOS at boot time or the BIOS (SMM), the distribution processing unit 111 distributes the logs into private logs and logs other than private logs.

The compression management unit 112 manages compression of BIOS logs for each assigned log. For example, if the log is classified as a private log, the compression management unit 112 causes the cryptographic compression processing unit 113 to perform compression processing on the log when the capacity of the private log reaches a predetermined capacity. In addition, if the log classification is a log other than a private log, the compression management unit 112 causes the compression processing unit 114 to perform compression processing on the log when the capacity of the log other than the private log reaches a predetermined capacity. .

The cryptographic compression processing unit 113 performs cryptographic compression processing on the private log. The compression processing unit 114 performs compression processing on logs other than private logs.

The write management unit 115 specifies a partial log area in the log area 41 and manages log writing every time the BIOS is started. For example, the write management unit 115 uses the management table 121 to change the partial log area in which the BIOS log is written each time the BIOS is started. Then, the write management unit 115 instructs the write processing unit 117 to write the BIOS log in the partial log area to be changed.

Further, the write management unit 115 erases data in a specified partial log area of the divided log area 41 after the BIOS is started and while the OS is in operation. That is, the write management unit 115 initializes the specified partial log area after the BIOS is started and while the OS is operating. For example, the write management unit 115 uses the management table 121 to determine whether logs are recorded in all of the plurality of partial log areas. That is, the write management unit 115 determines whether there is any partial log area in which a log can be recorded without erasing the log among the plurality of partial log areas. When the write management unit 115 determines that logs are recorded in all of the plurality of partial log areas, the write management unit 115 uses the management table 121 to perform the following processing. The write management unit 115 erases the data in the partial log area in which the oldest log has been written, which is the partial log area excluding the partial log area written when an error occurred in the log area 41. , instructs the write processing unit 116.

Note that the write management unit 115 may not be able to erase all of a specific partial log area after the BIOS is started and while the OS is in operation. For example, this is the case when the OS is under load. In such a case, the write management unit 115 may use the management table 121 to erase the remaining part of the specific partial log area that could not be erased the next time the BIOS is started.

The write processing unit 116 writes the BIOS log in the partial log area changed and designated by the write management unit 115. Furthermore, the write processing unit 116 erases data in the partial log area that is instructed to be erased by the write management unit 115.

[Write management concept]
Here, the concept of write management performed by the write management unit 115 will be explained with reference to FIGS. 3A and 3B. 3A and 3B are diagrams illustrating the concept of write management according to the embodiment. The BIOS log area 41 shown in FIGS. 3A and 3B is divided into four areas. Each partial log area shall be written as 41-1, 41-2, 41-3, and 41-4. The partial log area 41-3 holds (DataStored) the previous and previous startup logs, the partial log area 41-4 holds the previous and previous startup logs, and the partial log area 41-1 stores the previous and previous startup logs. Keeps startup logs. Neither partial log area is a log when an error occurs. Here, an example will be described in which a log is written in the partial log area 41-2 when the BIOS is started.

When the BIOS is started, the write management unit 15 confirms that no log is held (DataStored) in the partial log area 41-2. If the write management unit 15 holds logs in the partial log area 41-2, other partial log areas also already hold logs, so the write management unit 15 erases the data when the BIOS is started. After erasing the data, the write management unit 15 writes the log to the partial log area 41-2. On the other hand, if the write management unit 15 does not hold any logs in the partial log area 41-2, it writes the logs in the partial log area 41-2.

The partial log area 41-3 is the area in the log area 41 where logs are written the oldest. Therefore, since logs are recorded in all of the plurality of partial log areas, the write management unit 115 erases the data after the BIOS is started and while the OS is operating. Thereafter, the write management unit 115 can write the log to the partial log area 41-3 from which the data has been erased the next time the BIOS is started. In this way, by erasing data in the partial log area during OS operation, the write management unit 115 can rotate the partial log area in which logs are written and write logs each time the BIOS is started. can. In addition, the write management unit 115 can shorten the time it takes to start up the computer next time by erasing data in the partial log area while the OS is operating.

Assume that an error occurs while writing a log to the partial log area 41-2 when the BIOS is started. Then, the write management unit 115 retains the error log by removing the partial log area 41-2 from rotation every time the BIOS is started. The write management unit 115 continues rotation of partial log areas other than the partial log area 41-2. In other words, the write management unit 115 plans to write a log into the partial log area 41-3 from which data was erased during operation of the OS when the BIOS is started next time. Further, since the data in the partial log area 41-3 was erased during operation of the OS, the partial log area 41-4 becomes the area in the log area 41 where logs are written the oldest. Therefore, if logs are recorded in all of the plurality of partial log areas, the write management unit 115 plans to erase the data in the partial log area 41-4 after the BIOS is started and while the OS is operating. do.

FIG. 3B shows a case where logs when an error occurs are held in a plurality of partial log areas. The upper diagram of FIG. 3B shows a case where logs when an error occurs are held in two partial log areas 41-4 and 41-2. In such a case, the write management unit 115 continues rotation of the partial log areas 41-1 and 41-3 other than the partial log areas 41-2 and 41-4.

The lower diagram of FIG. 3B shows a case where logs when an error occurs are held in three partial log areas 41-4, 41-2, and 41-3. In such a case, the write management unit 115 confirms that no log is held in the partial log area 41-1 at the time of BIOS startup, and if the log is held, the write management unit 115 deletes the data before writing the partial log area 41-1. After deleting the , write the log. On the other hand, if the write management unit 15 does not hold any logs in the partial log area 41-1, it continues writing the logs into the partial log area 41-1.

[Example of management table configuration]
Here, an example of the configuration of the management table 121 according to the embodiment will be described with reference to FIG. 4. FIG. 4 is a diagram illustrating an example of the configuration of a management table according to the embodiment. As shown in FIG. 4, the management table 121 stores TableWriting, TableInit, TableInitializing, TableCount, TableMask, TablesDataStored, and FlashManagementTableList in association with each other.

TableWriting is used to specify the partial log area where logs are being written. TableWriting has a length of 1 byte, and each bit is associated with each partial log area. As an example, in the example of FIGS. 3A and 3B, when the partial log area 41-2 is writing a log, TableWriting stores "01000000".

TableInit is used to specify the partial log area to be initialized. TableInit is 1 byte long and associates each bit with each partial log area. As an example, in the example of FIGS. 3A and 3B, when the partial log area 41-3 is the target to be initialized (erased), TableInit stores "00100000".

TableInitializing is used to select a partial log area to be initialized. TableInitializing is 1 byte long and associates each bit with each partial log area. TableCount stores the total number of available partial log areas. In the example of FIGS. 3A and 3B, TableCount stores "4". TableMask is used to specify the partial log area to be masked. TableMask is 1 byte long and associates each bit with each partial log area. The term "mask" here refers to holding so that it cannot be overwritten after writing. For example, the masked partial log area is the area where the log was saved when an error occurred.

TablesDataStored is used to specify a partial log area that stores log data. TablesDataStored is 1 byte long, and each bit is associated with each partial log area. As an example, in the example of FIGS. 3A and 3B, if the partial log areas 41-1, 41-3, and 41-4 store log data, TablesDataStored stores "10110000". FlashManagementTableList stores the address of each area management table 122. Note that TableInit and TableMask are linked to the values indicated by the BIOS menu.

[Example of area management table configuration]
Here, an example of the configuration of the area management table 122 according to the embodiment will be described with reference to FIG. 5. The area management table 122 exists as many as the number of partial log areas obtained by dividing the log area 41. FIG. 5 is a diagram illustrating an example of the configuration of an area management table according to the embodiment. As shown in FIG. 5, the area management table 122 stores FlashID, CountStartUp, DataStartAddress, and DataLength in association with each other.

FlashID is an ID for distinguishing partial log areas. CountStartUp is a counter that indicates how many times the BIOS has been started since the log was stored. If it is the latest BIOS startup log, "0" is set, and if the area is not initialized, the count is incremented each time the BIOS is started. DataStartAddress is the address where log data is saved. DataLength is the size of the log data storage destination.

[Flow of log deletion process during OS operation]
Here, the flow of log deletion processing during OS operation according to the embodiment will be described with reference to FIG. 6. FIG. 6 is a diagram illustrating an example of the flow of log deletion processing during OS operation according to the embodiment. As shown in FIG. 6, during OS operation, the log management unit 11 uses ACPI (Advanced Programmable Interrupt Controller) to erase (initialize) data in the log area 41 of the BIOS. ACPI is used because it is possible to enter SMM using ACPI's AML (ACPI Machine Language). By entering SMM, it is possible to interrupt the log management section 11 of the BIOS during operation of the OS.

For example, the BIOS (Sweep) operates the ACPI Register area 32 of the CPU/Chip Set 30 in order to call the ACPI Driver 21 some time after the OS is started (<21>). Since the ACPI Register area 32 has been operated, the CPU/Chip Set 30 issues an SCI (System Control Interrupt) (<22>). SCI is a hardware interrupt for notifying the OS of ACPI events. The ACPI Driver 21 receives the SCI, executes Handler processing (<23>), and calls the specified AML. AML operates the SMM Register area 33 to call the SMM (<24>). Since the SMM Register area 33 has been operated, the CPU/Chip Set 30 issues an SMI (<25>). The BIOS (SMM) receives the SMI, becomes an SMM, and requests the BIOS log management unit 11 to delete the BIOS log (<26>).

The log management unit 11 of the BIOS erases (initializes) the corresponding part (partial log area) of the log area 41 of the BIOS (<27>). For example, the write management unit 115 in the log management unit 11 uses the management table 121 to determine whether logs are recorded in all of the plurality of partial log areas obtained by dividing the log area 41. If the write management unit 115 determines that logs are recorded in all of the plurality of partial log areas, the write management unit 115 uses the management table 121 to exclude the partial log area written when the error occurred. The write processing unit 116 is instructed to erase the data in the partial log area in which the oldest log has been written among the partial log areas. Then, the write processing unit 116 erases the data in the specified partial log area. Note that the write management unit 115 may not be able to erase all of a specific partial log area during operation of the OS. In such a case, the write management unit 115 may use the management table 121 to erase the remaining part of the specific partial log area that could not be erased the next time the BIOS is started.

Thereby, by erasing the partial log area of the BIOS during operation of the OS, the log management unit 11 can suppress the process of erasing the partial log area of the BIOS when the BIOS is started next time. As a result, the log management unit 11 can shorten the computer startup time.

[Flowchart of processing at BIOS startup]
FIG. 7 is a diagram illustrating an example of a flowchart of processing at the time of starting the BIOS according to the embodiment. Note that in FIG. 7, it is assumed that the BIOS has been started.

When the BIOS is started, the log management unit 11 acquires the management table 121 (step S11). The log management unit 11 initializes TableWriting of the management table 121 to "0" (step S12). That is, the log management unit 11 initializes TableWriting to "0" because there is currently no partial log area to write a log to.

The log management unit 11 adds the Mask location specified in the BIOS Menu to TablesMask of the management table 121 (step S13). In the BIOS Menu, when a user wants to hold (mask) data in a specific partial log area, the partial log area to be held is specified. The log management unit 11 obtains the BIOS Menu and sets the Mask location specified in the BIOS Menu to TablesMask.

The log management unit 11 determines whether there is an area management table 122 in which the management table 121 has Mask=0 and DataStored=0 (step S14). That is, the log management unit 11 determines whether or not there is no partial log area to be held (masked) and there is a partial log area that does not contain data. In other words, the log management unit 11 determines whether there is a target for a partial log area that can be written immediately without erasing the partial log area. If it is determined that there is an area management table 122 with Mask=0 and DataStored=0 (step S14; Yes), the log management unit 11 stores a partial log corresponding to the area management table 122 with Mask=0 and DataStored=0. The process moves to step S25 to write the log in the area.

On the other hand, if it is determined that there is no area management table 122 with Mask = 0 and DataStored = 0 (step S14; No), the log management unit 11 sets the initialization target location specified in the BIOS Menu to TablesInit of the management table 121. is written (step S15). In the BIOS Menu, if the user wants to erase a specific partial log area, the partial log area to be erased is specified. The log management unit 11 obtains the BIOS Menu and sets the initialization area specified in the BIOS Menu in TableInit.

The log management unit 11 determines whether there is an area management table 122 with Mask=0 (step S16). That is, the log management unit 11 uses the TablesMask of the management table 121 to determine whether there is any log area 41 that is not maintained (masked). If it is determined that there is an area management table 122 with Mask=0 (step S16; Yes), the log management unit 11 identifies the area management table 122 with Mask=0 and the maximum Count of the management table 121, and TablesInit The corresponding bit is set (step S17). That is, the log management unit 11 identifies the partial log area in which the oldest log has been written, excluding the retained (masked) partial log area, and sets it as the target for deletion. The log management unit 11 then proceeds to step S19 to proceed to the deletion process.

On the other hand, if it is determined that there is no area management table 122 with Mask=0 (step S16; No), the log management unit 11 checks whether there is a partial log area specified to be initialized in the BIOS Menu. Determination is made (step S18). In the BIOS Menu, if the user wants to erase a specific partial log area, the partial log area to be erased is specified. The log management unit 11 determines whether there is a partial log area that the user wants to erase. If it is determined that there is no partial log area designated to be initialized in the BIOS Menu (step S18; No), the log management unit 11 ends the BIOS startup process without performing the deletion process.

On the other hand, if it is determined that there is a partial log area designated to be initialized in the BIOS Menu (step S18; Yes), the log management unit 11 moves to step S19 to perform deletion processing.

In step S19, the log management unit 11 performs steps S20 to S23 until there are no bits set in TablesInit of the management table 121 (steps S19 and S24). That is, the log management unit 11 performs a process of erasing the target partial log area corresponding to the bit set in TablesInit.

The log management unit 11 selects one of the bits set in TalbesInit of the management table 121, and sets "1" to the corresponding bit in TableInitializing (step S20). That is, it is assumed that the log management unit 11 selects one partial log area to be erased and is in the process of initializing it.

Then, the log management unit 11 specifies the data range from the Data Start Address and Data Length for the area management table 122 in which TableInitializing of the management table 121 is "1", and performs deletion processing (step S21). That is, the log management unit 11 deletes data in the partial log area specified from TableInitializing.

After confirming the EndFlag of the erasing process, the log management unit 11 sets the corresponding bit of DataStored in the management table 121 to 0, and also sets the corresponding bits of TablesInit and TableInitializing to 0 (step S22). That is, when the deletion process is completed, the log management unit 11 sets the corresponding location in the management table 121 to a state in which no data is stored and the log deletion has been completed for the partial log area for which the deletion process has been completed.

Then, the log management unit 11 sets CountStartUp in the corresponding area management table 122 to "0" (step S23). That is, the log management unit 11 initializes the number of activations of the target partial log area. The log management unit 11 then proceeds to step S24 and step S19.

When there are no bits set in TablesInit of the management table 121, the log management unit 11 adds 1 to all CountStartUps in the area management table 122 where Mask=0 and DataStored=1 in the management table 121 (step S25). That is, the log management unit 11 adds 1 to the number of times the BIOS has been started for the partial log area that contains data, not for retention (mask).

The log management unit 11 selects one area management table 122 in which Mask=0 and DataStored=0 in the management table 121, and sets "1" to the corresponding bit of TableWriting (step S26). That is, the log management unit 11 selects a partial log area that is not to be held (mask) and does not contain data, and makes it a log writing target.

The log management unit 11 writes the log from StartAddress of the area management table 122 where TableWriting=1 of the management table 121 (step S27). Then, the log management unit 11 ends the processing at the time of starting the BIOS.

[Flowchart of deletion processing during OS operation]
FIG. 8 is a diagram illustrating an example of a flowchart of deletion processing during OS operation according to the embodiment.

After a while after the OS starts, the log management unit 11 acquires the management table 121 (step S31). The log management unit 11 determines whether there is an area management table 122 in which the management table 121 has Mask=0 and DataStored=0 (step S32). That is, the log management unit 11 determines whether or not there is no partial log area to be held (masked) and there is a partial log area that does not contain data. In other words, the log management unit 11 determines whether there is a target for a partial log area that can be written immediately without erasing the partial log area. If it is determined that there is an area management table 122 with Mask=0 and DataStored=0 (step S32; Yes), the log management unit 11 ends the deletion process during OS operation.

On the other hand, if it is determined that there is no area management table 122 with Mask=0 and DataStored=0 (step S32; No), the log management unit 11 performs the following process. The log management unit 11 identifies the area management table 122 with Mask=1 other than 1 and has the largest CountStartUp, and sets the corresponding TalesInit bit of the management table 121 (step S33). That is, the log management unit 11 selects the partial log area in which the oldest BIOS startup log is held from among the partial log areas that are not to be held (mask), and makes it a log deletion target.

Then, the log management unit 11 performs a deletion process on the log to be deleted (step S34). That is, the log management unit 11 executes the log deletion process during OS operation described with reference to FIG. Then, the log management unit 11 ends the deletion process during OS operation.

[Flowchart of processing when an error occurs]
FIG. 9 is a diagram illustrating an example of a flowchart of processing when an error occurs according to the embodiment.

When an error occurs, the log management unit 11 acquires the management table 121 (step S41). The log management unit 11 determines whether there is an area management table 122 with TableWriting=1 in the management table 121 (step S42). That is, the log management unit 11 determines whether there is a partial log area in which a log is being written. If it is determined that there is no area management table 122 with TableWriting=1 (step S42; No), the log management unit 11 terminates the process because there is no error during writing of the partial log area.

On the other hand, if it is determined that there is an area management table 122 with TableWriting=1 (step S42; Yes), the log management unit 11 selects the area management table 122 determined to exist and sets Mask in the management table 121. Add (step S43). That is, the log management unit 11 sets the corresponding bit of TablesMask of the management table 121 in order to mask the target area management table 122.

Then, the log management unit 11 sets TableWriting of the management table 121 to "0" (step S44). That is, the log management unit 11 changes the state in which the log is being written to the state in which the log is not being written. The log management unit 11 then ends the processing when an error occurs.

[Effects of Examples]
In this way, the information processing device 1 has a plurality of partial storage areas obtained by dividing the storage area for storing BIOS logs. The information processing device 1 changes the partial storage area in which the BIOS log is recorded each time the BIOS is started. The information processing device 1 records the BIOS log in the changed partial storage area. If the information processing device 1 determines that there is no partial storage area in which the log can be recorded without erasing the log among the plurality of partial storage areas after the BIOS is started and while the OS is operating, the information processing device 1 deletes the log. Delete the log of the partial storage area with old records and secure a new partial storage area. According to this configuration, the information processing device 1 erases the partial storage area of the log during OS operation instead of when starting the BIOS, so that the information processing device 1 can erase the log without performing the erasing process the next time the BIOS is started. This makes it possible to write data, thereby shortening the computer's startup time.

In addition, if the information processing device 1 determines that there is no partial storage area in which the log can be recorded without erasing the log among the plurality of partial storage areas, the information processing device 1 determines whether the log is recorded when an error occurs. The log of the partial storage area with the oldest log record among the plurality of partial storage areas excluding the partial storage area is deleted. According to this configuration, the information processing device 1 can erase logs in a partial storage area that can be written at the next startup of the BIOS while maintaining (protecting) important logs during OS operation.

Further, during operation of the OS, the information processing device 1 calls the SMM of the BIOS from the ACPI driver of the OS using the specified AML, and at the timing when the instruction to delete the BIOS log is obtained from the SMM, the information processing device 1 Clear logs from storage area. According to this configuration, the information processing device 1 can realize a mechanism for erasing the log area of the BIOS during operation of the OS.

Furthermore, if the information processing device 1 is unable to erase the log of a specific partial storage area during operation of the OS, the information processing device 1 will automatically delete the remaining logs that could not be erased in the specific partial storage area when the BIOS is started next time. Clear the logs. According to this configuration, even if the information processing device 1 is unable to erase all logs in a specific partial storage area during operation of the OS, the information processing device 1 only needs to erase the remaining logs the next time the BIOS is started. Therefore, erasing does not take much time, and the computer startup time can be shortened.

[others]
In the above embodiments, each component of the illustrated device does not necessarily have to be physically configured as illustrated. In other words, the specific manner of distributing and integrating devices is not limited to what is shown in the diagram, and all or part of them can be functionally or physically distributed or integrated in arbitrary units depending on various loads and usage conditions. can be configured. For example, the distribution processing section 111, the compression management section 112, the cryptographic compression processing section 113, and the compression processing section 114 may be integrated. Further, the write management unit 115 may be distributed to perform BIOS log write processing, log deletion processing at the time of BIOS startup, and log deletion processing after OS startup.

Further, the various processes described in the above embodiments can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. Therefore, an example of a computer that executes a BIOS log management program that implements the same functions as the information processing device 1 shown in FIG. 1 will be described below. FIG. 10 is a diagram illustrating an example of a computer that executes a BIOS log management program (some descriptions are omitted for brevity).

As shown in FIG. 10, the computer 200 includes a CPU (Central Processing Unit) 203 that executes various calculation processes, an input device 215 that accepts data input from a user, and a display device 209. The computer 200 also includes an internal storage 213 and an external storage 214 that read programs and the like from storage media, and a communication device 217 that exchanges data with other computers via a network. The computer 200 also includes a memory 201 that temporarily stores various information, an SPI Flash 205, and the like. The memory 201, CPU 203, internal storage 213, external storage 214, SPI Flash 205, display device 209, input device 215, and communication device 217 are connected via a bus 219.

The SPI Flash 205 stores a BIOS log management program 205a and BIOS log management processing related information 205b. The communication device 217 manages the interface between the network and the inside of the device, and controls the input/output of data from other computers. For example, a modem, a LAN adapter, or the like can be used as the communication device 217.

The display device 209 is a display device that displays data such as a cursor, icons, toolbox, documents, images, and functional information. The display device 209 can employ, for example, a liquid crystal display or an organic EL (Electroluminescence) display.

The CPU 203 reads the BIOS log management program 205a, expands it into the memory 201, and executes it as a process. This process corresponds to each functional unit of the information processing device 1. The BIOS log management processing related information 205b includes, for example, a management table 121 and an area management table 122. For example, the external storage 214 stores information such as the BIOS log management program 205a.

1 Information processing device 10 Firmware
11 Log management section 12 Storage section 20 OS
30 CPU/Chip Set
40 SPI Flash
41 Log area 111 Distribution processing unit 112 Compression management unit 113 Cryptographic compression processing unit 114 Compression processing unit 115 Write management unit 116 Write processing unit 121 Management table 122 Area management table

Claims (6)

A plurality of partial storage areas obtained by dividing a storage area for storing BIOS (Basic Input/Output System) logs;
a changing unit that changes a partial storage area for recording logs of the BIOS each time the BIOS is started;
a recording unit that records the BIOS log in the partial storage area changed by the changing unit;
After the BIOS has started and while the OS (Operating System) is operating, if it is determined that there is no partial storage area in which the log can be recorded without erasing the log, the log an erasing unit that erases a log of a partial storage area with old records to secure a new partial storage area;
An information processing device comprising: When the erasing unit determines that there is no partial storage area in which the log can be recorded without erasing the log among the plurality of partial storage areas, the deletion unit deletes the partial storage area in which the log was recorded when an error occurred. The information processing apparatus according to claim 1, wherein the log of the partial storage area with the oldest log record among the plurality of partial storage areas excluding . The erasing unit calls the SMM of the BIOS from the ACPI driver of the OS using specified AML while the OS is in operation, and performs a specified operation at a timing when an instruction to erase the log of the BIOS is obtained from the SMM. The information processing apparatus according to claim 1 or 2, wherein the log of a partial storage area of the information processing apparatus is erased. Furthermore, when the log in a specific partial storage area cannot be erased during operation of the OS, the erasing unit erases the remaining log that could not be erased in the specific partial storage area when the BIOS is started next time. The information processing apparatus according to claim 1 or 2, wherein the information processing apparatus erases a log of the information processing apparatus. a partial storage area among a plurality of partial storage areas obtained by dividing a storage area for storing BIOS logs, and changing the partial storage area for recording the BIOS logs each time the BIOS is started;
Recording the BIOS log in the changed partial storage area,
After the BIOS is started and while the OS is operating, if it is determined that there is no partial storage area in the plurality of partial storage areas in which logs can be recorded without erasing the logs, the portion where log records are old is determined. A BIOS log management program that causes a computer to erase logs from a storage area and secure a new partial storage area. a partial storage area among a plurality of partial storage areas obtained by dividing a storage area for storing BIOS logs, and changing the partial storage area for recording the BIOS logs each time the BIOS is started;
Recording the BIOS log in the changed partial storage area,
After the BIOS is started and while the OS is operating, if it is determined that there is no partial storage area in the plurality of partial storage areas in which logs can be recorded without erasing the logs, the portion where log records are old is determined. A BIOS log management method in which a computer executes the process of deleting logs in a storage area and securing a new partial storage area.

Images