Hot plug control method and device of external equipment, storage medium and electronic equipment
By detecting the hot-swap signals on the expansion slot in the operating system and finding the identification of the target driver, the problem of low hot-swap control efficiency of external devices is solved, and efficient control and troubleshooting of external devices is achieved.
Patent Information
- Application Number
- CN202411132394.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-12-06
AI Technical Summary
In the prior art, the hot-swap control efficiency of external devices is low, and changes in external devices cannot be sensed in time, resulting in hardware failure or ineffective handling during plug-in and unplug-and-removal operations.
By detecting hot-swap signals on the expansion slot in the operating system, finding the driver identification of the target driver, and transmitting the signal to the target driver for processing, or masking the signal to improve control efficiency.
Improve the hot-swap control efficiency of external devices, ensure that the system can timely sense and handle the plug-and-remove changes of external devices, and avoid system crashes or restarts caused by improper hot-swap.
Smart Images

Figure CN119088742A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of computers, and in particular, to a method, device, storage medium and electronic device for hot plugging control of an external device. Background Art
[0002] At present, general operating systems are provided with an enable configuration for hot plugging, and the hot plug response processing of external devices is turned on and off through the enable configuration. However, this method is for all external devices connected to the expansion slots, that is, the hot plug signals of external devices that support hot plugging or do not support hot plugging will be shielded. However, after the above method shields the hot plug signals of external devices, when the shielded external device has a hardware failure or is plugged in and out, because the hot plug signal is shielded, the changes of the shielded external device cannot be perceived in time.
[0003] In view of the problems in the related art such as low hot-swap control efficiency of external devices, no effective solution has been proposed yet. Summary of the invention
[0004] The embodiments of the present application provide a method, apparatus, storage medium and electronic device for hot plugging control of an external device, so as to at least solve the problem of low efficiency of hot plugging control of external devices in the related art.
[0005] According to an embodiment of the present application, a hot-swap control method for an external device is provided, which is applied to an operating system running on a mainboard device, wherein an expansion slot is deployed on the mainboard device, and the operating system drives an external device connected to the expansion slot through a driver program, and a reference driver identifier of a reference driver program supporting hot-swap of an external device is stored in the mainboard device, and the method includes:
[0006] Detecting a hot plug signal generated on the expansion slot, wherein the hot plug signal is used to indicate that a hot plug of an external device has occurred on the expansion slot;
[0007] In the case where a target hot plug signal is detected on the expansion slot, detecting a target driver identifier of a target driver corresponding to a target external device generating the target hot plug signal;
[0008] Searching for the target drive identifier from the reference drive identifier;
[0009] In the case where the target drive identifier is found from the reference drive identifier, the target hot plug signal is transmitted to the target driver program, wherein the target driver program is used to perform hot plug processing on the target external device in response to the target hot plug signal; in the case where the target drive identifier is not found from the reference drive identifier, the target hot plug signal is shielded from the target driver program.
[0010] In an exemplary embodiment, the detection of the target driver identification of the target driver corresponding to the target external device that generates the target hot plug signal includes: identifying the target external device that generates the target hot plug signal on the expansion slot; detecting whether there is a driver that allows driving the target external device among the drivers installed on the operating system; in the case of detecting that there is a driver that allows driving the target external device among the drivers installed on the operating system, determining the driver that allows driving the target external device as the target driver; and obtaining the target driver identification of the target driver.
[0011] In an exemplary embodiment, a kernel hot-plug driver and a kernel driver are installed in the operating system, a hot-plug interrupt processing function is registered in the kernel hot-plug driver, and the kernel driver is used to manage the reference driver identifier; searching for the target driver identifier from the reference driver identifier includes: running the kernel hot-plug driver, calling the hot-plug interrupt processing function through the kernel hot-plug driver; querying the kernel driver for the target driver identifier through the hot-plug interrupt processing function; receiving the query result of the target driver identifier returned by the kernel driver through the hot-plug interrupt processing function, wherein the query result is used to indicate whether the target driver identifier is found from the reference driver identifier.
[0012] In an exemplary embodiment, a signal monitoring program is also installed in the operating system; the detecting of the hot plug signal generated on the expansion slot includes: running the signal monitoring program when the operating system has been started; detecting the hot plug signal generated on the expansion slot through the signal monitoring program; the detecting of the target driver identifier of the target driver corresponding to the target external device that generates the target hot plug signal includes: triggering a hot plug interrupt to the kernel hot plug driver when the signal monitoring program detects that the target hot plug signal is generated on the expansion slot; the kernel hot plug driver calls the hot plug interrupt processing function when detecting that the hot plug interrupt is triggered; and detecting the target driver identifier of the target driver corresponding to the target external device through the hot plug interrupt processing function.
[0013] In an exemplary embodiment, the operating system is divided into a user layer and a kernel layer, the user layer is configured to allow a user to configure the reference driver identifier, a kernel driver is installed in the kernel layer, and the operating system runs a system file system in the kernel layer; before searching for the target driver identifier from the reference driver identifier, the method also includes: transferring the reference driver identifier configured on the user layer from the user layer to the kernel driver of the kernel layer; writing the reference driver identifier into the system file system through the kernel driver to obtain a target system file recording the reference driver identifier.
[0014] In an exemplary embodiment, the kernel driver that transfers the reference driver identifier configured on the user layer from the user layer to the kernel layer includes: during the boot process of the operating system, obtaining a first configuration file created by the user at the user layer from the user layer through the boot system of the operating system, wherein the reference driver identifier is recorded in the first configuration file; transmitting the reference driver identifier recorded in the first configuration file to the kernel driver through the boot system; writing the reference driver identifier into the system file system through the kernel driver to obtain a target system file recording the reference driver identifier, includes: receiving the reference driver identifier transmitted by the boot system through the kernel driver; creating an initial system file in the system file system through the kernel driver; writing the reference driver identifier into the initial system file in the form of a linked list through the kernel driver to obtain the target system file.
[0015] In an exemplary embodiment, when it is detected that the target hot plug signal is generated on the expansion slot, the method also includes: extracting target device information from the target hot plug signal, wherein the target device information is the device information of the target external device that generates the target hot plug signal; matching target slot information from a second configuration file based on the target device information, wherein the second configuration file records the device information of the external device connected to each expansion slot, and the target slot information is the slot information of the target expansion slot to which the target external device is connected; generating alarm information based on the target device information and the target slot information, and pushing the alarm information to the client.
[0016] According to another embodiment of the present application, a hot-swap control device for an external device is provided, which is applied to an operating system running on a mainboard device, wherein an expansion slot is deployed on the mainboard device, and the operating system drives the external device connected to the expansion slot through a driver program, and the mainboard device stores a reference driver identifier of a reference driver program that supports hot-swap of the external device, and the device includes:
[0017] A first detection module, used for detecting a hot plug signal generated on the expansion slot, wherein the hot plug signal is used for indicating that a hot plug of an external device has occurred on the expansion slot;
[0018] A second detection module is used to detect a target driver identifier of a target driver corresponding to a target external device generating the target hot plug signal when a target hot plug signal is detected on the expansion slot;
[0019] A search module, used for searching the target drive identifier from the reference drive identifier;
[0020] a transmission module, configured to transmit the target hot-plug signal to the target driver program when the target driver identifier is found from the reference driver identifier, wherein the target driver program is configured to perform hot-plug processing on the target external device in response to the target hot-plug signal;
[0021] The shielding module is used to shield the target hot plug signal to the target driver program when the target driver identifier is not found in the reference driver identifier.
[0022] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when run.
[0023] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
[0024] According to another embodiment of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.
[0025] Through the present application, a hot plug signal generated on an expansion slot is detected, wherein the hot plug signal is used to indicate that a hot plug of an external device has occurred on the expansion slot; when a target hot plug signal is detected on the expansion slot, a target driver identifier of a target driver corresponding to the target external device generating the target hot plug signal is detected; the target driver identifier is searched from a reference driver identifier; when the target driver identifier is found from the reference driver identifier, the target hot plug signal is transmitted to the target driver, wherein the target driver is used to perform hot plug processing on the target external device in response to the target hot plug signal; when the target driver identifier is not found from the reference driver identifier, the target hot plug signal is shielded from the target driver. That is, whether to use the target driver to respond to the target hot plug signal is determined according to the target driver identifier of the target driver corresponding to the target external device generating the target hot plug signal, and for a target external device that does not support hot plug processing, the target hot plug signal is shielded from the target driver, thereby solving the problem of low hot plug control efficiency of the external device and achieving the effect of improving the hot plug control efficiency of the external device. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 The hardware structure frame of the server device of the hot plug control method of an external device in the embodiment of the present application is Figure 2
[0027] Figure 2 This is a process of a hot-swap control method for an external device according to an embodiment of the present application;
[0028] Figure 3 is a schematic diagram of a first configuration file according to an embodiment of the present application;
[0029] Figure 4 is a schematic diagram of a driver of an operating system according to an embodiment of the present application;
[0030] Figure 5 is a schematic diagram of a second configuration file according to an embodiment of the present application;
[0031] Figure 6 It is a flow chart of calling a hot-plug interrupt processing function to process hot-plug according to an embodiment of the present application;
[0032] Figure 7 is a flowchart of a working process of an operating system according to an embodiment of the present application;
[0033] Figure 8 is a structural block diagram of a hot-swap control device for an external device according to an embodiment of the present application;
[0034] Fig. 9It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0035] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0036] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0037] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 FIG. 1 is a hardware structure block diagram of a server device of a hot-swap control method for an external device according to an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the server device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.
[0038] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the hot plug control method of the external device in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the server device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0039] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.
[0040] In this embodiment, a hot-plug control method for an external device is provided, which is applied to an operating system running on a mainboard device, wherein an expansion slot is deployed on the mainboard device, and the operating system drives an external device connected to the expansion slot through a driver program, wherein a reference driver identifier of a reference driver program supporting hot-plugging of an external device is stored in the mainboard device. Figure 2 is a flow chart of a hot-swap control method for an external device according to an embodiment of the present application. Figure 2 As shown, the process includes the following steps:
[0041] Step S202, detecting a hot plug signal generated on the expansion slot, wherein the hot plug signal is used to indicate that a hot plug of an external device has occurred on the expansion slot;
[0042] Step S204, when it is detected that a target hot plug signal is generated on the expansion slot, detecting a target driver identifier of a target driver corresponding to a target external device that generates the target hot plug signal;
[0043] Step S206, searching the target drive identifier from the reference drive identifier;
[0044] Step S208, when the target drive identifier is found from the reference drive identifier, the target hot plug signal is transmitted to the target driver program, wherein the target driver program is used to perform hot plug processing on the target external device in response to the target hot plug signal; when the target drive identifier is not found from the reference drive identifier, the target hot plug signal is shielded from the target driver program.
[0045] Through the above steps, the hot plug signal generated on the expansion slot is detected, wherein the hot plug signal is used to indicate that the hot plug of the external device has occurred on the expansion slot; when the target hot plug signal is detected on the expansion slot, the target driver identifier of the target driver corresponding to the target external device generating the target hot plug signal is detected; the target driver identifier is searched from the reference driver identifier; when the target driver identifier is found from the reference driver identifier, the target hot plug signal is transmitted to the target driver, wherein the target driver is used to perform hot plug processing on the target external device in response to the target hot plug signal; when the target driver identifier is not found from the reference driver identifier, the target hot plug signal is shielded from the target driver. That is to say, according to the target driver identifier of the target driver corresponding to the target external device generating the target hot plug signal, it is determined whether to use the target driver to respond to the target hot plug signal, and for the target external device that does not support hot plug processing, the target driver is shielded from the target hot plug signal, so that the problem of low hot plug control efficiency of the external device can be solved, and the effect of improving the hot plug control efficiency of the external device is achieved.
[0046] Optionally, in this embodiment, the external device connected to the expansion slot can communicate with the mainboard device through but not limited to PCIE (Peripheral Component Interconnect Express, a high-speed serial computer expansion bus). In the following embodiments, the hot-swap control method of the above-mentioned external device can be described by taking the PCI E device as an external device as an example but not limited to, but is not limited to the specific external device. Any external device that is allowed to be connected to the expansion slot and hot-swapped can use the hot-swap control method of the external device proposed in this application.
[0047] Optionally, in this embodiment, in order to clearly illustrate the application scenario of the hot-plug control method of the external device proposed in this application, the hot-plug of the PCI E device is introduced as follows: PCI E devices are widely used in computing storage devices as a general-purpose device. Some application scenarios require that PCIe devices can continue to operate uninterruptedly with high reliability. For this reason, the PCIe bus uses hot plug (Hot Plug) and hot swap (Hot Swap) to achieve the replacement of PCIe devices without turning off the system power. Due to the different functional designs of different PCIe devices and motherboard devices, not all PCIe devices can support hot plugging. For PCIe devices that cannot support hot plugging, if the hot plugging process is executed incorrectly and cannot be effectively exited, it may bring some adverse consequences, such as: system restart, downtime, etc.
[0048] In order to solve the above problems, the hot-plug function of PCle devices that do not support hot-plugging is shielded to reduce system crashes or restarts caused by improper hot-plugging. Due to the existence of the reference driver identifier, it is allowed to connect PCle devices that support hot-plugging on the same expansion slot, and it is also allowed to connect PCle devices that do not support hot-plugging on the expansion slot. It is only necessary to determine whether the PCle device that is currently hot-plugged supports hot-plugging based on the target driver corresponding to the target external device of the target hot-plugging signal, and it is possible to dynamically modify which devices need to shield hot-plugging through the configuration file, providing an effective method to manage the hot-plugging operation of PCle devices, aiming to improve the stability, security and maintainability of the system.
[0049] In the technical solution provided in the above step S202, the hot plug signal from the kernel can be monitored through, but not limited to, a device description mechanism provided by the operating system kernel, such as: udev (Unified Device Description, a device description mechanism provided by the Linux kernel), mdev, devd, etc.
[0050] Optionally, in this embodiment, hot plugging of the external device may include but is not limited to: inserting the external device into the expansion slot, unplugging the external device from the expansion slot, etc.
[0051] Optionally, in this embodiment, taking the use of udev to monitor the hot-plug signal from the kernel as an example, when a PCle device is physically inserted into or unplugged from a PCle slot on the motherboard, the hardware detects the change; the hardware notifies the kernel of a device status change through an interrupt signal; the kernel recognizes the hot-plug event and may, but is not limited to, generate an event through the proc file system or other mechanisms of the kernel to indicate that the device has been inserted or unplugged; udev monitors these kernel events, and when it detects that the current kernel event is a hot-plug event for a PCIe device, udev converts the event into a hot-plug signal and sends it to user space, which may, but is not limited to, appear in the form of a device node change in the / dev directory.
[0052] In the technical solution provided in the above step S204, the PCle device and the driver are basic components of the hardware and software interaction in the operating system. When the PCle device is inserted into the PCle slot of the motherboard, the operating system can, but is not limited to, identify the hardware device through the driver. The driver can, but is not limited to, provide an interface for the operating system to communicate with the PCle device, allowing the system to call the functions of the device.
[0053] Optionally, in this embodiment, the target driver identifier of the target driver program corresponding to the target external device generating the target hot plug signal can be extracted from the target hot plug signal but is not limited to it. Alternatively, other information carried in the target hot plug signal can be identified and the target driver identifier of the target driver program corresponding to the target external device generating the target hot plug signal can be detected based on the identified other information.
[0054] Optionally, in this embodiment, the driver name, vendor ID (identity document), device ID, driver version, etc. of the driver may be used as the driver identification of the driver but is not limited to it.
[0055] In an exemplary embodiment, the target driver identifier of the target driver corresponding to the target external device that generates the target hot plug signal can be detected in the following manner but is not limited to: identifying the target external device that generates the target hot plug signal on the expansion slot; detecting whether there is a driver that allows driving the target external device among the drivers installed on the operating system; in the case of detecting that there is a driver that allows driving the target external device among the drivers installed on the operating system, determining the driver that allows driving the target external device as the target driver; and obtaining the target driver identifier of the target driver.
[0056] Optionally, in this embodiment, the driver program may exist in the operating system in the form of a kernel module, but is not limited to. When a PCIe device is inserted into the PCIe slot of the motherboard, the kernel of the operating system may detect, but is not limited to, hardware changes in the PCIe slot through the PCIe controller and BIOS / UEF. The kernel identifies the vendor ID and device ID of the PCIe device, and searches for a matching driver program based on the identified vendor ID and device ID. If a corresponding driver program is found, the hardware device is driven by the driver program. However, if no corresponding driver program is found, it is considered that the system does not support the current PCI E device.
[0057] Optionally, in this embodiment, when a target hot-plug signal is detected on the expansion slot, it is possible but not limited to traversing to find whether the PCle device that has been hot-plugged has a driver loaded. If the driver is loaded on the PCle device that has been hot-plugged, the target driver identifier of the target driver is obtained; if the driver is not loaded on the PCle device that has been hot-plugged, it is considered that the current PCle device hot-plugging will not affect subsequent processing.
[0058] In the technical solution provided in the above step S206, the reference driver identifier is a driver identifier corresponding to a reference driver program that supports hot plugging of external devices, which can be, but is not limited to, written into the operating system during the startup of the mainboard device.
[0059] In an exemplary embodiment, a kernel hot-plug driver and a kernel driver are installed in the operating system, a hot-plug interrupt processing function is registered in the kernel hot-plug driver, and the kernel driver is used to manage the reference driver identifier; the target driver identifier can be searched from the reference driver identifier in the following manner but is not limited to: running the kernel hot-plug driver and calling the hot-plug interrupt processing function through the kernel hot-plug driver; querying the kernel driver for the target driver identifier through the hot-plug interrupt processing function; receiving the query result of the target driver identifier returned by the kernel driver through the hot-plug interrupt processing function, wherein the query result is used to indicate whether the target driver identifier is found from the reference driver identifier.
[0060] Optionally, in this embodiment, it is possible but not limited to that during the server startup process, the operating system starts the hot plug udev signal monitoring program as the kernel hot plug driver and registers the hot plug interrupt processing function. When the hot plug udev signal monitoring program detects that a target hot plug signal is generated on the expansion slot, the hot plug interrupt processing function is called.
[0061] Optionally, in this embodiment, when the user hot plugs in or unplugs a PCle device, a hot plug interrupt is triggered, and the kernel hot plug driver calls the hot plug interrupt processing function to handle the hot plug, which may include but is not limited to: traversing to find whether the driver is loaded for the PCle device that has been hot plugged; for the PCle device that has been loaded with the driver, querying from the kernel driver whether the PCle device that has been hot plugged supports hot plugging.
[0062] Optionally, in this embodiment, the kernel driver may be, but is not limited to, a newly added one in this application, for receiving driver information of a PCle device supporting hot-plugging transmitted from user mode, i.e., a reference driver identifier. The kernel driver provides an interface for the kernel hot-plug driver of the kernel layer to interact with the application program of the user space, allowing the system to dynamically identify and configure PCle devices supporting hot-plugging at runtime without restarting or recompiling the kernel. By transmitting information to the kernel through the user space, the list of devices supporting hot-plugging can be flexibly updated and maintained to adapt to different usage scenarios and requirements.
[0063] In an exemplary embodiment, a signal monitoring program is also installed in the operating system; the hot plug signal generated on the expansion slot can be detected in the following manner but not limited to: when the operating system has been started, the signal monitoring program is run; the hot plug signal generated on the expansion slot is detected by the signal monitoring program; the target driver identifier of the target driver program corresponding to the target external device that generates the target hot plug signal can be detected in the following manner but not limited to: when the signal monitoring program detects that the target hot plug signal is generated on the expansion slot, a hot plug interrupt is triggered to the kernel hot plug driver program; when the kernel hot plug driver program detects that the hot plug interrupt is triggered, the hot plug interrupt processing function is called; and the target driver identifier of the target driver program corresponding to the target external device is detected by the hot plug interrupt processing function.
[0064] Optionally, in this embodiment, it is possible but not limited to that during the server startup process, the operating system runs a signal monitoring program, and detects the hot plug signal generated on the expansion slot through the signal monitoring program; when the signal monitoring program detects that a target hot plug signal is generated on the expansion slot, the hot plug interrupt is triggered to the kernel hot plug driver; when the kernel hot plug driver detects that the hot plug interrupt is triggered, the hot plug interrupt processing function is called; and the target driver identifier of the target driver corresponding to the target external device is detected through the hot plug interrupt processing function.
[0065] In an exemplary embodiment, the operating system is divided into a user layer and a kernel layer, the user layer is configured to allow a user to configure the reference driver identifier, a kernel driver is installed in the kernel layer, and the operating system runs a system file system in the kernel layer; before searching for the target driver identifier from the reference driver identifier, the following method may be used but is not limited to: transferring the reference driver identifier configured on the user layer from the user layer to the kernel driver of the kernel layer; writing the reference driver identifier into the system file system through the kernel driver to obtain a target system file recording the reference driver identifier.
[0066] Optionally, in this embodiment, the kernel driver can receive the PCle device driver information supporting hot plugging transmitted from the user state, i.e., the reference driver identification, through the sysfs mechanism, but is not limited thereto, and saves the information in the form of a linked list as a target system file. Alternatively, the PCle device driver information supporting hot plugging transmitted from the user state can also be received in other ways.
[0067] In an exemplary embodiment, the reference driver identifier configured on the user layer may be transferred from the user layer to the kernel driver of the kernel layer in the following manner, but is not limited to: during the boot process of the operating system, a first configuration file created by the user at the user layer is obtained from the user layer through the boot system of the operating system, wherein the reference driver identifier is recorded in the first configuration file; the reference driver identifier recorded in the first configuration file is transferred to the kernel driver through the boot system; the reference driver identifier is written into the system file system through the kernel driver, so as to obtain a target system file recording the reference driver identifier, but is not limited to: the reference driver identifier transmitted by the boot system is received through the kernel driver; an initial system file is created in the system file system through the kernel driver; the reference driver identifier is written into the initial system file in the form of a linked list through the kernel driver, so as to obtain the target system file.
[0068] Optionally, in this embodiment, it is possible but not limited to that during the server startup process, the operating system runs a startup script, parses the first configuration file, and writes a reference driver identifier that supports hot plugging into a sysfs file created by the kernel driver in the system file system, and the kernel driver obtains a target system file that records the reference driver identifier that supports hot plugging.
[0069] Optionally, in this embodiment, the initial system file can be but is not limited to creating a sysfs file in sysfs, and the kernel driver can be but is not limited to receiving the PCle device driver information supporting hot plugging transmitted from the user state through the sysfs mechanism as a reference driver identifier, and saving the information in the form of a linked list to obtain the target system file.
[0070] In an exemplary embodiment, an example of a first configuration file is provided. Figure 3 is a schematic diagram of a first configuration file according to an embodiment of the present application, such as Figure 3 As shown, the first configuration file distinguishes which PCle devices support hot plugging and which PCle devices do not support hot plugging through the reference driver identifier. The first configuration file records the reference driver identifiers of all PCle devices that support hot plugging. The first configuration file can, but is not limited to, record reference driver identifiers 1 to reference driver identifiers N in the format "PCle_SUPPORT_HOTPLUG_DRIVER N=xx", wherein PCle_SUPPORT_HOTPLUG_DRIVER N indicates that this is the Nth entry of the PCle device driver that supports hot plugging in the first configuration file, N is an index, and more entries can be added as needed, and "XX" is the reference driver identifier of the PCle device.
[0071] In an exemplary embodiment, an example of a driver for an operating system is provided. Figure 4 is a schematic diagram of a driver of an operating system according to an embodiment of the present application, such as Figure 4 As shown, a new driver 1 is added as the above kernel driver. Driver 1 receives the PCle device driver information supporting hot plugging transmitted by the user state through the sysfs mechanism, and saves the information in the form of a linked list to / sys / devices / virtual / misc / plpciehp / support_hotplug_drivers. The user state notifies the driver to update the above linked list by adding, deleting, checking, and modifying the file.
[0072] Taking the operating system also including driver 2 as the kernel hot-plug driver as an example, when a target hot-plug signal is detected on the expansion slot, driver 2 calls the hot-plug interrupt processing function to query driver 1 for the target driver identifier, and receives the query result of the target driver identifier returned by driver 1 through the hot-plug interrupt processing function.
[0073] In an exemplary embodiment, when it is detected that the target hot plug signal is generated on the expansion slot, the following method can be used but is not limited to: extracting target device information from the target hot plug signal, wherein the target device information is the device information of the target external device that generates the target hot plug signal; matching target slot information from a second configuration file based on the target device information, wherein the second configuration file records the device information of the external device connected to each expansion slot, and the target slot information is the slot information of the target expansion slot to which the target external device is connected; generating alarm information based on the target device information and the target slot information, and pushing the alarm information to the client.
[0074] Optionally, in this embodiment, the target hot plug signal may be sent in the following format, but is not limited to:
[0075] device: / / is used to indicate the device type, for example: 'driver', 'char device', 'block device', etc.
[0076] action: / / is used to indicate the type of operation, such as 'add', 'remove', 'change', etc.
[0077] device_name: / / used to indicate the name of the device;
[0078] device_id: / / Used to indicate the unique identifier of the device, which can be the MAC address of the device, device node, etc.;
[0079] attributes: / / Used to indicate the attributes of the device, including the attributes of the device driver, such as: 'substring', 'error', etc.;
[0080] data: / / is used to indicate the data of the message, which can be the status of the device, configuration information, etc.
[0081] Optionally, in this embodiment, each field in the target hot plug signal can be used as target device information but is not limited to it, and the device information of the PCle device where the plugging and unplugging occurs can be determined based on the above fields in the target hot plug signal, thereby achieving that whether a hot plug event occurs in the PCle device can be monitored regardless of whether the PCle device supports hot plugging.
[0082] Optionally, in this embodiment, the second configuration file records the device information of the external device connected to each expansion slot, and the device information recorded in the second configuration file is matched with the target device information in the target hot plug signal to determine the slot information of the target expansion slot to which the target external device that has been hot plugged is connected. In other words, the second configuration file is matched with the target device information to determine which expansion slot has hardware changed.
[0083] Optionally, in this embodiment, the alarm information can be pushed to the user for processing through but not limited to alarms, emails, etc., for example: if it is an unexpected alarm, that is, the user does not actively plug or unplug the PCle device, it means that the PCle device has failed and the system cannot recognize it. The user of the PCle device that supports hot plugging can replace it without shutting down the machine, otherwise it needs to shut down the machine for replacement to avoid affecting the business; if the user actively plugs or unplugs the PCle device, the hardware configuration file in 4 is updated to the current configuration.
[0084] In an exemplary embodiment, an example of a second configuration file is provided. Figure 5 is a schematic diagram of a second configuration file according to an embodiment of the present application, such as Figure 5 As shown, the slot information of each expansion slot and the device information connected to each expansion slot are recorded through the second configuration file. Taking the Mth expansion slot in the second configuration file as an example, the second configuration file can be but not limited to recording the device information on the Mth expansion slot in the following format:
[0085] SLOT M_BDF = xxx; / / The unique identifier of the PCle device in the system, which may include but is not limited to the bus number (Bus), device number (Device) and function number (Function), is used to accurately determine the position of the device on the PCle bus. For example, SLOT1_BDF = 0000:01:00.0 means that the device is located on the 0th bus, the 1st device, and the 0th function;
[0086] SLOT M_HARDWARE_TYPE = xxx; / / used to indicate the type or category of hardware, or the functional description of the device;
[0087] SLOT M_HARDWARE_VENDOR_ID = xx; / / Vendor ID;
[0088] SLOT M_HARDWARE_DEVICE_ID = xx; / / Device ID, used in pair with the vendor ID to identify the specific device model;
[0089] SLOT M_HARDWARE_SUBVENDOR_ID = xx; / / Subvendor ID, used to identify the seller or secondary manufacturer of the device;
[0090] SLOT M_HARDWARE_SUBDEVICE_ID = xx; / / Subdevice ID, often used with subvendor ID to identify a specific device variant or customized version.
[0091] In the technical solution provided in the above step S208, Figure 6 is a flow chart of calling a hot plug interrupt processing function to process hot plug according to an embodiment of the present application, such as Figure 6 As shown, when the user hot-plugs or unplugs a PCle device, a hot-plug interrupt is triggered, and the kernel hot-plug driver can, but is not limited to, call the hot-plug interrupt processing function to handle hot-plugging through the following steps:
[0092] Step S602: traverse and search whether the hot-plugged PCIe device has a driver loaded. If the system does not support the hot-plugged PCIe device, the corresponding driver will not be prepared, and the hot-plugging of the PCIe device will not affect subsequent processing;
[0093] Step S604: for the PCle device with the driver loaded, query from the kernel driver whether the PCle device that has been hot-plugged supports hot-plugging;
[0094] Step S606: If hot plugging is supported, the driver of the PCle device is notified to handle plugging, loading or removing the device;
[0095] Step S608: If hot plugging is not supported, the hot plugging signal is shielded, and the operating system maintains the loading or removal of the device;
[0096] Step S610: Regardless of whether the PCle device supports hot plugging and whether a driver is loaded, a hot plugging message is pushed to the user through the udev mechanism.
[0097] It should be noted that the hot-swap control method for external devices proposed in this application can be applied to various occasions where hot-swap shielding is required, such as servers, storage devices, etc. Servers and storage devices usually need to support hot-swap functions because they usually need to quickly expand or replace devices according to needs. The method proposed in this application can shield hot-swap for PCle devices that do not support hot-swap: in the same expansion slot, both hot-swap-supported PCle devices and non-hot-swap-supported PCle devices are allowed to be inserted, and which devices need to be shielded from hot-swap can be dynamically modified through the configuration file; for PCle devices that do not support hot-swap, since the perception of hot-swap by its driver is shielded, potential system restarts and downtime caused by plugging and unplugging are avoided. At the same time, regardless of whether the PICe device supports hot-swap, if the card is plugged and unplugged, the user can perceive it and can handle it in time to reduce the impact on the business.
[0098] Optionally, in this embodiment, in order to better understand the hot-plug control process of the above-mentioned external device in the hot-plug control method of the external device proposed in this application, the above-mentioned process is described in conjunction with an optional embodiment below, but it is not used to limit the technical solution of the embodiment of this application.
[0099] In an exemplary embodiment, an example of a working process of an operating system is provided. Figure 7 is a flowchart of a working process of an operating system according to an embodiment of the present application, such as Figure 7 As shown, the operating system can work through but is not limited to the following steps:
[0100] Step S702: During the server startup process, the BIOS (Basic Input Output System) is configured to enable hot plugging, the expansion slot is enabled with hot plugging function, and the operating system is also configured to enable hot plugging support for PCle devices;
[0101] Step S704: during the booting process of the operating system, the kernel driver receives the PCle device driver information supporting hot plugging (i.e., the first configuration file) transmitted from the user state through the sysfs mechanism, and writes the PCle device driver information supporting hot plugging into the system file system to obtain the target system file;
[0102] Step S706: Run the hot-plug udev signal monitoring program (i.e., signal monitoring program) to monitor the PCle device hot-plug signal from the kernel;
[0103] Step S708: When the PCle device is hot-plugged or unplugged, the hot-plug udev signal monitoring program triggers the hot-plug interrupt, and the kernel hot-plug driver calls the registered hot-plug interrupt processing function to handle the hot-plug;
[0104] Step S710: After the hot-plug udev signal monitoring program monitors the udev message, it parses the message to determine the information of the PCle device that is plugged in and out, and determines which expansion slot has hardware changed;
[0105] Step S712: Notify the user through alarm, email, etc. to handle the issue.
[0106] Through the hot-plug control method of external devices proposed in this application, a PCle device hot-plug shielding method is designed, a kernel driver and a configuration file for whether to support hot-plug are added, and the configuration file is parsed during the boot phase to notify the kernel of the PCle support for hot-plug information, so as to achieve the purpose of dynamically shielding hot-plug, and utilize the udev mechanism of the linu× system to monitor the udev hot-plug messages. Whether the PCle device supports hot-plug or not, the user can perceive it, thereby simplifying the system administrator's management of hardware changes.
[0107] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.
[0108] In this embodiment, a hot-swap control device for an external device is also provided, which is applied to an operating system running on a mainboard device, wherein an expansion slot is deployed on the mainboard device, wherein the operating system drives the external device connected to the expansion slot through a driver, and wherein the mainboard device stores a reference driver identifier of a reference driver that supports hot-swap of an external device. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and those that have been described will not be repeated here. As used below, the term "module" may be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, the implementation in hardware, or a combination of software and hardware, is also possible and conceivable.
[0109] Figure 8 is a structural block diagram of a hot-swap control device for an external device according to an embodiment of the present application, such as Figure 8 As shown, the device comprises:
[0110] A first detection module 82, configured to detect a hot plug signal generated on the expansion slot, wherein the hot plug signal is used to indicate that a hot plug of an external device has occurred on the expansion slot;
[0111] A second detection module 84 is used to detect a target driver identifier of a target driver corresponding to a target external device generating the target hot plug signal when a target hot plug signal is detected on the expansion slot;
[0112] A search module 86, configured to search the target drive identifier from the reference drive identifier;
[0113] The first processing module 88 is used to transmit the target hot-plug signal to the target driver program when the target driver identifier is found from the reference driver identifier, wherein the target driver program is used to perform hot-plug processing on the target external device in response to the target hot-plug signal; and shield the target hot-plug signal from the target driver program when the target driver identifier is not found from the reference driver identifier.
[0114] Through the above device, the hot plug signal generated on the expansion slot is detected, wherein the hot plug signal is used to indicate that the hot plug of the external device has occurred on the expansion slot; when the target hot plug signal is detected on the expansion slot, the target driver identifier of the target driver corresponding to the target external device generating the target hot plug signal is detected; the target driver identifier is searched from the reference driver identifier; when the target driver identifier is found from the reference driver identifier, the target hot plug signal is transmitted to the target driver, wherein the target driver is used to perform hot plug processing on the target external device in response to the target hot plug signal; when the target driver identifier is not found from the reference driver identifier, the target hot plug signal is shielded from the target driver. That is to say, according to the target driver identifier of the target driver corresponding to the target external device generating the target hot plug signal, it is determined whether to use the target driver to respond to the target hot plug signal, and for the target external device that does not support hot plug processing, the target driver is shielded from the target hot plug signal, so that the problem of low hot plug control efficiency of the external device can be solved, and the effect of improving the hot plug control efficiency of the external device is achieved.
[0115] In an exemplary embodiment, the second detection module includes:
[0116] An identification unit, used for identifying the target external device generating the target hot plug signal on the expansion slot;
[0117] A detection unit, used for detecting whether there is a driver program allowed to drive the target external device among the drivers installed on the operating system;
[0118] a determining unit, configured to determine the driver program that is allowed to drive the target external device as the target driver program when it is detected that there is a driver program that is allowed to drive the target external device among the drivers installed on the operating system;
[0119] The first acquisition unit is used to acquire the target driver identifier of the target driver program.
[0120] In an exemplary embodiment, a kernel hot-plug driver and a kernel driver are installed in the operating system, a hot-plug interrupt processing function is registered in the kernel hot-plug driver, and the kernel driver is used to manage the reference driver identifier; the search module includes:
[0121] An operating unit, configured to operate the kernel hot-plug driver and call the hot-plug interrupt processing function through the kernel hot-plug driver;
[0122] A query unit, configured to query the kernel driver for the target driver identifier through the hot plug interrupt processing function;
[0123] The first receiving unit is used to receive the query result of the target driver identifier returned by the kernel driver through the hot plug interrupt processing function, wherein the query result is used to indicate whether the target driver identifier is found from the reference driver identifier.
[0124] In an exemplary embodiment, a signal monitoring program is also installed in the operating system; the first detection module is also used to: run the signal monitoring program when the operating system has been started; detect the hot plug signal generated on the expansion slot through the signal monitoring program; the second detection module is also used to: trigger a hot plug interrupt to the kernel hot plug driver when the signal monitoring program detects that the target hot plug signal is generated on the expansion slot; the kernel hot plug driver calls the hot plug interrupt processing function when detecting that the hot plug interrupt is triggered; and detect the target driver identifier of the target driver corresponding to the target external device through the hot plug interrupt processing function.
[0125] In an exemplary embodiment, the operating system is divided into a user layer and a kernel layer, the user layer is configured to allow the user to configure the reference driver identifier, a kernel driver is installed in the kernel layer, and the operating system runs a system file system in the kernel layer; before searching for the target driver identifier from the reference driver identifier, the device further includes:
[0126] A transmission module, used for transmitting the reference driver identifier configured on the user layer from the user layer to the kernel driver of the kernel layer;
[0127] The writing module is used to write the reference driver identifier into the system file system through the kernel driver to obtain a target system file recording the reference driver identifier.
[0128] In an exemplary embodiment, the transmission module includes:
[0129] A second acquisition unit is configured to acquire, during the process of booting the operating system, from the user layer through the booting system of the operating system, a first configuration file created by the user in the user layer, wherein the reference driver identifier is recorded in the first configuration file;
[0130] A transmission unit, configured to transmit the reference driver identifier recorded in the first configuration file to the kernel driver through the boot system;
[0131] The writing module comprises:
[0132] A second receiving unit, configured to receive the reference driver identifier transmitted by the boot system through the kernel driver;
[0133] A creation unit, configured to create an initial system file in the system file system through the kernel driver;
[0134] The writing unit is used to write the reference driver identifier into the initial system file in the form of a linked list through the kernel driver to obtain the target system file.
[0135] In an exemplary embodiment, when it is detected that the target hot plug signal is generated on the expansion slot, the device further includes:
[0136] An extraction module, used for extracting target device information from the target hot-plug signal, wherein the target device information is device information of a target external device that generates the target hot-plug signal;
[0137] a matching module, configured to match target slot information from a second configuration file according to the target device information, wherein the second configuration file records device information of an external device connected to each expansion slot, and the target slot information is slot information of a target expansion slot to which the target external device is connected;
[0138] The second processing module is used to generate alarm information according to the target device information and the target slot information, and push the alarm information to the client.
[0139] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.
[0140] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
[0141] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.
[0142] An embodiment of the present application further provides an electronic device, Fig. 9 is a structural block diagram of an electronic device according to an embodiment of the present application, such as Fig. 9 As shown, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the method embodiments described above.
[0143] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.
[0144] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.
[0145] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.
[0146] The embodiments of the present application also provide a computer program, which includes computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps of any one of the above method embodiments.
[0147] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.
[0148] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.
[0149] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.
Claims
1. A hot-swap control method for an external device, It is characterized in that The method is applied to an operating system running on a mainboard device, wherein an expansion slot is deployed on the mainboard device, wherein the operating system drives an external device connected to the expansion slot through a driver, wherein a reference driver identifier of a reference driver supporting hot plugging of the external device is stored in the mainboard device, and the method comprises: Detecting a hot plug signal generated on the expansion slot, wherein the hot plug signal is used to indicate that a hot plug of an external device has occurred on the expansion slot; In the case where a target hot plug signal is detected on the expansion slot, detecting a target driver identifier of a target driver corresponding to a target external device generating the target hot plug signal; Searching for the target drive identifier from the reference drive identifier; In the case where the target drive identifier is found from the reference drive identifier, the target hot plug signal is transmitted to the target driver program, wherein the target driver program is used to perform hot plug processing on the target external device in response to the target hot plug signal; in the case where the target drive identifier is not found from the reference drive identifier, the target hot plug signal is shielded from the target driver program.
2. The method according to claim 1, It is characterized in that The detecting of the target driver identifier of the target driver corresponding to the target external device generating the target hot plug signal comprises: Identifying the target external device generating the target hot plug signal on the expansion slot; Detecting whether there is a driver program that allows driving the target external device among the drivers installed on the operating system; In the case where it is detected that there is a driver program that allows driving the target external device among the drivers installed on the operating system, determining the driver program that allows driving the target external device as the target driver program; The target driver identifier of the target driver is obtained.
3. The method according to claim 1, It is characterized in that A kernel hot-plug driver and a kernel driver are installed in the operating system, a hot-plug interrupt processing function is registered in the kernel hot-plug driver, and the kernel driver is used to manage the reference driver identifier; The searching the target drive identifier from the reference drive identifier comprises: Running the kernel hot-plug driver, and calling the hot-plug interrupt processing function through the kernel hot-plug driver; Querying the target driver identifier from the kernel driver through the hot-plug interrupt processing function; The query result of the target driver identifier returned by the kernel driver is received through the hot plug interrupt processing function, wherein the query result is used to indicate whether the target driver identifier is found from the reference driver identifier.
4. The method according to claim 3, It is characterized in that A signal monitoring program is also installed in the operating system; The detecting the hot plug signal generated on the expansion slot comprises: running the signal monitoring program when the operating system has been started; detecting the hot plug signal generated on the expansion slot by the signal monitoring program; The detecting of the target driver identifier of the target driver corresponding to the target external device that generates the target hot plug signal includes: triggering a hot plug interrupt to the kernel hot plug driver when the signal monitoring program detects that the target hot plug signal is generated on the expansion slot; the kernel hot plug driver calls the hot plug interrupt processing function when detecting that the hot plug interrupt is triggered; and detecting the target driver identifier of the target driver corresponding to the target external device through the hot plug interrupt processing function.
5. The method according to claim 1, It is characterized in that The operating system is divided into a user layer and a kernel layer, the user layer is configured to allow a user to configure the reference driver identifier, a kernel driver is installed in the kernel layer, and the operating system runs a system file system in the kernel layer; Before searching the target drive identifier from the reference drive identifier, the method further includes: Transmitting the reference driver identifier configured on the user layer from the user layer to the kernel driver of the kernel layer; The reference driver identifier is written into the system file system through the kernel driver to obtain a target system file recording the reference driver identifier.
6. The method according to claim 5, It is characterized in that The step of transmitting the reference driver identifier configured on the user layer from the user layer to the kernel driver of the kernel layer includes: During the booting process of the operating system, a first configuration file created by a user in the user layer is obtained from the user layer through the booting system of the operating system, wherein the reference drive identifier is recorded in the first configuration file; Transmitting the reference driver identifier recorded in the first configuration file to the kernel driver through the boot system; The step of writing the reference driver identifier into the system file system through the kernel driver to obtain a target system file recording the reference driver identifier includes: Receiving the reference driver identifier transmitted by the boot system through the kernel driver; Creating an initial system file in the system file system by the kernel driver; The reference driver identifier is written into the initial system file in the form of a linked list through the kernel driver to obtain the target system file.
7. The method according to claim 1, It is characterized in that In the case where it is detected that the target hot plug signal is generated on the expansion slot, the method further includes: Extracting target device information from the target hot-plug signal, wherein the target device information is device information of a target external device that generates the target hot-plug signal; Matching target slot information from a second configuration file according to the target device information, wherein the second configuration file records device information of an external device connected to each expansion slot, and the target slot information is slot information of a target expansion slot to which the target external device is connected; Alarm information is generated according to the target device information and the target slot information, and the alarm information is pushed to the client.
8. A hot-swap control device for an external device, It is characterized in that An operating system is applied to a mainboard device, wherein an expansion slot is deployed on the mainboard device, wherein the operating system drives an external device connected to the expansion slot through a driver, wherein a reference driver identifier of a reference driver supporting hot plugging of the external device is stored in the mainboard device, and the device comprises: A first detection module, used for detecting a hot plug signal generated on the expansion slot, wherein the hot plug signal is used for indicating that a hot plug of an external device has occurred on the expansion slot; A second detection module is used to detect a target driver identifier of a target driver corresponding to a target external device generating the target hot plug signal when a target hot plug signal is detected on the expansion slot; A search module, used for searching the target drive identifier from the reference drive identifier; a transmission module, configured to transmit the target hot-plug signal to the target driver program when the target driver identifier is found from the reference driver identifier, wherein the target driver program is configured to perform hot-plug processing on the target external device in response to the target hot-plug signal; The shielding module is used to shield the target hot plug signal to the target driver program when the target driver identifier is not found in the reference driver identifier.
9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, It is characterized in that When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.
Citation Information
Cited By
Network card equipment hot plug control method and device, electronic equipment and storage medium
CN120342794A
