A method, system, apparatus and medium for managing processing of an interrupt by a server system

Abstract

The application provides a server system management interruption processing method, system, device and medium, the method comprises the following steps: different BIOS bottom application driving programs are customized according to different application scenes; the request timeout length of the driving program is optimized by adjusting the IPMI retry number of the driving program; when a system management interruption occurs, the driving program is called according to the application scene; the current IPMI reporting service is interrupted according to the set IPMI retry number by running the driving program. The application solves the system delay problem by using different customized driving programs in different environments. When processing SMI reporting service exceptions in similar scenes, only 120 milliseconds are consumed, the delay time is reduced by orders of magnitude, and a stable and safe business operation environment is provided for business sensitive customers. The pain points of customers are solved, and the use efficiency and practicability of the server are improved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a method, system, device, and medium for handling server system management interruptions. Background Technology

[0002] A server is a type of computer that runs faster, handles higher loads, and is more expensive than a regular computer. Servers provide computing or application services to other client machines (such as PCs, smartphones, ATMs, and even large equipment like train systems) on a network. Servers feature high-speed CPU processing power, long-term reliable operation, powerful I / O external data throughput capabilities, and better scalability.

[0003] In current server application scenarios, stable system operation without jitter or latency is required, especially when running sensitive business operations. Prolonged system latency can cause significant losses to ongoing services. Occasionally, unexpected restarts or failures of the Server Management Console (BMC) can lead to BMC service interruption. During this BMC unavailability, if a System Management Interrupt (SMI) is triggered by memory or PCIe CE issues, calling IPMI to report information to the BMC, the IPMI service cannot complete due to the BMC's absence, becoming stuck in the SMM service and causing severe system latency. The latency is approximately 10 seconds, specifically due to the requirement to perform 50,000 SMM IPMI retry attempts. The system only resumes normal operation after the retry completes, resulting in a lengthy process that impacts business continuity, work efficiency, and server stability. Summary of the Invention

[0004] To address the above problems, the present invention aims to provide a method, system, device, and medium for handling server system management interruptions, which solves the system latency problem by using different customized drivers in different environments.

[0005] To achieve the above objectives, this invention provides the following technical solution: a method for handling server system management interruptions, comprising:

[0006] Different BIOS low-level application drivers can be customized according to different application scenarios;

[0007] Optimize the driver's request timeout duration by adjusting the number of IPMI retry attempts.

[0008] When a system management interrupt occurs, the driver is invoked according to the application scenario;

[0009] Run the driver to interrupt the current IPMI reporting service based on the set number of IPMI retry attempts.

[0010] Furthermore, the customization of different BIOS underlying application drivers according to different application scenarios includes: creating a DXE driver in the BIOS for BIOS post-processing scenarios, enabling the server to support IPMI services defined by the DXE driver in BIOS post-processing scenarios.

[0011] Furthermore, the customization of different BIOS underlying application drivers according to different application scenarios also includes:

[0012] Create an SMM driver in the BIOS for OS scenarios, enabling the server to support IPMI services defined by the SMM driver in OS scenarios.

[0013] Furthermore, the optimization of the driver's request timeout duration by adjusting the number of IPMI retry attempts includes:

[0014] Set the IPMI retry count for the DXE driver to 50,000.

[0015] Furthermore, the optimization of the driver's request timeout duration by adjusting the number of IPMI retry attempts also includes:

[0016] Set the IPMI retry count of the SMM driver to 1000 and the request timeout duration of the driver to 120 milliseconds.

[0017] Furthermore, the step of calling the driver according to the application scenario after a system management interruption includes: if the current scenario is a BIOS post-processor scenario, then the DXE driver is called; if the current scenario is an OS scenario, then the SMM driver is called.

[0018] Accordingly, the present invention also discloses a server system management interrupt handling system, including: a program customization module for customizing different BIOS underlying application drivers according to different application scenarios; and an optimization module for optimizing the request timeout duration of the driver by adjusting the number of IPMI retryes of the driver.

[0019] The calling module is used to invoke the driver program according to the application scenario when a system management interrupt occurs;

[0020] The execution module is used to run the driver and interrupt the current IPMI reporting service according to the set number of IPMI retry attempts.

[0021] Furthermore, the program customization module is specifically used to: create a DXE driver in the BIOS for BIOS post-processing scenarios, enabling the server to support the IPMI service defined by the DXE driver in BIOS post-processing scenarios; and create an SMM driver in the BIOS for OS scenarios, enabling the server to support the IPMI service defined by the SMM driver in OS scenarios.

[0022] Furthermore, the optimization module is specifically used to: set the IPMI retry count for the DXE driver to 50,000 times; and set the IPMI retry count for the SMM driver to 1,000 times.

[0023] Accordingly, the present invention discloses a server system management interruption handling device, comprising:

[0024] Memory, used to store the handlers for server system management interrupts;

[0025] A processor, when executing the server system management interrupt handler, implements the steps of the server system management interrupt handling method as described in any of the above.

[0026] Accordingly, the present invention discloses a readable storage medium storing a server system management interrupt handler, which, when executed by a processor, implements the steps of the server system management interrupt handling method described in any of the above claims.

[0027] Compared with existing technologies, the advantages of this invention are as follows: This invention discloses a method, system, device, and medium for handling server system management interruptions. Based on the basic principles of BIOS, it creates two IPMI drivers, DXE and SMM, in the BIOS. This supports the use of the IPMI service defined by the DXE driver in BIOS POST scenarios and the use of the defined SMM IPMI driver in OS scenarios. Specifically, the SMM driver defines a verified, secure, and reliable IPMI service timeout. In the event of a BMC service interruption and an SMI report, the current IPMI reporting service is interrupted as soon as possible, allowing the system to recover quickly and shortening the delay time caused by SMI reporting, enabling the server to resume business operations in a shorter time.

[0028] After using this invention, processing SMI reporting services in similar scenarios only requires 120 milliseconds, a significant reduction in latency, providing a stable and secure business operating environment for business-sensitive customers. This solves customer pain points and improves server efficiency and usability.

[0029] Therefore, it is evident that the present invention has outstanding substantive features and significant progress compared with the prior art, and the beneficial effects of its implementation are also obvious. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0031] Figure 1 This is a flowchart illustrating a specific embodiment of the present invention.

[0032] Figure 2 This is a system structure diagram of a specific embodiment of the present invention.

[0033] In the diagram, 1 is the program customization module; 2 is the optimization module; 3 is the calling module; and 4 is the execution module. Detailed Implementation

[0034] The core of this invention is to provide a method for handling server system management interruptions. In existing technologies, when the BMC service is unavailable, if scenarios such as memory or PCIe CE trigger SMI to call IPMI to report information to the BMC, the IPMI service cannot complete due to the BMC's absence, getting stuck in the SMM service and causing severe system delays. The delay is approximately 10 seconds, specifically due to the requirement to support 50,000 SMM IPMI retry attempts. Only after the retry completes will the current reporting action exit and the system resume normal operation. This prolonged delay impacts user business continuity, work efficiency, and server stability.

[0035] The server system management interruption handling method provided by this invention firstly customizes different BIOS underlying application drivers according to different application scenarios. Then, it optimizes the driver's request timeout duration by adjusting the number of IPMI retry attempts. When a system management interruption occurs, the driver is invoked according to the application scenario. Finally, the driver is run, interrupting the current IPMI reporting service according to the set number of IPMI retry attempts. Therefore, this invention solves the system latency problem by using different customized drivers in different environments. When handling SMI reporting services in similar scenarios, it only takes 120 milliseconds, achieving an order-of-magnitude reduction in latency and providing a stable and secure business operating environment for business-sensitive customers. It addresses customer pain points and improves server efficiency and usability.

[0036] To enable those skilled in the art to better understand the present invention, the invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0037] Example 1:

[0038] like Figure 1 As shown, this embodiment provides a method for handling server system management interruptions, including the following steps:

[0039] S1: Customize different BIOS underlying application drivers according to different application scenarios.

[0040] Specifically, a DXE driver is created in the BIOS for BIOS post-processing scenarios, enabling the server to support the IPMI service defined by the DXE driver in BIOS post-processing scenarios. An SMM driver is also created in the BIOS for OS scenarios, enabling the server to support the IPMI service defined by the SMM driver in OS scenarios.

[0041] S2: Optimize the driver's request timeout duration by adjusting the number of IPMI retry attempts.

[0042] Specifically, the IPMI retry count for the DXE driver is set to 50,000. The IPMI retry count for the SMM driver is set to 1,000, and the driver's request timeout is set to 120 milliseconds.

[0043] In this step, the timeout setting in the driver is optimized based on the actual application scenario (the timeout time is determined by the number of IPMI retry attempts). Because the time sensitivity differs between BIOS POST and OS scenarios, the IPMI retry count in the driver for BIOS POST scenarios is specifically defined as 50,000 times, while the IPMI retry count in the driver for OS scenarios is defined as 1,000 times. This has been repeatedly verified to be stable and reliable. This achieves the goal of not affecting the accuracy of actual SMI information reporting while avoiding system delays caused by SMI information reporting in the event of BMC service anomalies.

[0044] S3: When a system management interrupt occurs, the driver is invoked according to the application scenario.

[0045] Specifically, when a system management interrupt occurs, if the current scenario is a BIOS post-processor scenario, the DXE driver is called; if the current scenario is an OS scenario, the SMM driver is called.

[0046] S4: Run the driver and interrupt the current IPMI reporting service according to the set number of IPMI retry attempts.

[0047] Therefore, this method customizes different timeout times based on the type of driver called in different scenarios, reducing the system latency from 10 seconds when a BMC anomaly occurs to 120 milliseconds in this method. The above system latency is determined by the number of IPMI retry attempts. In the 120-millisecond BMC anomaly SMI reporting scenario, the latency is negligible, essentially avoiding the jitter risk caused by system latency.

[0048] This embodiment provides a method for handling server system management interruptions. Two IPMI drivers, DXE and SMM, are created in the BIOS. The DXE driver is used for IPMI services in BIOS POST scenarios, while the SMM driver is used in OS scenarios. The SMM driver defines a verified, secure, and reliable IPMI service timeout. When a BMC service interruption occurs and an SMI report is generated, the current IPMI reporting service is interrupted as quickly as possible to allow the system to recover quickly, reducing the delay caused by SMI reporting and enabling the server to resume business operations in a shorter time.

[0049] Example 2:

[0050] Based on Example 1, such as Figure 2 As shown, the present invention also discloses a server system management interrupt handling system, including: a program customization module 1, an optimization module 2, a calling module 3, and an execution module 4.

[0051] Program customization module 1 is used to customize different BIOS low-level application drivers according to different application scenarios. Specifically, program customization module 1 is used to: create a DXE driver in the BIOS for BIOS POST scenarios, enabling the server to support the IPMI service defined by the DXE driver in BIOS POST scenarios; and create an SMM driver in the BIOS for OS scenarios, enabling the server to support the IPMI service defined by the SMM driver in OS scenarios.

[0052] Optimization module 2 is used to optimize the request timeout duration of the driver by adjusting the number of IPMI retry attempts. Specifically, optimization module 2 sets the number of IPMI retry attempts for the DXE driver to 50,000 and the number of IPMI retry attempts for the SMM driver to 1,000.

[0053] Module 3 is used to invoke the driver program according to the application scenario when a system management interrupt occurs.

[0054] Execution module 4 is used to run the driver and interrupt the current IPMI reporting service according to the set number of IPMI retry attempts.

[0055] This embodiment provides a server system management interrupt handling system, which reduces the latency required for SMI reporting services to 120 milliseconds in a given scenario. This order of magnitude reduction provides a stable and secure business operating environment for business-sensitive customers. It addresses customer pain points and improves server efficiency and usability.

[0056] Example 3:

[0057] This embodiment discloses a server system management interrupt handling device, including a processor and a memory; wherein, when the processor executes the server system management interrupt handling program stored in the memory, it performs the following steps:

[0058] 1. Customize different BIOS underlying application drivers according to different application scenarios.

[0059] 2. Optimize the driver's request timeout duration by adjusting the number of IPMI retry attempts.

[0060] 3. When a system management interruption occurs, the driver program is invoked according to the application scenario.

[0061] 4. Run the driver and interrupt the current IPMI reporting service according to the set number of IPMI retry attempts.

[0062] Furthermore, the server system management interruption handling device in this embodiment may further include:

[0063] The input interface is used to acquire the handler for server system management interrupts imported from external sources and save the acquired handler to the memory. It can also be used to acquire various instructions and parameters transmitted from external terminal devices and transmit them to the processor, so that the processor can perform corresponding processing using these instructions and parameters. In this embodiment, the input interface may specifically include, but is not limited to, a USB interface, a serial interface, a voice input interface, a fingerprint input interface, a hard disk read interface, etc.

[0064] An output interface is used to output various data generated by the processor to connected terminal devices, so that other terminal devices connected to the output interface can obtain the various data generated by the processor. In this embodiment, the output interface may include, but is not limited to, a USB interface, a serial interface, etc.

[0065] A communication unit is used to establish a remote communication connection between the server system management interruption processing device and an external server, so that the server system management interruption processing device can mount the image file to the external server. In this embodiment, the communication unit may specifically include, but is not limited to, a remote communication unit based on wireless communication technology or wired communication technology.

[0066] The keyboard is used to acquire various parameter data or commands input by the user through real-time keystrokes.

[0067] The monitor is used to display relevant information in real time regarding the process of locating a short circuit in the server's power supply line.

[0068] A mouse can be used to assist users in inputting data and simplifying user operations.

[0069] Example 4:

[0070] This embodiment also discloses a readable storage medium, which includes random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art. The readable storage medium stores a server system management interrupt handler, which, when executed by a processor, performs the following steps:

[0071] 1. Customize different BIOS underlying application drivers according to different application scenarios.

[0072] 2. Optimize the driver's request timeout duration by adjusting the number of IPMI retry attempts.

[0073] 3. When a system management interruption occurs, the driver program is invoked according to the application scenario.

[0074] 4. Run the driver and interrupt the current IPMI reporting service according to the set number of IPMI retry attempts.

[0075] In summary, this invention addresses system latency issues by using different customized drivers in different environments. When handling SMI reporting services in similar scenarios, it only requires 120 milliseconds, achieving a significant reduction in latency and providing a stable and secure business operating environment for business-sensitive customers. This solves customer pain points and improves server efficiency and usability.

[0076] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. The methods disclosed in the embodiments are described simply because they correspond to the systems disclosed in the embodiments; relevant details can be found in the method section.

[0077] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0078] In the embodiments provided by this invention, it should be understood that the disclosed systems, methods, and approaches can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between systems or units may be electrical, mechanical, or other forms.

[0079] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0080] In addition, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit.

[0081] Similarly, in the various embodiments of the present invention, each processing unit can be integrated into a functional module, or each processing unit can exist physically, or two or more processing units can be integrated into a functional module.

[0082] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0083] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0084] The foregoing has provided a detailed description of the server system management interrupt handling method, system, apparatus, and readable storage medium provided by this invention. Specific examples have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of this invention. It should be noted that those skilled in the art can make various improvements and modifications to this invention without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this invention.

Claims

1. A method for handling server system management interruptions, characterized in that, include: Different BIOS low-level application drivers can be customized according to different application scenarios; Optimize the driver's request timeout duration by adjusting the number of IPMI retry attempts. When a system management interrupt occurs, the driver is invoked according to the application scenario; Run the driver to interrupt the current IPMI reporting service according to the set number of IPMI retry attempts; The customization of different BIOS low-level application drivers according to different application scenarios includes: Create a DXE driver in the BIOS for BIOS post-processing scenarios, enabling the server to support IPMI services defined by the DXE driver in BIOS post-processing scenarios; The method of customizing different BIOS low-level application drivers according to different application scenarios also includes: Create an SMM driver in the BIOS for OS scenarios, enabling the server to support IPMI services defined by the SMM driver in OS scenarios; The optimization of the driver's request timeout duration by adjusting the number of IPMI retry attempts includes: Set the IPMI retry count for the DXE driver to 50,000. The method of optimizing the driver's request timeout duration by adjusting the number of IPMI retryes also includes: Set the IPMI retry count for the SMM driver to 1000; The timeout duration is determined by the number of IPMI retry attempts. The time sensitivity differs between BIOS post-processing and OS scenarios. The IPMI retry attempt count is configured differently based on the time sensitivity of different scenarios and has been verified to ensure the accuracy of SMI information reporting while avoiding system latency.

2. The method for handling server system management interruptions according to claim 1, characterized in that, When a system management interruption occurs, the driver is invoked according to the application scenario, including: When a system management interrupt occurs, if the current scenario is a BIOS post-processor scenario, the DXE driver is invoked; if the current scenario is an OS scenario, the SMM driver is invoked.

3. A server system management interrupt handling system, characterized in that, include: The program customization module is used to customize different BIOS underlying application drivers according to different application scenarios; The optimization module is used to optimize the request timeout duration of the driver by adjusting the number of IPMI retryes. The calling module is used to invoke the driver program according to the application scenario when a system management interrupt occurs; The execution module is used to run the driver and interrupt the current IPMI reporting service according to the set number of IPMI retry attempts. The program customization module is specifically used for: creating a DXE driver in the BIOS for BIOS post-scenes, enabling the server to support the IPMI service defined by the DXE driver in BIOS post-scenes; and creating an SMM driver in the BIOS for OS-scenes, enabling the server to support the IPMI service defined by the SMM driver in OS-scenes. The optimization module is specifically used to: set the IPMI retry count of the DXE driver to 50,000 times; and set the IPMI retry count of the SMM driver to 1,000 times. The timeout duration is determined by the number of IPMI retry attempts. The time sensitivity differs between BIOS post-processing and OS scenarios. The IPMI retry attempt count is configured differently based on the time sensitivity of different scenarios and has been verified to ensure the accuracy of SMI information reporting while avoiding system latency.

4. A device for handling server system management interruptions, characterized in that, include: Memory, used to store the handlers for server system management interrupts; A processor, when executing the server system management interrupt handler, implements the steps of the server system management interrupt handling method as claimed in any one of claims 1 to 2.

5. A readable storage medium, characterized in that: The readable storage medium stores a server system management interrupt handler, which, when executed by a processor, implements the steps of the server system management interrupt handling method as described in any one of claims 1 to 2.

Images