Log management method, device and equipment and readable storage medium

Abstract

The invention provides a log management method, device and equipment and a readable storage medium. The method comprises the steps that virtual PCIe equipment is constructed and loaded, and an equipment identifier and a manufacturer identifier are obtained so that an in-band system can recognize the virtual PCIe equipment; configuring a shared memory and a message queue associated with the PCIe device; and according to the interrupt trigger state of the message queue, reading and storing the log data written by the in-band system stored in the shared memory. Through the technical scheme of the invention, the virtual PCIe equipment is constructed and loaded, and the shared memory and the message queue are utilized to realize seamless data interaction with the in-band system in the runtime stage, so that the log data can be reliably collected and stored when the in-band system is abnormal, and the maintainability and fault diagnosis efficiency of the system are remarkably enhanced.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a log management method, device, equipment and readable storage medium. Background Art

[0002] With the development of information technology, the reliability and stability of computing devices such as servers and workstations have become one of the important indicators for measuring product competitiveness. When the operating system (OS) in these devices encounters problems such as performance degradation and kernel panic, timely and effective diagnosis and resolution of the problem is crucial to ensure the stable operation of the system. Kernel panic refers to a self-protection mechanism taken by the operating system to avoid further damage to the system when an unrecoverable error is detected. It usually causes the system to stop working and display a "panic" message. Performance degradation may be caused by improper system resource management, hardware failure or other potential problems.

[0003] Traditional fault diagnosis methods rely on logging and analysis within the operating system. However, this method is inadequate when the operating system crashes or third-party application programs fail. For example, when a system encounters a kernel panic, it is usually difficult to obtain further diagnostic information because the operating system kernel has stopped working. In addition, although the existing kdump mechanism can alleviate this problem to a certain extent, it is not always an ideal solution in practical applications due to its configuration complexity and the requirement for specific hardware support.

[0004] kdump is a Linux kernel crash dump mechanism that can capture the state dump of the system memory when the system crashes to help developers analyze the cause of the crash. However, kdump also has certain limitations. For example, its support for different Linux distributions and kernel versions varies, which may result in the inability to collect the required third-party application logs in some cases. In addition, kdump configuration is more complicated and may be unstable under certain hardware configurations. More importantly, in the case of some operating system crashes, kdump may not be able to successfully start the second kernel, which in turn makes it impossible to obtain the memory dump information at the time of the crash. Summary of the invention

[0005] In view of this, the present specification provides a log management method, device, electronic device, and readable storage medium to improve the above-mentioned problem of difficulty in log collection.

[0006] The specific technical solutions are as follows:

[0007] The present specification provides a log management method, which is applied to a BMC device. The method includes: constructing a virtual PCIe device and loading it, obtaining a device identifier and a manufacturer identifier so that an in-band system can identify the virtual PCIe device; configuring a shared memory and a message queue associated with the PCIe device, wherein the message queue is used for interrupt triggering with the in-band system during the runtime phase, and the shared memory is used for data interaction with the in-band system during the runtime phase; and reading and storing log data written by the in-band system stored in the shared memory according to the interrupt triggering state of the message queue.

[0008] As a technical solution, the log data written by the in-band system stored in the shared memory is read and stored according to the interrupt trigger status of the message queue, including: according to the interrupt trigger status of the message queue, the log data written by the in-band system stored in the shared memory is read, and classified and stored according to different associated third-party applications, wherein the log data written by the in-band system includes log data written by the in-band system to corresponding specific locations of the shared memory according to different third-party applications.

[0009] As a technical solution, the in-band system writes log data to corresponding specific locations of shared memory according to different third-party applications, including log data that the in-band system writes to corresponding specific locations of shared memory according to different third-party applications and occupies a preset fixed-size storage space.

[0010] As a technical solution, the virtual PCIe device is constructed and loaded, and the device identifier and the manufacturer identifier are obtained so that the in-band system can identify the virtual PCIe device, including: enabling the BMC Device function and loading it in the role of the PCIe device.

[0011] The present specification also provides a log management device, which is applied to a BMC device. The device includes: a first module, which is used to construct a virtual PCIe device and load it, and obtain a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device; a second module, which is used to configure a shared memory and a message queue associated with the PCIe device, wherein the message queue is used to trigger an interrupt with the in-band system during the runtime stage, and the shared memory is used to interact with the in-band system during the runtime stage; and a third module, which is used to read and store the log data written by the in-band system stored in the shared memory according to the interrupt triggering state of the message queue.

[0012] As a technical solution, the log data written by the in-band system stored in the shared memory is read and stored according to the interrupt trigger status of the message queue, including: according to the interrupt trigger status of the message queue, the log data written by the in-band system stored in the shared memory is read, and classified and stored according to different associated third-party applications, wherein the log data written by the in-band system includes log data written by the in-band system to corresponding specific locations of the shared memory according to different third-party applications.

[0013] As a technical solution, the in-band system writes log data to corresponding specific locations of shared memory according to different third-party applications, including log data that the in-band system writes to corresponding specific locations of shared memory according to different third-party applications and occupies a preset fixed-size storage space.

[0014] As a technical solution, the virtual PCIe device is constructed and loaded, and the device identifier and the manufacturer identifier are obtained so that the in-band system can identify the virtual PCIe device, including: enabling the BMC Device function and loading it in the role of the PCIe device.

[0015] This specification also provides an electronic device, including a processor and a readable storage medium, wherein the readable storage medium stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the aforementioned log management method.

[0016] This specification also provides a readable storage medium, which stores machine-executable instructions. When the machine-executable instructions are called and executed by a processor, the machine-executable instructions prompt the processor to implement the aforementioned log management method.

[0017] The above technical solution provided in this specification brings at least the following beneficial effects:

[0018] By building a virtual PCIe device and loading it, and using shared memory and message queues to achieve seamless data interaction with the in-band system at runtime, log data can be reliably collected and stored when the in-band system is abnormal, significantly enhancing the system's maintainability and fault diagnosis efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the implementation methods of this specification or the technical solutions in the prior art, the drawings required for use in the implementation methods of this specification or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some implementation methods recorded in this specification. For ordinary technicians in this field, other drawings can also be obtained based on these drawings of the implementation methods of this specification.

[0020] Figure 1 is a flow chart of a log management method in one implementation of this specification;

[0021] Figure 2 is a structural diagram of a log management device in one implementation of this specification;

[0022] Figure 3 It is a hardware structure diagram of an electronic device in one implementation mode of this specification.

[0023] Reference numerals: first module 21 , second module 22 , third module 23 . DETAILED DESCRIPTION

[0024] The terms used in the embodiments of this specification are only for the purpose of describing specific embodiments, rather than limiting this specification. The singular forms of "a", "said" and "the" used in this specification and claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to any or all possible combinations of one or more associated listed items.

[0025] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, in addition, the word "if" used may be interpreted as "at the time of" or "when" or "in response to determining".

[0026] The operating system may encounter various abnormal situations during operation, such as sudden performance degradation, kernel panic, etc. These abnormal situations may cause the system to crash or fail to operate normally. In order to ensure the stable operation and rapid recovery of the system, it is necessary to effectively collect and analyze the operating system logs.

[0027] The collection of operating system logs mainly relies on the in-band system, that is, log collection and analysis are performed within the operating system. However, this approach has some limitations. When a serious abnormality occurs in the operating system, such as a kernel panic, the in-band system may not work properly, resulting in the inability to collect critical crash logs. Some hardware platforms may not support or stably support the operating system's crash dump mechanism, such as Kdump. Existing crash dump mechanisms, such as Kdump, have a relatively complex configuration process and require professional knowledge. This solution may not be able to collect logs from third-party applications, which are equally important for fault analysis and location. When the operating system crashes, professional technicians are required to perform on-site analysis and processing, which increases maintenance costs.

[0028] To overcome the above limitations, the concept of out-of-band management (OOB) was introduced. Out-of-band management allows the computer system to be monitored and managed independently outside the operating system. This method is implemented through hardware devices such as BMC (Baseboard Management Controller), which can obtain system status information through BMC when the operating system crashes or cannot be accessed.

[0029] Although BMC provides out-of-band monitoring and management functions, in actual applications, how to effectively collect and analyze operating system logs, especially when the operating system crashes, is still a challenge. Existing technical solutions, such as Kdump, can achieve crash dumps to a certain extent, but there are problems such as complex configuration and dependence on specific hardware and operating system versions.

[0030] This specification aims to provide an improved method, through the interaction between the BMC device and the operating system, to collect the crash logs of the entire system and third-party application logs when the operating system crashes or an exception occurs, and transfer them to the BMC. This method not only improves the maintainability of the system and reduces maintenance costs, but also improves the out-of-band positioning capability when the in-band system is abnormal.

[0031] The specific technical solution is described below.

[0032] In one embodiment, the present specification provides a log management method, which is applied to a BMC device, and the method includes: constructing a virtual PCIe device and loading it, obtaining a device identifier and a manufacturer identifier so that an in-band system can identify the virtual PCIe device; configuring a shared memory and a message queue associated with the PCIe device, the message queue is used for interrupt triggering with the in-band system during the runtime stage, and the shared memory is used for data interaction with the in-band system during the runtime stage; according to the interrupt triggering status of the message queue, reading and storing the log data written by the in-band system stored in the shared memory.

[0033] Specifically, Figure 1 , including the following steps:

[0034] Step S11, constructing a virtual PCIe device and loading it, obtaining a device identifier and a manufacturer identifier so that the in-band system can recognize the virtual PCIe device.

[0035] Implement a virtual PCI Express (PCIe) device in the BMC. This virtual device will simulate a real PCIe device so that it can be identified in the in-band system, such as the operating system or BIOS system. The process of building a virtual PCIe device involves writing firmware code to implement the basic functions of the device, such as initialization, configuration, and operation. In order to ensure that the in-band system can correctly identify this virtual device, it must be assigned a unique device identifier (Device ID) and vendor identifier (Vendor ID). These two identifiers are assigned by relevant industry standard organizations to distinguish different hardware manufacturers and their products. For example, for a specific virtual PCIe device, its DeviceID may be 0x1234 and the Vendor ID may be 0x5678.

[0036] Once the virtual PCIe device is built, it needs to be loaded into the BMC. The loading process may involve compiling firmware code and adding the device to the system through the BMC's management interface or command line tools. Once loaded, the in-band system can discover and identify the virtual device by querying the PCI address space.

[0037] Step S12, configuring a shared memory and a message queue associated with the PCIe device, wherein the message queue is used for interrupt triggering with the in-band system during the runtime stage, and the shared memory is used for data interaction with the in-band system during the runtime stage.

[0038] Configure the shared memory (MEM_BAR) and message queue (MSG_BAR) associated with the above virtual PCIe device. The shared memory is used to transfer data between the in-band system and the BMC, while the message queue is used to trigger interrupts at runtime to notify the BMC of status changes or logging requests for the in-band system.

[0039] Configuring shared memory involves setting its size and location, ensuring it is large enough to accommodate the expected amount of log data. At the same time, some rules need to be defined to manage how data is stored in shared memory, such as data format, record length, etc. The message queue is used to handle interrupt requests. Whenever the in-band system has a new log entry to record, an interrupt message is sent to the message queue.

[0040] For example, if the in-band system detects an error, it writes an error log in the shared memory and sends an interrupt to the message queue. After the BMC receives the interrupt, it checks the contents of the shared memory and takes appropriate actions.

[0041] Step S13, according to the interrupt triggering state of the message queue, the log data written by the in-band system stored in the shared memory is read and stored.

[0042] When the in-band system generates a log entry that needs to be recorded, it stores the log in the shared memory and sends an interrupt request to the message queue. The BMC listens to the interrupt request in the message queue. Once an interrupt is detected, it immediately reads the data in the shared memory and stores the data in its own persistent storage medium.

[0043] To ensure the integrity of log data, the BMC may implement some additional mechanisms, such as checksums or sequence numbers, to verify the validity of data before storage. In addition, considering the limited storage space, the BMC can also use a circular buffer to only retain the most recent log records, and the old log records will be overwritten by the new records.

[0044] The advantage of this log management method is that even if a serious software error or hardware failure occurs in the in-band system, causing the operating system to fail to operate normally, the BMC can still continue to collect and store log data. This is crucial for fault diagnosis and recovery because it provides valuable debugging information to help administrators or developers locate the problem.

[0045] In one embodiment, the log data written by the in-band system stored in the shared memory is read and stored according to the interrupt trigger status of the message queue, including: reading the log data written by the in-band system stored in the shared memory according to the interrupt trigger status of the message queue, and storing the data according to different associated third-party application categories, wherein the log data written by the in-band system includes log data written by the in-band system to corresponding specific locations of the shared memory according to different third-party applications.

[0046] In one embodiment, the in-band system writes log data to corresponding specific locations of the shared memory according to different third-party applications, including log data that the in-band system writes to corresponding specific locations of the shared memory according to different third-party applications and occupies a preset fixed size storage space.

[0047] In one implementation, the step of constructing and loading a virtual PCIe device, and obtaining a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device, includes: enabling a BMC Device function, and loading the device in the role of a PCIe device.

[0048] In one implementation, the BMC device builds a virtual PCIe device and loads it into the system. This virtual device is transparent to the in-band system, that is, the operating system regards it as a real hardware device. In order to enable the in-band system to identify this virtual device, the BMC device assigns it a unique device identifier (DeviceID) and vendor identifier (VendorID). These identifiers are standard attributes of PCIe devices, and the operating system uses these identifiers to identify and drive the device.

[0049] Assume that a server's BMC device needs to monitor the health of the operating system. The BMC device builds a virtual PCIe device and assigns DeviceID 0x1234 and VendorID 0x5678. The operating system detects this new device during the boot process and loads the corresponding driver based on these identifiers, allowing the operating system to communicate with this virtual device.

[0050] The BMC device configures the shared memory (MEM_BAR) and message queue (MSG_BAR) associated with the virtual PCIe device. The shared memory area allows data exchange between the in-band system and the BMC device, while the message queue is used for interrupt triggering during the operating system runtime.

[0051] For example, the BMC device configures a 1MB shared memory area for the virtual PCIe device. The operating system can send or receive data by reading and writing this memory area. At the same time, the BMC device is also configured with a message queue to send an interrupt signal to the BMC when the operating system needs the BMC's attention to an event (such as log data is available).

[0052] The BMC device decides whether to read the log data stored in the shared memory based on the interrupt trigger status in the message queue. When the operating system is abnormal or needs to record logs, it writes the log data to the shared memory and sends an interrupt signal to the message queue to notify the BMC device that the log data is ready.

[0053] Suppose the operating system detects a kernel error and decides to log the error. The operating system writes the error information to the previously configured shared memory area and sends an interrupt signal to the message queue. After the BMC device detects the interrupt signal, it reads the log data from the shared memory and stores it in its own storage device, such as EMMC. In this way, even if the operating system crashes, these critical log data can be safely saved in the BMC device for subsequent analysis and troubleshooting.

[0054] Through this implementation, the BMC device can monitor and collect the log data of the operating system in real time, and maintain the integrity and availability of the log data even when the operating system crashes or other abnormal situations occur. This greatly improves the maintainability and reliability of the system, reduces maintenance costs, and enhances the ability to respond to system abnormalities.

[0055] In one implementation, based on the BMC Device function of AST2600, the BIOS and operating system can identify the device based on the unique DeviceID and VendorID in the role of PCIe device. The device has a shared memory MEM_BAR and a message queue MSG_BAR to meet the operating system's requirements for interrupt triggering and data interaction with BMC during the runtime stage.

[0056] The interactive content is fixed in a specific area mapped in MEM_BAR. The BMC side and the HOST side define multiple command words to determine the purpose, usage rules, and enable status of different functions (only the enable status of sub-functions is independently controlled from the enable status of BMC Device) for expansion.

[0057] The use of MEM_BAR by BMC and HOST (BIOS / OS) supports the allocation and definition of structures with the main functions of "addition, deletion, modification and query". After the function is enabled, the logs collected by the OS side will be saved to different locations of MEM_BAR according to different third-party application addresses, occupying a total of 512KB bytes. After the function is enabled, the occupied space size is fixed, and the content storage adopts a rotation strategy, that is, storage starts at the offset specified by the Header, and starts to rotate when the storage size reaches the size specified in the Header. The OS side first sends an interrupt to refresh the full log to the BMC side log, and then clears the content of the used memory and starts to store again at the offset.

[0058] The BMC-side log also adopts a rotation strategy. To prevent a single log from occupying too much EMMC space when it is continuously written, it is renamed to log.1 after reaching 1M in size. The new log content is stored in the log, and a maximum of 10 copies are saved.

[0059] In one embodiment, Figure 2This specification also provides a log management device, which is applied to BMC equipment. The device includes: a first module, which is used to build a virtual PCIe device and load it, and obtain a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device; a second module, which is used to configure a shared memory and a message queue associated with the PCIe device, the message queue is used to trigger an interrupt with the in-band system during the runtime stage, and the shared memory is used to interact with the in-band system during the runtime stage; a third module, which is used to read and store the log data written by the in-band system stored in the shared memory according to the interrupt triggering state of the message queue.

[0060] In one embodiment, the log data written by the in-band system stored in the shared memory is read and stored according to the interrupt trigger status of the message queue, including: reading the log data written by the in-band system stored in the shared memory according to the interrupt trigger status of the message queue, and storing the data according to different associated third-party application categories, wherein the log data written by the in-band system includes log data written by the in-band system to corresponding specific locations of the shared memory according to different third-party applications.

[0061] In one embodiment, the in-band system writes log data to corresponding specific locations of the shared memory according to different third-party applications, including log data that the in-band system writes to corresponding specific locations of the shared memory according to different third-party applications and occupies a preset fixed size storage space.

[0062] In one implementation, the step of constructing and loading a virtual PCIe device, and obtaining a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device, includes: enabling a BMC Device function, and loading the device in the role of a PCIe device.

[0063] The device implementation is the same as or similar to the corresponding method implementation, and will not be described in detail here.

[0064] In one embodiment, this specification provides an electronic device, including a processor and a readable storage medium, wherein the readable storage medium stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the aforementioned log management method. From a hardware level, the hardware architecture diagram can be seen in Figure 3 shown.

[0065] In one embodiment, the present specification provides a readable storage medium, wherein the readable storage medium stores machine executable instructions, and when the machine executable instructions are called and executed by a processor, the machine executable instructions prompt the processor to implement the aforementioned log management method.

[0066] Here, the readable storage medium can be any electronic, magnetic, optical or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, the readable storage medium can be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as hard disk drive), solid state drive, any type of storage disk (such as CD, DVD, etc.), or similar storage medium, or a combination thereof.

[0067] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0068] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0069] It will be appreciated by those skilled in the art that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, this specification may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0070] This specification is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0071] Moreover, these computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0072] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0073] It will be appreciated by those skilled in the art that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, this specification may be in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may be in the form of a computer program product implemented on one or more computer-usable storage media (which may include but are not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0074] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A log management method, characterized in that: Applied to a BMC device, the method includes: Constructing a virtual PCIe device and loading it, obtaining a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device; Configure a shared memory and a message queue associated with the PCIe device, wherein the message queue is used for interrupt triggering with the in-band system during the runtime phase, and the shared memory is used for data interaction with the in-band system during the runtime phase; According to the interrupt trigger status of the message queue, the log data written by the in-band system stored in the shared memory is read and stored.

2. The method according to claim 1, characterized in that The method of reading and storing the log data written by the in-band system stored in the shared memory according to the interrupt trigger state of the message queue includes: According to the interrupt trigger status of the message queue, the log data written by the in-band system stored in the shared memory is read, and stored according to the classification of different associated third-party applications. The log data written by the in-band system includes the log data written by the in-band system to the corresponding specific location of the shared memory according to different third-party applications.

3. The method according to claim 2, characterized in that The log data written by the in-band system to the corresponding specific position of the shared memory according to different third-party applications includes log data written by the in-band system to the corresponding specific position of the shared memory according to different third-party applications and occupying a preset fixed size storage space.

4. The method according to claim 1, characterized in that: The step of constructing a virtual PCIe device and loading it, and obtaining a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device, includes: Enable the BMC Device function and load it as a PCIe device.

5. A log management device, characterized in that: Applied to BMC equipment, the device comprises: The first module is used to construct and load a virtual PCIe device, and obtain a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device; The second module is used to configure a shared memory and a message queue associated with the PCIe device, wherein the message queue is used for interrupt triggering with the in-band system at the runtime stage, and the shared memory is used for data interaction with the in-band system at the runtime stage; The third module is used to read and store the log data written by the in-band system stored in the shared memory according to the interrupt trigger status of the message queue.

6. The device according to claim 5, characterized in that The method of reading and storing the log data written by the in-band system stored in the shared memory according to the interrupt trigger state of the message queue includes: According to the interrupt trigger status of the message queue, the log data written by the in-band system stored in the shared memory is read, and stored according to the classification of different associated third-party applications. The log data written by the in-band system includes the log data written by the in-band system to the corresponding specific location of the shared memory according to different third-party applications.

7. The device according to claim 6, characterized in that The log data written by the in-band system to the corresponding specific position of the shared memory according to different third-party applications includes log data written by the in-band system to the corresponding specific position of the shared memory according to different third-party applications and occupying a preset fixed size storage space.

8. The device according to claim 5, characterized in that The step of constructing a virtual PCIe device and loading it, and obtaining a device identifier and a manufacturer identifier so that the in-band system can identify the virtual PCIe device, includes: Enable the BMC Device function and load it as a PCIe device.

9. An electronic device, characterized in that: include: A processor and a readable storage medium, wherein the readable storage medium stores machine executable instructions that can be executed by the processor, and the processor executes the machine executable instructions to implement the method described in any one of claims 1 to 4.

10. A readable storage medium, characterized in that: The readable storage medium stores machine executable instructions, and when the machine executable instructions are called and executed by a processor, the machine executable instructions prompt the processor to implement any one of the methods of claims 1-4.

Images