CN116881091A - System event log reporting method, device, chip, equipment and storage medium - Google Patents
System event log reporting method, device, chip, equipment and storage medium Download PDFInfo
- Publication number
- CN116881091A CN116881091A CN202311156576.2A CN202311156576A CN116881091A CN 116881091 A CN116881091 A CN 116881091A CN 202311156576 A CN202311156576 A CN 202311156576A CN 116881091 A CN116881091 A CN 116881091A
- Authority
- CN
- China
- Prior art keywords
- command
- firmware
- system event
- event log
- operating system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000006870 function Effects 0.000 claims description 37
- 238000012545 processing Methods 0.000 claims description 19
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000007246 mechanism Effects 0.000 abstract description 9
- 238000004891 communication Methods 0.000 abstract description 5
- 230000004044 response Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 108010028984 3-isopropylmalate dehydratase Proteins 0.000 description 1
- 230000002547 anomalous effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005059 dormancy Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000006266 hibernation Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3024—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a central processing unit [CPU]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/30—Arrangements for executing machine instructions, e.g. instruction decode
- G06F9/30003—Arrangements for executing specific machine instructions
- G06F9/30076—Arrangements for executing specific machine instructions to perform miscellaneous control operations, e.g. NOP
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a system event log reporting method, a system event log reporting device, a system event log reporting chip, a system event log reporting device, a system event log reporting equipment and a storage medium. According to the system event log reporting method provided by the application, by utilizing the characteristic that the second firmware has the communication capability with the BMC, when the operating system calls the first firmware to execute the system event, the first firmware instructs the second firmware to send the log of the executed system event to the BMC for recording, so that the ARM architecture server chip can report the system event log to the BMC for recording even if the ARM architecture server chip does not support an SMM mechanism.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a system event log reporting method, device, chip, device, and storage medium.
Background
Server chips include x86 architecture chips represented by Intel and AMD, which have been developed for many years, and ARM architecture chips, which have been developed in recent years. In order to be compatible with the various server management functions of the x86 architecture chip, the ARM architecture chip needs to support the same various server management functions as the x86 architecture chip, for example, in an operation and maintenance scenario, a management function of recording a System Event Log (SEL) for a System processor power management Event such as restarting, shutdown, dormancy, hot plug, and the like, i.e. a System Event Log (SEL) recording function.
For the SEL recording function, when software uses a reboot or shutdown command of an operating system to restart or shut down a server and other system processor power management events, since the x86 architecture chip supports a system management mode (System Management Mode, SMM) mechanism, the software can trigger a system management interrupt (System Management Interrupt, SMI) through the x86 architecture chip, and the x86 architecture chip executes an interrupt processing function (i.e., SMI Handler) of system management in SMM to report the system processor power management events to a baseboard management controller (Baseboard Management Controller, BMC) for recording.
However, the ARM architecture chip does not support the SMM mechanism, and cannot report the system processor power management event to the BMC for recording.
Disclosure of Invention
The application discloses a system event log reporting method, a device, a chip, equipment and a storage medium, which can solve the problem that an ARM architecture chip cannot report a system processor power management event to a BMC for recording because the ARM architecture chip does not support an SMM mechanism.
According to a first aspect of the embodiment of the present application, a system event log reporting method is provided, and is applied to an ARM architecture chip, where the chip is connected to a baseboard management controller BMC, and the chip at least includes an operating system, a first firmware and a second firmware, and the method includes:
the operating system receives a first command and sends a second command to the first firmware according to the first command, wherein the first command is a command for indicating the operating system to execute a system event, and the second command is a command for indicating the first firmware to execute the system event by the operating system;
the first firmware receives a second command and sends a third command to the second firmware according to the second command, wherein the third command is a command for the first firmware to instruct the second firmware to send a system event log to the baseboard management controller BMC;
the second firmware receives the third command and sends the system event log to the baseboard management controller BMC according to the third command.
Optionally, the operating system includes an operating system power management module OSPM, and the step of the operating system sending the second command to the first firmware according to the first command specifically includes:
the operating system converts the first command into a second command through the operating system power management module OSPM and sends the second command to the first firmware.
Optionally, the operating system power management module OSPM writes a second command to the system register to send to the first firmware.
Optionally, the step of the first firmware sending the third command to the second firmware according to the second command specifically includes:
the first firmware converts the second command into a third command through a processing function corresponding to the second command, and transmits the third command to the second firmware.
Optionally, the first firmware writes the third command into the shared memory through a processing function corresponding to the second command to send to the second firmware.
Optionally, the step of the second firmware sending the system event log to the baseboard management controller BMC according to the third command includes:
and the second firmware runs a management mode interface processing function MMI Handle corresponding to the third command and sends the system event log to the baseboard management controller BMC.
According to a second aspect of the embodiment of the present application, a system event log reporting device is provided, and is integrated in an ARM architecture chip, where the chip is connected to a baseboard management controller BMC, and the chip at least includes an operating system, a first firmware, and a second firmware, and the device includes:
the first receiving and sending module is used for receiving a first command through the operating system and sending a second command to the first firmware according to the first command, wherein the first command is a command for indicating the operating system to execute a system event, and the second command is a command for indicating the operating system to execute the system event by the first firmware;
the second receiving and sending module is used for receiving a second command through the first firmware and sending a third command to the second firmware according to the second command, wherein the third command is a command for the first firmware to instruct the second firmware to send the system event log to the baseboard management controller BMC;
and the third receiving and transmitting module is used for receiving a third command through the second firmware and transmitting the system event log to the baseboard management controller BMC according to the third command.
According to a third aspect of the embodiment of the present application, there is provided a chip, including a memory and a processor, where the memory stores computer executable instructions, and the processor implements the system event log reporting method provided in the first aspect of the embodiment of the present application when executing the computer executable instructions stored in the memory.
According to a fourth aspect of embodiments of the present application, there is provided an electronic device comprising a baseboard management controller BMC and a chip as provided in the third aspect of embodiments of the present application connected thereto.
According to a fifth aspect of an embodiment of the present application, there is provided a computer-readable storage medium including computer-executable instructions, which when executed by a processor implement a system event log reporting method as provided in the first aspect of the embodiment of the present application.
The technical scheme provided by the embodiment of the application can comprise the following beneficial effects:
according to the system event log reporting method provided by the application, when the operating system calls the first firmware to execute the system event, the first firmware instructs the second firmware to send the log of the executed system event to the BMC for recording, so that the ARM architecture server chip can report the system event log to the BMC for recording even if the ARM architecture server chip does not support the SMM mechanism.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and together with the description, serve to explain the principles of the specification.
Fig. 1 is a flow chart of a system event log reporting method according to an embodiment of the present application;
FIG. 2 is a schematic structural diagram of a system event log reporting device according to another embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to another embodiment of the present application.
Description of the embodiments
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the application. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
In order to better understand the technical solutions provided by the embodiments of the present application and make the above objects, features and advantages of the embodiments of the present application more comprehensible, the following description of the method embodiments provided by the embodiments of the present application is given with reference to the accompanying drawings.
The System Event Log (SEL) may record various System events (such as a power management Event of a System processor such as restarting, shutdown, hibernation, etc.) of an Operating System (OS), and is often applied in an operation and maintenance scenario of a server. Typically, servers in a data center all need to support SEL reporting functions in order for operation and maintenance personnel to analyze anomalies by SEL when the server is anomalous.
However, current ARM architecture server chips do not preset a port to provide a channel for software to trigger a system management interrupt (System Management Interrupt, SMI) to enter a system management mode (System Management Mode, SMM) to report SEL to a baseboard management controller (Baseboard Management Controller, BMC) for recording, as in x86 architecture server chips, i.e., current ARM architecture server chips do not support the SMM mechanism and cannot report SEL to the BMC for recording.
The application provides a system event log reporting method, which can realize the reporting of an SEL through Firmware (Firmware) of an ARM architecture chip and solve the problem that the current ARM architecture server chip does not support an SMM mechanism and can not report the SEL to a BMC for recording.
The system event log reporting method provided by the application is described in detail below by way of an embodiment:
it should be noted that, in this embodiment, the System event log reporting method provided by the present application is applied to a System on Chip (SoC) Chip based on an ARM architecture. The chip at least comprises an operating system, a first firmware and a second firmware. The operating system is in the common World (Normal World) of ARM architecture chips. Normal World is used to indicate an unsafe state. The first firmware and the second firmware are in the Secure World (Secure World) of the ARM architecture chip. Secure World is used to indicate a Secure state. The first firmware may be used to operate hardware resources of the chip to perform system events. For example, the first firmware may be ARM trusted firmware (ARM Trusted Firmware, ATF). The second firmware is deployed to be communicable with the off-chip BMC. For example, the second firmware may be a Secure Partition (SP), which is firmware deployed to upload the SEL to the BMC.
Referring to fig. 1, fig. 1 is a flowchart of a system event log reporting method according to an embodiment of the present application. As shown in fig. 1, the method for reporting a system event log provided by the application comprises the following steps:
step 10: the operating system receives the first command and sends a second command to the first firmware according to the first command. Wherein the first command is a command instructing the operating system to execute a system event and the second command is a command instructing the operating system to execute a system event by the first firmware.
In this embodiment, when the operating system receives a command issued by a user or an application that instructs the operating system to execute a system event, the operating system converts the first command into a second command through an operating system power management module (Operating System Power Management, OSPM) and sends the second command to the first firmware. It should be noted that, the OSPM communicates with the first firmware through a power state collaboration interface (Power State Coordination Interface, PSCI) protocol, and the OSPM allows the operating system to control power management, whose functions are well known in the art and are not repeated in the present application.
In other embodiments, the OSPM may write the second command to the system register to send to the first firmware, or send the second command to the first firmware in other ways, and the application is not limited to a specific sending manner.
Specifically, the operating system converts a command for executing a system event into a function identifier function ID (i.e., a second command) corresponding to the system event through OSPM, and writes the function identifier function ID as a parameter into a system register to instruct the first firmware to execute the system event.
For example, when the operating system receives a user or application triggered command instructing the operating system to perform a Restart (RESET), the operating system triggers the OSPM to process a restart event. OSPM converts the command to perform a Restart (RESET) into a corresponding value psci_system_reset=0x 84000009 (i.e., a function ID corresponding to the restart event) and writes 0X84000009 as a parameter to SYSTEM register X0 to instruct the first firmware to perform a restart event. Or when the operating system receives a command triggered by a user or an application and indicating the operating system to execute shutdown (OFF), the operating system triggers the OSPM to process a restart event. OSPM converts the command to perform a shutdown (OFF) to the corresponding value psci_system_off=0x 84000008 (i.e., the fusion ID corresponding to the shutdown event), and writes 0X84000008 as a parameter to the SYSTEM register X0 to instruct the first firmware to perform the shutdown event.
Step 12: the first firmware receives the second command and sends a third command to the second firmware according to the second command. Wherein the third command is a command for the first firmware to instruct the second firmware to send the system event log to the baseboard management controller BMC.
In this embodiment, when the first firmware receives the second command, the first firmware converts the second command into the third command through a processing function corresponding to the second command, and sends the third command to the second firmware.
In other embodiments, the first firmware may write the third command to the shared memory for transmission to the second firmware via a processing function corresponding to the second command. Alternatively, the third command may be sent to the second firmware by another method, and the present application is not limited to a specific sending method.
Specifically, when the first firmware acquires the function identifier function ID (i.e., the second command) corresponding to the system event from the system register X0, the first firmware runs the processing function corresponding to the function identifier function ID, converts the function identifier function ID corresponding to the system event into the globally unique identifier GUID (i.e., the third command) corresponding to the system event through the management mode Communication protocol (i.e., the mm_communication protocol), and writes the globally unique identifier GUID corresponding to the system event as a parameter into the management mode cache MM Buffer (i.e., the shared memory) to instruct the second firmware to send the system event log to the baseboard management controller BMC.
Step 14: the second firmware receives the third command and sends the system event log to the baseboard management controller BMC according to the third command.
In this embodiment, when the second firmware receives the third command, the second firmware runs the management mode interface processing function MMI Handle corresponding to the third command to send SEL to the BMC for recording.
Specifically, when the second firmware acquires the globally unique identifier GUID corresponding to the system event from the management mode cache MM Buffer, the second firmware runs the management mode interface processing function MMI Handle corresponding to the globally unique identifier GUID. MMI Handle sends SEL to BMC for recording via intelligent platform management interface (Intelligent Platform Management Interface, IPMI) protocol.
When an operating system calls a first firmware capable of operating hardware resources to execute a system event, a second firmware capable of communicating with a BMC is called by the first firmware to report the system event log to the BMC for recording by utilizing the existing resources of the ARM architecture chip. The system event log reporting method has strong applicability.
In other embodiments, the method for reporting a system event log provided by the present application may further include the following steps:
step 16: and after receiving the response of the recorded system event log returned by the BMC, the second firmware sends the response of the third command to the first firmware.
Step 18: after receiving the response of the third command returned by the second firmware, the first firmware continues to execute the system event according to the second command. Specifically, after receiving the response of the third command returned by the second firmware, the first firmware continues to write the function identifier function ID corresponding to the system event into the system register or configures a general purpose input output (General Purpose Input Output, GPIO) according to the function identifier function ID corresponding to the system event to control the chip to execute the system event.
According to the system event log reporting method provided by the application, by utilizing the characteristic that the second firmware has the communication capability with the BMC, when the operating system calls the first firmware to execute the system event, the first firmware instructs the second firmware to send the log of the executed system event to the BMC for recording, so that the ARM architecture server chip can report the system event log to the BMC for recording even if the ARM architecture server chip does not support an SMM mechanism.
Correspondingly, the application also provides a system event log reporting device. The device is integrated on an SoC type chip based on an ARM architecture. Referring to fig. 2, fig. 2 is a schematic structural diagram of a system event log reporting device according to another embodiment of the present application. As shown in fig. 2, the system event log reporting apparatus 200 provided by the present application includes: a first receiving and transmitting module 210, a second receiving and transmitting module 220, and a third receiving and transmitting module 230. The first receiving and transmitting module 210 includes an operating system 212. The second receiving and transmitting module 220 includes a first firmware 222, wherein the first firmware 222 may be used to operate hardware resources of the chip to perform system events and communicate with the second firmware 230, for example, the first firmware 222 may be an ATF. The third receiving and transmitting module 230 includes a second firmware 232, wherein the second firmware 232 may communicate with the first firmware 222 and the BMC, respectively, and the second firmware 232 may be an SP, for example.
In the present embodiment, the first receiving and sending module 210 is configured to receive a first command through the operating system 212 and send a second command to the first firmware 222 according to the first command. Wherein the first command is a command instructing the operating system 212 to execute a system event and the second command is a command instructing the operating system 212 to instruct the first firmware 222 to execute a system event. The operating system 212 converts the first command into a second command through the operating system power management module OSPM and sends the second command to the first firmware 222.
In other embodiments, the operating system power management module OSPM writes a second command to the system register to send to the first firmware 222. Alternatively, the second command may be sent to the first firmware 222 by other means, and the present application is not limited to a specific sending manner.
In this embodiment, the second receiving and sending module 220 is configured to receive a second command through the first firmware 222 and send a third command to the second firmware 232 according to the second command, where the third command is a command that the first firmware 222 instructs the second firmware 232 to send the system event log to the baseboard management controller BMC. The first firmware 222 converts the second command into a third command through a processing function corresponding to the second command, and transmits the third command to the second firmware 232.
In other embodiments, the first firmware 222 may write the third command to the shared memory for transmission to the second firmware 232 via a processing function corresponding to the second command. Alternatively, the third command may be sent to the second firmware 232 by another method, and the present application is not limited to a specific sending method.
In this embodiment, the third receiving and sending module 230 is configured to receive the third command through the second firmware 232, and send the system event log to the baseboard management controller BMC according to the third command. The second firmware 232 runs a management mode interface processing function MMI Handle corresponding to the third command to send the system event log to the baseboard management controller BMC.
In other embodiments, the third receiving and sending module 230 is further configured to send, through the second firmware 232, a response of the third command to the first firmware 222 after receiving a response of the logged system event log returned by the BMC. The second receiving and sending module is further configured to, after receiving a response of the third command returned by the second firmware 232, continue executing, by the first firmware 222, the system event according to the second command.
It should be noted that, the system event log reporting device provided by the present application corresponds to the system event log reporting method provided by the present application, and the content described in the embodiment of the system event log reporting device may refer to the content described in the embodiment of the system event log reporting method.
According to the system event log reporting device provided by the application, by utilizing the characteristic that the second firmware has the communication capability with the BMC, when the operating system calls the first firmware to execute the system event, the first firmware instructs the second firmware to send the log of the executed system event to the BMC for recording, so that the ARM architecture server chip can report the system event log to the BMC for recording even if the ARM architecture server chip does not support an SMM mechanism.
Correspondingly, the application further provides a chip. The chip is a SoC type chip based on ARM architecture and comprises a memory and a processor. The memory stores computer-executable instructions. The processor executes computer executable instructions stored in the memory to implement a system event log reporting method according to an embodiment of the present application. The memory may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, the memory may be: volatile memory, nonvolatile memory, or similar storage medium. In particular, the memory may be RAM (Radom Access Memory, random access memory), flash memory, a storage drive (e.g., hard drive), a solid state disk, any type of storage disk (e.g., optical disk, DVD, etc.), or a similar storage medium, or a combination thereof. The chips may be data processor (Data Processing Unit, DPU) chips, central processing unit (Central Processing Unit, CPU) chips, and graphics processor (Graphic Processing Unit, GPU) chips, among others.
Correspondingly, the application further provides electronic equipment. Referring to fig. 3, fig. 3 is a schematic structural diagram of an electronic device according to another embodiment of the application. The electronic device 1 may comprise a baseboard management controller BMC30 and a chip 20 provided by the application. The chip 20 and the BMC30 are connected. The chip 20 includes a system event log reporting device 200 provided in the embodiment of the present application. Alternatively, the electronic device 1 may be a server or a cluster of servers of a data center.
Correspondingly, the application also provides a computer readable storage medium, which comprises computer executable instructions, and the computer executable instructions realize the system event log reporting method provided by the embodiment of the application when being executed by a processor.
The foregoing description of the preferred embodiments of the application is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the application.
Claims (10)
1. The utility model provides a system event log reporting method which is characterized in that the method is applied to ARM framework chip, the chip is connected with baseboard management controller BMC, the chip at least comprises operating system, first firmware and second firmware, the method includes:
the operating system receives a first command and sends a second command to the first firmware according to the first command, wherein the first command is a command for indicating the operating system to execute a system event, and the second command is a command for indicating the first firmware to execute the system event by the operating system;
the first firmware receives a second command and sends a third command to the second firmware according to the second command, wherein the third command is a command for the first firmware to instruct the second firmware to send a system event log to the baseboard management controller BMC;
the second firmware receives the third command and sends the system event log to the baseboard management controller BMC according to the third command.
2. The method of claim 1, wherein the operating system includes an operating system power management module OSPM, and wherein the operating system sends the second command to the first firmware according to the first command by:
the operating system converts the first command into a second command through the operating system power management module OSPM and sends the second command to the first firmware.
3. The method of claim 2 wherein the operating system power management module OSPM writes a second command to the system register to send to the first firmware.
4. The method of claim 1, wherein the step of the first firmware sending a third command to the second firmware based on the second command specifically comprises:
the first firmware converts the second command into a third command through a processing function corresponding to the second command, and transmits the third command to the second firmware.
5. The method of claim 4, wherein the first firmware writes a third command to the shared memory for transmission to the second firmware via a processing function corresponding to the second command.
6. The method of claim 1, wherein the step of the second firmware sending the system event log to the baseboard management controller BMC according to the third command comprises:
and the second firmware runs a management mode interface processing function MMI Handle corresponding to the third command and sends the system event log to the baseboard management controller BMC.
7. The utility model provides a system event log reporting device which characterized in that integrates in ARM framework chip, and the chip is connected with baseboard management controller BMC, and the chip includes operating system, first firmware and second firmware at least, the device includes:
the first receiving and sending module is used for receiving a first command through the operating system and sending a second command to the first firmware according to the first command, wherein the first command is a command for indicating the operating system to execute a system event, and the second command is a command for indicating the operating system to execute the system event by the first firmware;
the second receiving and sending module is used for receiving a second command through the first firmware and sending a third command to the second firmware according to the second command, wherein the third command is a command for the first firmware to instruct the second firmware to send the system event log to the baseboard management controller BMC;
and the third receiving and transmitting module is used for receiving a third command through the second firmware and transmitting the system event log to the baseboard management controller BMC according to the third command.
8. A chip comprising a memory and a processor, the memory storing computer executable instructions, the processor implementing the system event log reporting method of any of claims 1 to 6 when executing the computer executable instructions stored in the memory.
9. An electronic device comprising a baseboard management controller BMC and a chip as claimed in claim 8 connected thereto.
10. A computer readable storage medium comprising computer executable instructions which when executed by a processor implement the system event log reporting method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311156576.2A CN116881091B (en) | 2023-09-08 | 2023-09-08 | System event log reporting method, device, chip, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311156576.2A CN116881091B (en) | 2023-09-08 | 2023-09-08 | System event log reporting method, device, chip, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116881091A true CN116881091A (en) | 2023-10-13 |
| CN116881091B CN116881091B (en) | 2024-05-28 |
Family
ID=88257328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311156576.2A Active CN116881091B (en) | 2023-09-08 | 2023-09-08 | System event log reporting method, device, chip, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116881091B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170039151A1 (en) * | 2015-08-05 | 2017-02-09 | American Megatrends, Inc. | Universal intelligent platform management interface (ipmi) host to baseboard management controller (bmc) communication for non-x86 and legacy free systems |
| CN107608868A (en) * | 2017-09-08 | 2018-01-19 | 联想(北京)有限公司 | Log collecting method, baseboard management controller BMC and Magnetic Disk Controler |
| CN108182138A (en) * | 2018-01-24 | 2018-06-19 | 郑州云海信息技术有限公司 | Acquisition methods, system, device and the storage medium of BMC SEL daily records |
| CN108572312A (en) * | 2018-04-12 | 2018-09-25 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | SoC chip test method, device, system and SoC chip test witness plate |
| CN112948157A (en) * | 2021-01-29 | 2021-06-11 | 苏州浪潮智能科技有限公司 | Server fault positioning method, device and system and computer readable storage medium |
| CN114564725A (en) * | 2022-02-28 | 2022-05-31 | 苏州浪潮智能科技有限公司 | Command interaction method, device, equipment and storage medium |
| CN115981956A (en) * | 2022-12-28 | 2023-04-18 | 中科可控信息产业有限公司 | SPDK service process monitoring method, device, equipment, storage medium and program product |
| CN116069538A (en) * | 2023-02-21 | 2023-05-05 | 宁畅信息产业(北京)有限公司 | Fault repairing method and device, electronic equipment and storage medium |
| CN116126772A (en) * | 2023-02-10 | 2023-05-16 | 苏州浪潮智能科技有限公司 | UART serial port management system and method applied to ARM server |
-
2023
- 2023-09-08 CN CN202311156576.2A patent/CN116881091B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170039151A1 (en) * | 2015-08-05 | 2017-02-09 | American Megatrends, Inc. | Universal intelligent platform management interface (ipmi) host to baseboard management controller (bmc) communication for non-x86 and legacy free systems |
| CN107608868A (en) * | 2017-09-08 | 2018-01-19 | 联想(北京)有限公司 | Log collecting method, baseboard management controller BMC and Magnetic Disk Controler |
| CN108182138A (en) * | 2018-01-24 | 2018-06-19 | 郑州云海信息技术有限公司 | Acquisition methods, system, device and the storage medium of BMC SEL daily records |
| CN108572312A (en) * | 2018-04-12 | 2018-09-25 | 中国电子产品可靠性与环境试验研究所（（工业和信息化部电子第五研究所）（中国赛宝实验室）） | SoC chip test method, device, system and SoC chip test witness plate |
| CN112948157A (en) * | 2021-01-29 | 2021-06-11 | 苏州浪潮智能科技有限公司 | Server fault positioning method, device and system and computer readable storage medium |
| CN114564725A (en) * | 2022-02-28 | 2022-05-31 | 苏州浪潮智能科技有限公司 | Command interaction method, device, equipment and storage medium |
| CN115981956A (en) * | 2022-12-28 | 2023-04-18 | 中科可控信息产业有限公司 | SPDK service process monitoring method, device, equipment, storage medium and program product |
| CN116126772A (en) * | 2023-02-10 | 2023-05-16 | 苏州浪潮智能科技有限公司 | UART serial port management system and method applied to ARM server |
| CN116069538A (en) * | 2023-02-21 | 2023-05-05 | 宁畅信息产业(北京)有限公司 | Fault repairing method and device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 知否知否: ""ARMv8-A TrustZone概述"", pages 1 - 5, Retrieved from the Internet <URL:https://blog.csdn.net/qq_24835087/article/details/122636928> * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116881091B (en) | 2024-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6333965B2 (en) | Technology to track wake clock usage | |
| US10049010B2 (en) | Method, computer, and apparatus for migrating memory data | |
| WO2019084916A1 (en) | Method and system for recovering logic in fpga chip, and fpga apparatus | |
| CN103823708B (en) | The method and apparatus that virtual machine read-write requests are processed | |
| US11184435B2 (en) | Message transmission method and apparatus in cluster file system | |
| WO2024007510A1 (en) | Server management method, apparatus and system, and electronic device and readable storage medium | |
| CN109597653A (en) | Method, BIOS and the BMC of BIOS and BMC command interaction | |
| US20190042161A1 (en) | Hard Disk Operation Method and Hard Disk Manager | |
| US10175717B2 (en) | System and method for enhancing real-time clock usage in an information handling system | |
| US20140115112A1 (en) | Server system and message processing method thereof | |
| US11888690B2 (en) | System and method for subscription limitation enforcement in distributed system | |
| US11914725B2 (en) | Operating system agnostic and secure bi-directional data handling | |
| CN106330327B (en) | Method and device for managing enabling state of optical module | |
| US10649832B2 (en) | Technologies for headless server manageability and autonomous logging | |
| CN116701285A (en) | Remote access control apparatus, remote access control method, remote access control device, and computer readable medium | |
| CN116881091B (en) | System event log reporting method, device, chip, equipment and storage medium | |
| CN115981956A (en) | SPDK service process monitoring method, device, equipment, storage medium and program product | |
| CN115981892A (en) | Log reading method and device, electronic equipment and storage medium | |
| US11226862B1 (en) | System and method for baseboard management controller boot first resiliency | |
| CN111459863B (en) | NVME-MI-based chassis management system and method | |
| CN114817134A (en) | Snapshot task monitoring method, device, equipment and medium | |
| US20170154142A1 (en) | Method and apparatus for simulating slow storage disk | |
| JP2001051871A (en) | Remote debugging device | |
| CN114613418B (en) | System and method for NVMe-MI function test of solid state disk | |
| US20240028723A1 (en) | Suspicious workspace instantiation detection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |