Method of operating computing device, method of operating operating system, and computing device

Abstract

A method of operating a computing device, a method of operating an operating system, and a computing device are provided. A method of operating a computing device includes performing, by a BIOS (Basic Input / Output System), a pre-boot memory test on a memory; recording, in the log, memory failure information generated as a result of performing the pre-boot memory test by the BIOS; and after installing an operating system (OS) of the computing device, performing a page offline operation using the memory failure information.

Description

Technical Field

[0001] The present disclosure relates to a method for responding to a memory failure and a computing device applying the method. Background Art

[0002] BIOS (Basic Input / Output System) performs tests on hardware components of a computing device after the computing device is powered on. For example, a BIOS test can be performed on a memory module. If a memory failure is detected as a result of performing such a test, a corresponding response action is executed.

[0003] The response action can include initiating an interrupt, mapping-out in a channel where a memory failure has occurred, PPR (post-packaging repair), etc. Initiating an interrupt can prevent an administrator from taking any response action other than power-off or front-end inspection. Even when a failure occurs only in a partial area of a memory module, mapping-out of a channel having a memory error can prevent all memory modules connected to the channel from being used. Mapping-out of a channel can deactivate the channel to the memory module, thereby reducing the bandwidth of the entire memory input / output. Due to limitations supported by a processor, PPR has limited availability.

[0004] On the other hand, at the operating system (OS) level, a page-offline technique is provided. The page-offline technique isolates a memory area where a failure has occurred so that the memory area where a failure has occurred is not used on a page-by-page basis. Such a page-offline technique prevents a page (frame) of a memory area where a memory failure has occurred from being mapped to a page utilized by a process, thereby preventing the memory area where a memory failure has occurred from being actually utilized. Since such a page-offline technique only excludes a failure-occurring area controlled by the operating system from use, there is an advantage of maximizing the utilization of memory resources compared to the above-described initiating an interrupt, mapping-out of a channel, and PPR techniques.

[0005] Since the above-described page-offline technique is provided by the operating system, the above-described page-offline technique is a technique that cannot be utilized before startup is completed. That is, if an action related to memory fail fail-safe (such as initiating an interrupt, mapping-out, and PPR) is taken due to the occurrence of a memory failure in the BIOS, there is a possibility that the above-described page-offline technique will not be utilized. Summary of the Invention

[0006] Aspects of the present invention provide a method for responding by using the page offline technology of an operating system even when a memory failure occurs during the memory test process of the BIOS, and a computing device for executing the method.

[0007] Aspects of the present invention also provide a method for taking appropriate response actions for memory failures according to the type of memory failure, and a computing device for executing the method.

[0008] Aspects of the present invention also provide a method for taking response actions on page offline failures, and a computing device for executing the method when the page offline of the operating system is attempted as a response action to a memory failure when the memory failure occurs during the memory test process of the BIOS but fails.

[0009] However, aspects of the present invention are not limited to the aspects set forth herein. By referring to the detailed description of the present invention given below, the above and other aspects of the present invention will become clearer to those of ordinary skill in the art to which the present invention pertains.

[0010] According to one aspect of the present disclosure, a method of operating a computing device includes: performing a pre-boot memory test on a memory by a BIOS (Basic Input / Output System); recording memory failure information generated as a result of the pre-boot memory test performed by the BIOS in a log; and after an operating system (OS) of the computing device is installed, performing a page offline operation using the memory failure information.

[0011] According to one aspect of the present disclosure, a method of operating an operating system (OS) installed in a computing device includes: reading memory failure information recorded by the BIOS and generated as a result of performing a pre-boot memory test of the BIOS; and performing a page offline operation using the memory failure information.

[0012] According to one aspect of the present disclosure, a computing device includes: a BIOS ROM configured to store a BIOS program, the BIOS program configured to record memory failure information generated as a result of performing a pre-boot memory test on a memory, and load a startup image of an operating system and at least one auto-execution instruction; and a processor configured to execute the operating system and the at least one auto-execution instruction. The at least one auto-execution instruction includes instructions for reading the memory failure information after the step of loading the startup image of the operating system and recording at least some of the memory failure information in a page offline information file referenced by a page offline module of the operating system. The operating system includes instructions for performing a page offline operation using at least some of the memory failure information in the page offline information file. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The above and other aspects and features of the present invention will become clearer by describing exemplary embodiments of the present invention in detail with reference to the accompanying drawings.

[0014] Figure 1 is a block diagram of a computing device according to some embodiments of the present disclosure.

[0015] Figure 2 is a flowchart of a method for responding to a memory failure according to some embodiments of the present disclosure.

[0016] Figure 3 is a diagram for explaining a page offline information file mentioned in some embodiments of the present disclosure.

[0017] Figure 4 is a diagram for explaining a data pattern of a log cited in some embodiments of the present disclosure.

[0018] Figure 5 is for explaining some embodiments in which some operations of the method for responding to a memory failure described with reference to Figure 2 are modified.

[0019] Figures 6 to 8 is a signal flowchart for helping to understand the method for responding to a memory failure according to some embodiments of the present disclosure.

[0020] Figure 9 is a hardware configuration diagram of a computing system according to some embodiments of the present disclosure. Detailed Description of Specific Embodiments

[0021] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings. By referring to the following detailed description of the exemplary embodiments and the accompanying drawings, the advantages and features of the present disclosure and the methods for realizing the advantages and features of the present disclosure can be more easily understood. However, the present disclosure can be implemented in many different forms and should not be construed as limited to the embodiments set forth herein. Instead, these embodiments are provided so that the present disclosure will be thorough and complete, and will fully convey the concept of the disclosure to those skilled in the art, and the present disclosure will be defined by the appended claims and equivalents of the appended claims. When describing the present disclosure, if a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description will be omitted.

[0022] Unless the context clearly specifies the singular, the singular expressions used in the following embodiments include the plural concept. In addition, unless the context clearly specifies the plural, the plural expressions include the singular concept. Furthermore, the terms (such as, first, second, A, B, (a), (b)) used in the following embodiments are only used to distinguish one element from another element, and the terms do not limit the nature, order or sequence of the related elements.

[0023] Elements described with reference to terms used in the present disclosure (such as units, modules, blocks, devices, or components, etc.) and functional blocks shown in the drawings can be implemented in the form of software, hardware, or a combination thereof. For example, software can be machine code, firmware, embedded code, and application software. For example, hardware can include circuits, electronic circuits, processors, computers, integrated circuits, integrated circuit cores, passive components, or a combination thereof.

[0024] The following will refer to Figure 1 Describe the configuration and operation of a computing device according to some embodiments of the present disclosure.

[0025] As Figure 1 shown, a computing device 100 according to some embodiments may include a BIOS 120, a memory 130, and an operating system 150. It will be understood that Figure 1 the configuration diagram of the computing device 100 shown in Figure 9 is shown in units of logical elements rather than actual hardware elements. The hardware configuration of the computing device 100 can be understood by referring to Figure 1 the description of Figure 9 which will be described below. For example,

[0026] When power is supplied to the computing device 100, the BIOS program stored in the ROM (Read-Only Memory) is executed. Therefore, the operating BIOS 120 performs a self-test on various hardware elements (such as the memory 130). Such a self-test is performed before starting the operating system 150. The present disclosure relates to a case where a memory failure occurs as a result of testing on the memory 130 among various hardware elements.

[0027] The BIOS 120 records information about the memory failure in a log. Since, as described above, the memory test is performed by the BIOS 120 before the operating system 150 starts, the log may not be recorded as a file. This is because the operating system 150 can only be written to the storage device 140 after the operating system 150 has completed the installation of the file system. Therefore, the BIOS 120 can record the log in a predetermined address area of the memory 130 in a predetermined format, or record the log in the CMOS (Complementary Metal Oxide Semiconductor) memory that stores BIOS configuration values (i.e., CMOS settings).

[0028] BIOS 120 may determine a response action based on the type of memory failure. For example, if the type of memory failure is included in one or more predetermined fatal types, BIOS 120 may perform any of the legacy response actions. One or more predetermined fatal types may include several predetermined memory failure types that cannot be overcome by performing page offline. One or more predetermined fatal types may include a memory failure type associated with a processing failure of a control signal. The legacy response action may include enabling interruption, channel mapping out, PPR, and restarting. BIOS 120 may control one or more hardware elements (such as power supply 110) during the execution of the legacy response action.

[0029] If the type of memory failure is not included in the fatal type, the BIOS 120 may record the memory failure information in a log, and may initiate booting using the operating system 150 by executing a boot loader. Figure 4 Describes the format of memory failure information.

[0030] The operating system 150 may be loaded into the memory 130 and execute various initialization instructions for starting the computing device 100. The initialization instructions may include a BIOS link instruction that reads the memory fault information and writes at least some of the memory fault information to a page offline information file referenced by the page offline module. The page offline information file may be accessed through a file system structure configured by the operating system 150 on the storage device 140.

[0031] That is, the memory failure information included in the log recorded by the BIOS is recorded in the page offline information file by the BIOS test information link module (not shown), which is implemented by executing the BIOS link instruction. In other words, the BIOS test information link module plays a role in copying the memory failure information to the page offline information file that can be accessed by the operating system. Therefore, no matter how fast, the BIOS test information link module can be executed after the installation of the file system of the operating system 150 is completed.

[0032] In some embodiments, the BIOS test information linking module can be automatically executed at startup by being included in a list of modules that are automatically executed at startup. For example, the startup automatic execution script may include commands and parameters for executing the BIOS test information linking module.

[0033] The page offline module 151 is a module of the operating system 150, and according to the execution method of the offline module 151, the page offline module 151 may be executed simultaneously with the startup of the operating system 150, or may be executed when a specific event occurs after the startup. When the page offline module 151 is executed, the page offline may be performed by referring to the physical address of the memory failure area written in the page offline information file. Therefore, it may be expected that the BIOS link instruction is executed at the latest before the page offline module 151 is executed. In some embodiments, the BIOS link instruction may be executed and completed before the page offline module 151 is executed.

[0034] In some embodiments, one or more APIs executed in the process of executing the page offline module 151 may be hooked by an API hooking technique to ensure that the execution time of the BIOS link instruction is earlier than the execution time of the page offline module 151. For example, such a hook can ensure that the BIOS link instruction is completed before the execution of the page offline module 151 is initiated. In the hook callback function executed according to the hook, it is verified whether the execution of the page offline module 151 is correct, and if the execution of the page offline module 151 is correct as a result of the verification, the execution of the BIOS link instruction can be completed first. Therefore, it can be ensured that the execution time of the BIOS link instruction is earlier than the execution time of the page offline module 151, and the memory fault area confirmed as a result of the memory test performed by the BIOS 120 can be reliably disabled by the page offline module 151.

[0035] In some embodiments, because the way of recording logs and the location where logs are stored may be different for each model of BIOS 120, the BIOS link instruction may be implemented separately for each model of BIOS. If the page offline module 151 performs the operation of the BIOS test information link module as described above, the page offline module 151 should be implemented separately for each model of BIOS 120. Although such an implementation may result in an excessive increase in the page offline module 151, as described above, it will be understood that the BIOS link instruction is implemented separately from the page offline module 151.

[0036] Of course, it goes without saying that in some other embodiments, the page offline module 151 may perform the operation of the BIOS test information link module as described above. In this case, there is an implementation advantage that there is no need to call a separate technology (such as the above-mentioned hook) for ensuring that the execution time of the BIOS link instruction is earlier than the execution time of the page offline module 151.

[0037] The configuration and operation of the computing device according to some embodiments have been described above. By referring to some embodiments to be described below, the method for operating the computing device of the present disclosure can be understood in more detail. In addition, the technical ideas that can be understood by the above-mentioned embodiments of the dynamic monitoring system can be reflected in the various embodiments to be described below.

[0038] In the following, reference will be made to Figure 2 A method for responding to a memory failure according to some embodiments of the present disclosure is described. The dynamic monitoring method according to some embodiments may be performed by a computing device. In the following, when the execution entity of each operation is omitted, it can be understood that the execution entity is the above-mentioned computing device.

[0039] A memory test is performed by the BIOS (S100). When a memory failure is detected in the memory test (S200), the memory failure information is recorded in a log (S300). The present disclosure is not limited thereto. In some embodiments, when the type of the memory failure corresponds to one or more predetermined page offline link target types, the BIOS may record the memory failure information of the memory failure in the log. For example, the predetermined page offline link target type may include a single bit type, a transient error type, a row type, and an area type. The row type may indicate a continuous failure of adjacent cells with a constant x address and a varying y address. The area type may indicate a continuous failure of adjacent cells within a closed area.

[0040] For example, Figure 5 As shown in , if a memory failure is detected in a memory test (S200), it may be determined whether to record the memory failure information in a log (S210) according to the type of the memory failure. For example, if the type of the memory failure is a fatal type (S210), a legacy response action may be performed without recording the memory failure information in a log (S220). Hereinafter, whether the type of the memory failure is a fatal type is referred to as a first condition of step S210.

[0041] For example, only if the first condition is satisfied when a failure is detected in a memory test, a legacy response action by the BIOS may be performed ( S220 ), and otherwise, memory failure information may be recorded in a log ( S300 ).

[0042] The legacy response actions may include enabling interrupt, channel mapping out, PPR and restart, and the determination of the execution target action among the legacy response actions will be determined by the logic of the BIOS.

[0043] If the first condition is met, it may be the case that the type of memory failure is included in one or more predetermined fatal types. In this case, by minimizing the execution of legacy response actions, the use of available resources of the memory module can be maximized.

[0044] In some embodiments, only if the second condition is satisfied when a memory failure is detected in a memory test, memory failure information may be recorded in a log ( S300 ), and if the second condition is not satisfied, any one of the legacy response actions may be performed ( S220 ).

[0045] The second condition may be a condition satisfied when the data size corresponding to the address area where the memory failure occurs is less than a reference value. That is, in this case, only when the data size of the area that cannot be used due to the memory failure is less than a standard value, the memory failure response is performed by page offline in a limited manner, thereby enhancing the stability of the execution environment of the computing device.

[0046] In some embodiments, it can be configured in the BIOS through CMOS settings, etc.: whether the legacy response action by the BIOS will be performed only if the first condition is met when a failure is detected in the memory test, or whether the memory failure response action will be performed by page offline only if the second condition is met. This allows the user of the computing device to specify whether to prioritize the stability of the execution environment or maximize the use of memory resources according to the purpose of the computing device.

[0047] In some embodiments, the memory fault information may include information about the physical address where the memory fault occurs, and a bit indicating activation as the value of the page offline check flag. In some embodiments, the memory fault information may include the physical address of the memory fault and a first value of the page offline check flag indicating activation of the page offline operation. The physical address may correspond to the page address of the page with the memory fault. The activation of the page offline operation indicates that the physical address of the memory fault has not undergone the page offline operation. The operating system can manage the memory in units of pages. In some embodiments, the pre-start memory test can be performed in units of pages, and memory fault information associated with the page address of the page with the memory fault (ie, a bad page) is generated. In some embodiments, after the page offline operation is completed, the bad page associated with the first value of the page offline check flag can be removed from the memory space managed by the operating system.

[0048] The log may be recorded in the EWL (Enhanced Warning Log) structure of the BDAT (BIOS Data Advanced Configuration and Power Management Interface (ACPI) Table). The conventional EWL structure does not define an entry for writing memory fault information. In view of this, in some embodiments, such as Figure 4As shown in FIG. 1 , entries of physical address information and entries 13 and 15 of page offline check flags may be added to EWL structures 12 and 14. Figure 4 The log in the EWL structure shown in can be recorded in a predetermined area of ​​the memory as described above, or can be recorded in the CMOS memory. In addition, the operating system can access the log through the ACPI interface in a standardized manner.

[0049] In some embodiments, the memory fault information may further include one or more additional entries. The one or more additional entries may be information that a page offline module of the operating system may refer to to perform page offline in a manner corresponding to the memory test result of the BIOS.

[0050] For example, the additional entry may include at least one of type information of memory failure, history information of memory failure occurrence, memory test mode information of BIOS, model and version information of BIOS, model information of memory module, and model information of memory controller.

[0051] After recording the memory failure information, booting using the operating system installed on the computing device (i.e., installing the operating system on the computing device) is performed (S400), and after booting (i.e., after installing the operating system), the log is read, and at least a portion of the memory failure information recorded in the log is recorded in a page offline information file (S500). The page offline information file may be a file in which physical addresses of pages to be targeted for page offline by a page offline module are recorded. Figure 3 The following is a description of the page offline information file in the Linux operating system (10, 11). Specifically, Figure 3 The description of the page offline information file for soft page offline (10) and the description of the page offline information file for hard page offline (11) are shown. Soft page offline performs page offline after backing up the data of the page that is the target of page offline, and hard page offline performs page offline without data backup.

[0052] In some embodiments, in step S500 , if a value of a page offline check flag included in the memory fault information is a value indicating activation (eg, true), physical address information included in the memory fault information may be recorded in an offline information file.

[0053] As described above, step S500 may be performed by the BIOS test information link module or by the page offline module. "After startup" may be interpreted as "after loading the kernel of the operating system capable of executing user-level applications or services into the memory and completing the installation of the file system".

[0054] Next, in step S600, the page offline can be performed using the physical address information recorded in the page offline information file. Through the page offline, the memory area corresponding to the physical address information will not be mapped to the memory page accessed by the process executed on the operating system. Therefore, the stability of the memory access of the process will be enhanced.

[0055] In some embodiments, the soft page offline may be performed first through step S600 , and the hard page offline may be performed when the soft page offline fails.

[0056] The following will refer to Figures 6 to 8 The description is provided to facilitate understanding of some embodiments.

[0057] Figure 6 is a signal flow diagram for more clearly understanding the interaction between the BIOS 120 and the operating system 150.

[0058] When power is supplied to the computing device, the BIOS 120 included in the computing device performs a self-memory test (S100). When a memory failure is detected as a result of the memory test (S200), the BIOS 120 records the memory failure information in a log (S300). The BIOS 120 loads and executes a boot program (S410), and the operating system 150 executes instructions for system initialization to boot the computing device (S420). After booting the computing device, the BIOS 120 no longer operates.

[0059] The operating system 150 reads the log (S510). As mentioned above, the log may be read from a specific address of the memory or the CMOS memory.

[0060] The operating system 150 records the memory failure information included in the log in the page offline information file (S520). Recording the memory failure information in the page offline information file may be performed by a BIOS test information linking module executed by the booted operating system, or may be performed by the page offline module itself.

[0061] Next, the operating system 150 performs page offline using information recorded in the page offline information file ( S600 ).

[0062] In some embodiments, if page offline by operating system 150 fails, legacy response actions by BIOS 120 may be performed as a second-best solution. Figure 7 Some embodiments are shown for preventing BIOS 120 from continuously attempting to take a page offline by operating system 150 even if taking the page offline by operating system 150 has failed.

[0063] When a memory failure is detected ( S200 ) as a result of performing the self memory test ( S100 ), the BIOS 120 may record physical address information where the memory failure occurs and memory failure information including a bit indicating activation as a value of a page offline check flag in a log ( S300 ).

[0064] The operating system 150 can be operated by referring to Figure 6 The described process attempts offline processing of a page corresponding to the physical address information (i.e., page offline or bad page offline) (S600). If the page offline is successful (S610), the operating system 150 may update the value of the page offline check flag recorded in the log to a bit indicating deactivation (S620). In some embodiments, after the page offline operation is completed (i.e., successfully completed), the page offline check flag may be updated to a second value indicating deactivation of the page offline operation. The deactivation of the page offline operation indicates that the physical address of the bad page with the memory fault has undergone an offline operation, thereby removing the physical address of the bad page from the memory space managed by the OS. The entity that updates the value of the page offline check flag may be a BIOS test information link module or a page offline module.

[0065] If the page offline fails (S610), the operating system 150 restarts the computing device (S700). In the restart of the computing device, the value of the page offline check flag may still be set to a bit indicating activation (ie, may be maintained as a bit indicating activation).

[0066] By restarting (S700), BIOS 120 will perform memory test again (not shown) and detect memory failure as before unless there is a special situation (not shown). At this time, BIOS 120 checks whether the value of the page offline check flag is a bit indicating activation (S710).

[0067] If a restart occurs based on the failure of page offline, since the value of the page offline check flag is still set to the bit indicating activation, BIOS 120 can indirectly check whether page offline has been attempted and failed as a memory fault response action by checking whether the value of the page offline check flag is the bit indicating activation.

[0068] If the value of the page offline check flag is a bit indicating activation ( S710 ), the BIOS 120 updates the value of the page offline check flag to a bit indicating deactivation ( S720 ), and may perform a legacy response action ( S720 a ).

[0069] On the other hand, in some embodiments, even if BIOS 120 determines page offline as a memory failure response action, records memory failure information in a log, and starts the operating system, the operating system may determine whether to perform page offline on its own.Figure 8 Explain this.

[0070] When a memory failure is detected ( S200 ) as a result of performing the self memory test ( S100 ), the BIOS 120 may record in a log the physical address information where the memory failure occurs, a bit indicating activation as a value of a page offline check flag, and memory failure information including one or more additional entries ( S300 b ).

[0071] For example, the additional entry may include at least one of type information of memory failure, history information of memory failure occurrence, memory test mode information of BIOS, model and version information of BIOS, model information of memory module, and model information of memory controller.

[0072] The type information of the memory failure may include at least one of a single-unit type, a plurality of single-unit types, and a low failure type.

[0073] For ease of understanding, the following description assumes a case in which type information of a memory failure is recorded as an additional entry.

[0074] After reading the log ( S510 ), the operating system 150 may determine whether the type of the memory failure is a type in which page offline is enabled by using type information of the memory failure recorded in the log ( S515 ).

[0075] Page offline is a technique that depends on the operating system 150, and in some embodiments, the page offline module itself, rather than the BIOS test information linking module, may determine whether the type of memory fault is a type for which page offline is enabled (S515). For example, a list of types of memory faults for which page offline is enabled is pre-stored, and the page offline module may refer to the list to determine whether the type of memory fault is a type for which page offline is enabled.

[0076] If the type of memory failure is a type in which page offline is enabled, as described above, the operating system 150 records the physical information in which the memory failure occurs in the page offline information file (S520), performs page offline (S600), and updates the value of the page offline check flag to a value indicating deactivation after performing page offline (S620).

[0077] If the type of memory failure is not a type in which page offline is enabled, the operating system may restart the computing device ( S700 ).

[0078] According to the restart (S700), the BIOS 120 checks whether the value of the page offline check flag is a bit indicating activation (S710), and when the value of the page offline check flag is a bit indicating activation, updates the value of the page offline check flag to a bit indicating deactivation (S720), and may perform a legacy response action (S720a).

[0079] Refer to the above Figures 1 to 8 The technical ideas understood by describing some embodiments can be reflected in other embodiments described below.

[0080] Figure 9 is a hardware configuration diagram of a computing system 1000 according to some embodiments of the present disclosure. For example, Figure 9 The computing system 1000 may refer to Figure 1 The computing device 100 described above. The computing system 1000 may include one or more processors 1100, a system bus 1700, a BIOS ROM 1600 storing a BIOS program, a communication interface 1200, a memory 1400 loading a computer program 1500 executed by the processor 1100, and a storage device 1300 storing the computer program 1500. The computing system 1000 may be provided through a cloud service, and in this case, the one or more processors 1100, the communication interface 1200, the memory 1400, and the storage device 1300 may all be virtual resources.

[0081] The BIOS program may log memory failure information generated as a result of performing a pre-boot memory test. That is, the BIOS program logs the memory failure information in a log and then successfully performs a boot using the operating system, rather than performing a legacy response action due to a memory failure detected as a result of performing a memory test. The log is written to the EWL structure of the BDAT (BIOS Data ACPI Table) and may be recorded at a specific address of the memory 1400 or a CMOS memory (not shown).

[0082] In some embodiments, the BIOS program may include instructions to execute a legacy response action when the type of memory failure is a fatal type, and if the type of memory failure is not a fatal type, record the memory failure information in a log and then perform booting normally using the operating system.

[0083] The processor 1100 controls the overall operation of each component of the computing system 1000. The processor 1100 may perform calculations on at least one application or program for performing the method / operation according to various embodiments of the present disclosure. The memory 1400 stores various types of data, instructions and / or information. The memory 1400 may load one or more computer programs 1500 from the storage device 1300 to perform the method / operation according to various embodiments of the present disclosure. The system bus 1700 provides communication functions between components of the computing system 1000. The communication interface 1200 supports Internet communication for the computing system 1000. The storage device 1300 may store one or more computer programs 1500 non-temporarily.

[0084] The computer program 1500 may include one or more instructions for implementing the methods / operations according to various embodiments of the present disclosure. When the computer program 1500 is loaded into the memory 1400, the processor 1100 may perform the methods / operations according to various embodiments of the present disclosure by executing one or more instructions.

[0085] Computer program 1500 may include a plurality of instructions constituting an operating system, and one or more automatically executed instructions that are automatically executed when the operating system is started.

[0086] The one or more automatic execution instructions may include instructions for reading memory fault information after starting the operating system and recording at least a portion of the memory fault information to a page offline information file referenced by the page offline module. In addition, the operating system may include instructions for executing page offline using information written in the page offline information file.

[0087] Already referred to Figures 1 to 9 Various embodiments of the present disclosure and their effects are described. Effects according to the technical idea of ​​the present disclosure are not limited to the above-mentioned effects, and other effects not described can be clearly understood by those skilled in the art from the above description.

[0088] The technical ideas of the present disclosure described so far can be implemented as computer-readable codes on a computer-readable medium. The computer program recorded on the computer-readable recording medium can be transmitted to another computing device through a network (such as the Internet), installed on another computing device, and thus used on another computing device.

[0089] Although the operations are shown in a specific order in the drawings, it should not be understood that when the operations must be performed in a specific order or a continuous order or when all operations must be performed, the desired results can be obtained. In some cases, multitasking and parallel processing may be advantageous. Although some embodiments of the present disclosure have been described above with reference to the drawings, it will be understood by those skilled in the art that the present disclosure can be implemented in other specific forms without changing the technical ideas or essential features. The embodiments described above should be understood in all aspects to be illustrative and not restrictive. The scope of protection of the present invention should be interpreted according to the attached claims, and all technical ideas within the equivalent scope should be interpreted as included in the scope of rights of the technical ideas defined by the present disclosure.

Claims

1. A method of operating a computing device, comprising: recording in a log memory failure information generated as a result of a pre-boot memory test performed by a basic input / output system; as well as After booting the operating system of the computing device, a page offline operation is performed using the memory fault information.

2. The method according to claim 1, in, The steps to record storage fault information in the log include: When the type of memory failure corresponding to the memory failure information is included in at least one predetermined page offline link target type, the memory failure information is recorded in the log.

3. The method according to claim 1, in, The memory failure information includes a physical address of the memory failure and a first value of a page offline check flag indicating activation of a page offline operation, and wherein the physical address corresponds to a page address of a page having a memory fault, and Among them, the activation of the page offline operation indicates that the physical address of the memory failure has not undergone the page offline operation.

4. The method according to claim 3, in, Logs are recorded in the enhanced warning log structure of the basic input / output system data advanced configuration and power management interface table.

5. The method according to claim 3, in, The steps to perform page offline operations include: After the page offline operation is completed, the page offline check flag is updated to a second value indicating deactivation of the page offline operation, The deactivation of the page offline operation indicates that the physical address has undergone an offline operation, so that the physical address is removed from the memory space managed by the operating system.

6. The method according to claim 5, further comprising: In response to the page offline operation failing, restarting the computing device while maintaining the first value of the page offline check flag, The first value of the page offline check flag is updated to a second value of the page offline check flag, and a legacy response action is performed after the step of updating the first value of the page offline check flag to the second value.

7. The method according to claim 1, in, The steps to perform page offline operations include: Read the memory failure information recorded in the log; Recording at least a portion of the memory fault information in a page offline information file referenced by a page offline module of the operating system; and The page offline operation is performed using the information recorded in the page offline information file.

8. The method according to claim 7, in, The step of reading the memory fault information and the step of recording the at least some of the memory fault information are performed after the file system of the operating system is installed and before the step of starting to perform the page offline operation.

9. The method according to claim 7, in, The steps of reading the memory fault information and recording the at least a portion of the memory fault information are performed by a basic input / output system test information linking module executed after the operating system is booted.

10. The method according to claim 7, in, The steps of reading the memory fault information and recording the at least a portion of the memory fault information are performed by a page offline module of the operating system.

11. The method according to claim 7, in, The step of recording at least a portion of the memory fault information comprises: Record the physical address of the memory failure, Here, the physical address corresponds to a page address which is a unit of memory management by an operating system.

12. The method according to claim 7, in, The memory failure information includes a physical address of the memory failure, a bit indicating activation as a value of a page offline check flag, and information indicating a memory failure type. wherein the physical address corresponds to a page address which is a unit of memory management by an operating system, and The step of recording at least a portion of the memory fault information in a page offline information file referenced by the page offline module comprises: When the memory failure type is included in at least one predetermined page offline execution target type, the at least some of the memory failure information is recorded in the page offline information file.

13. The method according to claim 12, in, The step of recording the at least a portion of the memory fault information in a page offline information file referenced by the page offline module comprises: When the memory failure type is not included in the at least one predetermined page offline execution target type, restarting is performed.

14. A method of operating an operating system installed in a computing device, comprising: reading memory failure information, the memory failure information being recorded by a basic input / output system and being generated as a result of performing a pre-boot memory test of the basic input / output system; as well as Perform a page offline operation using the memory fault information.

15. The method according to claim 14, in, The steps to perform page offline operations include: Recording at least a portion of the memory fault information in a page offline information file referenced by a page offline module executing the operating system; and The page offline operation is performed using the information recorded in the page offline information file.

16. The method according to claim 15, in, The step of recording the at least a portion of the memory fault information in the page offline information file is performed after the file system of the operating system is installed and before the step of starting to perform the page offline operation.

17. The method according to claim 15, in, The step of recording the at least a portion of the memory fault information in the page offline information file is performed by a basic input / output system test information linking module which is installed in the operating system and is executed after the operating system is started.

18. The method according to claim 14, in, The memory failure information includes a physical address of a memory failure detected by a pre-boot memory test and a first value of a page offline check flag indicating activation of a page offline operation, wherein the physical address corresponds to a page address which is a unit of memory management by an operating system, and Among them, the activation of the page offline operation indicates that the physical address of the memory failure has not undergone the page offline operation.

19. The method according to claim 18, in, The steps to perform page offline operations include: After the page offline operation is successfully performed, updating the first value of the page offline check flag to a second value of the page offline check flag indicating deactivation of the page offline operation; and When the page offline operation fails, restart is performed while maintaining the first value of the page offline check flag. wherein the activation of the page off-line operation indicates that the physical address of the memory fault has not undergone the page off-line operation, and Among them, the deactivation of the page offline operation indicates that the physical address of the memory failure has been subjected to the page offline operation.

20. A computing device comprising: A basic input / output system read-only memory is configured to store a basic input / output system program, wherein the basic input / output system program is configured to: recording memory failure information generated as a result of performing a pre-boot memory test on the memory, and Loading a boot image of an operating system and at least one auto-execute instruction; as well as a processor configured to execute an operating system and the at least one auto-execute instruction, Wherein, the at least one automatic execution instruction includes: instructions for reading the memory fault information after the step of loading the boot image of the operating system and recording at least a portion of the memory fault information in a page offline information file referenced by a page offline module of the operating system, and The operating system includes instructions for performing a page offline operation using at least some of the memory fault information in the page offline information file.

Images