SSD firmware simulation verification method, system, computer equipment and storage medium

By building an SSD firmware simulation system on the host side and using inter-process communication and host resources for simulation testing, the problems of low testing efficiency and insufficient code coverage in SSD firmware development are solved, and efficient SSD firmware quality assurance is achieved.

CN112395146BActive Publication Date: 2024-11-12SHENZHEN YILIAN INFORMATION SYST CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011356664.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-11-27
Publication Date
2024-11-12
Estimated Expiration
2040-11-27

AI Technical Summary

Technical Problem

During the development of SSD firmware, the existing technology requires a large number of physical SSDs for testing, resulting in high cost and low testing efficiency, and black box testing has problems with insufficient code coverage.

Method used

Build an SSD firmware simulation system on the host side, run the SSD firmware simulation process through inter-process communication, modify the SSD driver code on the host side, forward the commands transmitted by the bus to the SSD firmware simulation interface, and realize data transmission and operation. The simulation system includes front-end modules, Read and write buffer management module, mapping table management module and back-end module use the host's CPU/DRAM resources for high-speed simulation.

Benefits of technology

It greatly improves the testing efficiency and code coverage of SSD firmware, reduces testing costs, reduces quality risks, and achieves more efficient SSD quality assurance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112395146B_ABST
    Figure CN112395146B_ABST
Patent Text Reader

Abstract

The present application relates to an SSD firmware simulation verification method, system, computer equipment and storage medium, wherein the method includes: building an SSD firmware simulation system on the host side, and running the SSD firmware under the SSD firmware simulation system on the host side; running the SSD firmware simulation process on the host side to realize data transmission with the upper-level driver through inter-process communication; modifying the SSD driver code on the host side, and forwarding the bus transmission command to the SSD firmware simulation interface; the SSD firmware simulation system completes the corresponding operation according to the input command. The present invention changes the SSD to be tested from being connected via the bus to running on the host side, which can greatly improve the operating efficiency of the SSD firmware, and can fully test / verify its code coverage path, thereby improving the quality of the SSD.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of solid state drive testing technology, and in particular to an SSD firmware simulation verification method, system, computer equipment and storage medium. Background Art

[0002] As the price of solid-state drives falls, solid-state drives are becoming more and more popular. SSDs (solid-state drives) have been widely used in various occasions. Currently in the PC market, major computer manufacturers have made the hard drives in computer devices into SSDs to replace traditional HDDs, providing users with a better experience in terms of reliability and performance.

[0003] During the development phase, a large number of tests are required to verify the reliability of the SSD firmware code. Generally speaking, each SSD manufacturer will conduct system-level tests based on physical SSDs, which can well simulate the usage model of real customers. However, since the physical disk test requires the SSD to be worn out, it will result in a lot of cost overhead; at the same time, the access speed based on the bus will be limited, resulting in low test efficiency and insufficient logical coverage of the key code of the SSD. How to effectively improve the test coverage of the SSD firmware is a key factor in improving the quality of SSDs.

[0004] At present, in the existing SSD development process, in order to verify the firmware logic, the firmware needs to be compiled and burned to the SSD for operation. At the same time, the SSD is connected to the host through a connector, and the host generates a specific load through the script / OS to test the function and performance of the disk. In this way, in order to achieve coverage of the code path, more hosts / platforms need to be deployed, and due to the limited actual performance of the SSD, it takes a long time to complete a certain test coverage. Even so, because it is a black box test, there are many code blind spots that cannot be covered, and thus there are quality risks. Summary of the invention

[0005] Based on this, it is necessary to provide an SSD firmware simulation verification method, system, computer device and storage medium that can improve the test efficiency to improve the quality of the SSD in response to the above technical problems.

[0006] A SSD firmware simulation verification method, the method comprising:

[0007] Building an SSD firmware simulation system on the host side, and running the SSD firmware under the SSD firmware simulation system on the host side;

[0008] The host runs an SSD firmware simulation process to achieve data transmission with an upper-layer driver through inter-process communication;

[0009] Modify the SSD driver code on the host side to forward the bus transmission commands to the SSD firmware emulation interface;

[0010] The SSD firmware simulation system completes corresponding operations according to the input commands.

[0011] In one embodiment, the step of running the SSD firmware emulation process on the host side to implement data transmission with the upper driver through inter-process communication includes:

[0012] The front-end module of the SSD firmware simulation system performs interaction with upper-layer drive commands;

[0013] The read-write buffer management module of the SSD firmware simulation system is used to allocate and recycle the read-write buffer.

[0014] Execute mapping conversion of the logic address of the upper module to the virtual NAND address through the mapping table management module of the SSD firmware emulation system;

[0015] The read, write and erase operations of the virtual NAND are performed through the back-end module of the SSD firmware simulation system.

[0016] In one embodiment, the step of running the SSD firmware emulation process on the host side to implement data transmission with the upper driver through inter-process communication also includes:

[0017] Applying for space from the host's memory for use in the L2P mapping table and the read / write buffer;

[0018] An area is requested from the memory of the host side to simulate the DIE / Block / Page composition of NAND to store the user data of the upper layer driver.

[0019] In one embodiment, the method further comprises:

[0020] When the SSD firmware simulation process exits, the NAND Array data in the host memory is written to other hard disk entities of the host through the bus;

[0021] When the SSD firmware simulation process is restarted, after the host allocates the corresponding NAND Array Memory space, data is loaded from the hard disk file corresponding to the host and filled into the NAND Array in the memory.

[0022] A SSD firmware simulation verification system, the system comprising:

[0023] A building module, wherein the building module is used to build an SSD firmware simulation system on the host side, and run the SSD firmware under the SSD firmware simulation system on the host side;

[0024] A simulation module, wherein the simulation module is used to run an SSD firmware simulation process on the host side to implement data transmission with an upper-layer driver through inter-process communication;

[0025] A command transmission module, which is used to modify the SSD driver code on the host side and forward the bus-transmitted commands to the SSD firmware simulation interface;

[0026] A command execution module is used by the SSD firmware simulation system to complete corresponding operations according to input commands.

[0027] In one embodiment, the simulation module is specifically used for:

[0028] The front-end module of the SSD firmware simulation system performs interaction with upper-layer drive commands;

[0029] The read-write buffer management module of the SSD firmware simulation system is used to allocate and recycle the read-write buffer.

[0030] Execute mapping conversion of the logic address of the upper module to the virtual NAND address through the mapping table management module of the SSD firmware emulation system;

[0031] The read, write and erase operations of the virtual NAND are performed through the back-end module of the SSD firmware simulation system.

[0032] In one embodiment, the simulation module is further used for:

[0033] Applying for space from the host's memory for use in the L2P mapping table and the read / write buffer;

[0034] An area is requested from the memory of the host side to simulate the DIE / Block / Page composition of NAND to store the user data of the upper layer driver.

[0035] In one embodiment, the system further comprises:

[0036] A data storage module, wherein the data storage module is used to write the NAND Array data in the host memory to other hard disk entities of the host through the bus when the SSD firmware simulation process exits;

[0037] The data recovery module is used to load data from the hard disk file corresponding to the host and fill it into the NAND Array in the memory after the host allocates the corresponding NAND Array Memory space when the SSD firmware simulation process is restarted.

[0038] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any one of the above methods when executing the computer program.

[0039] A computer-readable storage medium stores a computer program, wherein the computer program implements the steps of any one of the above methods when executed by a processor.

[0040] The above-mentioned SSD firmware simulation verification method, system, computer device and storage medium build an SSD firmware simulation system on the host side, and run the SSD firmware under the SSD firmware simulation system on the host side; run the SSD firmware simulation process on the host side to realize data transmission with the upper-level driver through inter-process communication; modify the SSD driver code on the host side, and forward the bus transmission command to the SSD firmware simulation interface; the SSD firmware simulation system completes the corresponding operation according to the input command. The present invention changes the SSD to be tested from being connected via the bus to running on the host side. It runs under the powerful CPU / DRAM resources of the host, which is equivalent to the local file system device driver, etc. The communication with the upper-level driver does not need to be transmitted through the bus, but only needs to use the mature inter-process communication technology of the kernel, which can greatly improve the operating efficiency of the SSD firmware, and can fully test / verify its code coverage path, thereby improving the quality of the SSD. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of the conception of the SSD firmware simulation verification system framework in the traditional technology;

[0042] Figure 2 It is a conceptual schematic diagram of the SSD firmware simulation verification system framework in the present invention;

[0043] Figure 3 A schematic diagram of a flow chart of an SSD firmware simulation verification method in one embodiment;

[0044] Figure 4 A schematic diagram of a flow chart of an SSD firmware simulation verification method in another embodiment;

[0045] Figure 5 A schematic diagram of a flow chart of an SSD firmware simulation verification method in yet another embodiment;

[0046] Figure 6A schematic diagram of an implementation framework of an SSD simulation process in one embodiment;

[0047] Figure 7 A schematic diagram of an implementation framework of an SSD simulation process in another embodiment;

[0048] Figure 8 A structural block diagram of an SSD firmware simulation verification system in an embodiment;

[0049] Fig. 9 It is a structural block diagram of an SSD firmware simulation verification system in another embodiment;

[0050] Fig.10 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0052] Currently, if Figure 1 The existing SSD firmware simulation verification system framework includes the following parts:

[0053] Host side: user mode.

[0054] Application: Runs various upper-level software to read and write disks.

[0055] Host side: kernel mode.

[0056] File system: various disk file management system drivers, such as FAT / NTFS / EXT…

[0057] Block device driver: a general kernel block device driver that encapsulates hardware read and write operations and provides a unified interface for upper-layer applications

[0058] Hard disk driver: Specific SSD hardware interface driver, such as SATA / ATA, PCIe / NVMe.

[0059] Hard disk side: Mount various hard disks, such as SSD / HDD, which communicate with the host through a physical bus connection.

[0060] Under the existing SSD firmware simulation and verification system framework, the firmware needs to be compiled and burned to the SSD for operation. At the same time, the SSD is connected to the host through a connector, and the host generates a specific load through the script / OS to test the function and performance of the disk. In this way, in order to achieve coverage of the code path, more hosts / platforms need to be deployed, and due to the limited actual performance of the SSD, it takes a long time to complete a certain test coverage. Even so, because it is a black box test, there are many code blind spots that cannot be covered, and thus there are quality risks.

[0061] Based on this, the present invention provides a SSD firmware simulation verification method, which can be applied to Figure 2 The SSD firmware simulation verification system framework shown in the figure includes the following parts:

[0062] Host side: user mode.

[0063] Application: Runs various upper-level software to read and write disks.

[0064] Host side: kernel mode.

[0065] File system: various disk file management system drivers, such as FAT / NTFS / EXT…

[0066] Block device driver: A general kernel block device driver that encapsulates hardware read and write operations and provides a unified interface for upper-level applications.

[0067] Hard disk driver: Specific SSD hardware interface driver, such as SATA / ATA, PCIe / NVMe.

[0068] Host side: SSD simulator.

[0069] Run the SSD simulation process, which transmits data with the upper-level driver through inter-process communication instead of through the bus.

[0070] Hard disk end: Mount various other hard disks, mount various hard disks, and communicate with the host through a physical bus connection.

[0071] In the present invention, the SSD to be tested is changed from being connected via a bus to running on the host side. It runs under the powerful CPU / DRAM resources of the host, which is equivalent to the local file system / block device driver, etc. Furthermore, the communication with the upper-level driver does not need to be transmitted via the bus, but only needs to use the mature inter-process communication technology of the kernel, which can greatly improve the operating efficiency and the code test coverage.

[0072] In one embodiment, Figure 3As shown, a SSD firmware simulation verification method is provided, the method comprising:

[0073] Step 302, building an SSD firmware simulation system on the host side, and running the SSD firmware under the SSD firmware simulation system on the host side;

[0074] Step 304, running the SSD firmware simulation process on the host side to achieve data transmission with the upper layer driver through inter-process communication;

[0075] Step 306, modifying the SSD driver code on the host side to forward the command transmitted by the bus to the SSD firmware emulation interface;

[0076] Step 308: The SSD firmware simulation system completes corresponding operations according to the input command.

[0077] In this embodiment, a SSD firmware simulation verification method is provided, which can be applied to Figure 2 In the system framework shown, by compiling / running the main logic code of the SSD firmware in the host environment, the hardware part it relies on is replaced by software in the form of simulated behavior, and the CPU / Memory resources of the host can be used for high-speed simulation, which improves the test efficiency and thus ensures the quality of the SSD. The specific implementation steps are as follows:

[0078] First, build an SSD firmware simulation system on the host side, and run the SSD firmware under the SSD firmware simulation system on the host side. Specifically, in order to be similar to the firmware running on the real SSD, several threads are subdivided within the SSD simulation process, including: front-end module, read-write buffer management module, mapping table management module, and back-end module. Secondly, in order to run on the host, the modules that need to be adapted include DRAM space and NAND Array.

[0079] Then, the host runs the SSD firmware simulation process to achieve data transmission with the upper driver through inter-process communication. Then, by modifying the SSD driver code on the host side, the bus transmission command is forwarded to the SSD firmware simulation interface. Finally, the SSD firmware simulation system completes the corresponding operation according to the input command.

[0080] In this embodiment, an SSD firmware simulation system is built on the host side, and the SSD firmware is run under the SSD firmware simulation system on the host side; the SSD firmware simulation process is run on the host side to realize data transmission with the upper-level driver through inter-process communication; the SSD driver code on the host side is modified to forward the bus transmission commands to the SSD firmware simulation interface; the SSD firmware simulation system completes the corresponding operation according to the input commands. This solution changes the SSD to be tested from being connected via the bus to running on the host side. It runs under the powerful CPU / DRAM resources of the host, which is equivalent to the local file system device driver, etc. Communication with the upper-level driver does not need to be transmitted through the bus, but only needs to use the mature inter-process communication technology of the kernel, which can greatly improve the operating efficiency of the SSD firmware, and can fully test / verify its code coverage path, thereby improving the quality of the SSD.

[0081] In one embodiment, Figure 4 As shown, a SSD firmware simulation verification method is provided, and the method also includes:

[0082] Step 402, executing interaction with upper-layer driver commands through the front-end module of the SSD firmware emulation system;

[0083] Step 404, performing allocation and recycling of the read-write buffer by the read-write buffer management module of the SSD firmware emulation system;

[0084] Step 406, performing mapping conversion from the logic address of the upper module to the virtual NAND address through the mapping table management module of the SSD firmware emulation system;

[0085] Step 408, performing read, write and erase operations of the virtual NAND through the backend module of the SSD firmware emulation system;

[0086] Step 410, applying for space from the host's memory for use in the L2P mapping table and the read / write buffer;

[0087] Step 412, requesting an area from the host memory to simulate the DIE / Block / Page structure of NAND to store user data of the upper driver.

[0088] In this embodiment, a SSD firmware simulation verification method is provided. In this method, in order to achieve the similarity with the firmware running on the real SSD, the SSD simulation process is subdivided into the following threads. Figure 6 Shown include:

[0089] Front-end module: responsible for command interaction with the upper-level driver.

[0090] Read-write buffer management module: responsible for the allocation and recovery of the process's read-write buffer.

[0091] Mapping table management module: responsible for the mapping conversion of the logical address of the upper-level module to the virtual NAND address.

[0092] Backend module: responsible for the read, write and erase operations of virtual NAND.

[0093] Secondly, in order to run on the host, the modules that need to be adapted include:

[0094] DRAM space: Instead of using the independent DRAM on the SSD, space is requested from the host memory for use in the L2P mapping table and read / write buffers.

[0095] NAND Array: Apply for an area in the host memory to simulate the DIE / Block / Page composition of NAND to store the user data of the upper-layer driver. Furthermore, considering the limited host memory space, the technical effect of reducing the memory space overhead can be achieved by reducing the simulated SSD capacity or compression technology.

[0096] In this embodiment, based on the framework of the above SSD simulation process, the host-side application and driver do not need to be adjusted, but only the corresponding SSD simulation process is implemented. The data reading and writing of the upper-level driver is converted into the module call in the process and the reading and writing of the NAND Array Memory Disk, which greatly improves the operation speed.

[0097] In one embodiment, Figure 5 As shown, a SSD firmware simulation verification method is provided, and the method also includes:

[0098] Step 502, when the SSD firmware simulation process exits, the NAND Array data in the host memory is written to other hard disk entities of the host through the bus;

[0099] Step 504, when the SSD firmware simulation process is restarted, after the host allocates the corresponding NAND Array Memory space, data is loaded from the hard disk file corresponding to the host and filled into the NAND Array in the memory.

[0100] In this embodiment, a SSD firmware simulation verification method is provided. In this method, since the data in the memory under the simulation model is volatile when power is off, further improvement can be made to fully simulate the data storage function of the SSD. For specific improvement steps, please refer to Figure 7 Shown include:

[0101] First, when the simulation process exits, the NAND Array data in the memory is written to other hard disk entities of the host through the bus, thereby realizing data storage.

[0102] Then, when the simulation process is restarted, after the host allocates the corresponding NAND Array Memory space, the data is loaded from the hard disk file corresponding to the host and filled into the NAND Array in the memory, thereby realizing data recovery.

[0103] In this embodiment, the data storage function of the SSD is fully simulated, and its code coverage path can be fully tested / verified, thereby achieving the technical effect of improving the quality of the SSD.

[0104] It should be understood that although Figure 1-7 The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figure 1-7 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0105] In one embodiment, Figure 8 As shown, a SSD firmware simulation verification system 800 is provided, and the system includes:

[0106] A building module 801 is used to build an SSD firmware simulation system on the host side, and run the SSD firmware under the SSD firmware simulation system on the host side;

[0107] The simulation module 802 is used to run the SSD firmware simulation process on the host side to implement data transmission with the upper layer driver through inter-process communication;

[0108] The command transmission module 803 is used to modify the SSD driver code on the host side and forward the bus transmission command to the SSD firmware simulation interface;

[0109] The command execution module 804 is used for the SSD firmware simulation system to complete corresponding operations according to the input commands.

[0110] In one embodiment, the simulation module 802 is specifically used for:

[0111] The front-end module of the SSD firmware simulation system performs interaction with upper-layer drive commands;

[0112] The read-write buffer management module of the SSD firmware simulation system is used to allocate and recycle the read-write buffer.

[0113] Execute mapping conversion of the logic address of the upper module to the virtual NAND address through the mapping table management module of the SSD firmware emulation system;

[0114] The read, write and erase operations of the virtual NAND are performed through the back-end module of the SSD firmware simulation system.

[0115] In one embodiment, the simulation module 802 is further configured to:

[0116] Applying for space from the host's memory for use in the L2P mapping table and the read / write buffer;

[0117] An area is requested from the memory of the host side to simulate the DIE / Block / Page composition of NAND to store the user data of the upper layer driver.

[0118] In one embodiment, Fig. 9 As shown, a SSD firmware simulation verification system 800 is provided, and the system also includes:

[0119] The data storage module 805 is used to write the NAND array data in the host memory to other hard disk entities of the host through the bus when the SSD firmware simulation process exits;

[0120] The data recovery module 806 is used to load data from the hard disk file corresponding to the host and fill it into the NAND Array in the memory after the host allocates the corresponding NAND Array Memory space when the SSD firmware simulation process is restarted.

[0121] For the specific limitations of the SSD firmware simulation and verification system, please refer to the limitations of the SSD firmware simulation and verification method above, which will not be repeated here.

[0122] In one embodiment, a computer device is provided, whose internal structure diagram can be as follows: Fig.10As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a SSD firmware simulation verification method is implemented.

[0123] Those skilled in the art will understand that Fig.10 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0124] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps in the above method embodiments when executing the computer program.

[0125] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0126] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0127] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0128] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A SSD firmware simulation verification method, characterized in that: The method comprises: Building an SSD firmware simulation system on the host side, and running the SSD firmware under the SSD firmware simulation system on the host side; The host runs an SSD firmware simulation process to achieve data transmission with an upper-layer driver through inter-process communication; Modify the SSD driver code on the host side to forward the bus transmission commands to the SSD firmware emulation interface; The SSD firmware simulation system completes corresponding operations according to the input commands; The steps of running the SSD firmware simulation process on the host side to realize data transmission with the upper-level driver through inter-process communication include: executing interaction with the upper-level driver commands through the front-end module of the SSD firmware simulation system; executing allocation and recovery of read-write buffers through the read-write buffer management module of the SSD firmware simulation system; executing mapping conversion of the logical address of the upper-level module to the virtual NAND address through the mapping table management module of the SSD firmware simulation system; and executing read, write and erase operations of the virtual NAND through the back-end module of the SSD firmware simulation system.

2. The SSD firmware simulation verification method according to claim 1, characterized in that: The step of running the SSD firmware simulation process on the host side to implement data transmission with the upper driver through inter-process communication also includes: Applying for space from the host's memory for use in the L2P mapping table and the read / write buffer; An area is requested from the memory of the host side to simulate the DIE / Block / Page composition of NAND to store the user data of the upper layer driver.

3. The SSD firmware simulation verification method according to claim 1 or 2, characterized in that: The method further comprises: When the SSD firmware simulation process exits, the NAND Array data in the host memory is written to other hard disk entities of the host through the bus; When the SSD firmware simulation process is restarted, after the host allocates the corresponding NAND Array Memory space, data is loaded from the hard disk file corresponding to the host and filled into the NAND Array in the memory.

4. A SSD firmware simulation verification system, characterized in that: The system comprises: A building module, wherein the building module is used to build an SSD firmware simulation system on the host side, and run the SSD firmware under the SSD firmware simulation system on the host side; A simulation module, wherein the simulation module is used to run an SSD firmware simulation process on the host side to implement data transmission with an upper-layer driver through inter-process communication; A command transmission module, which is used to modify the SSD driver code on the host side and forward the bus-transmitted commands to the SSD firmware simulation interface; A command execution module, wherein the command execution module is used for the SSD firmware simulation system to complete corresponding operations according to input commands; The simulation module is specifically used for: executing interaction with upper-level drive commands through the front-end module of the SSD firmware simulation system; executing allocation and recovery of read-write buffers through the read-write buffer management module of the SSD firmware simulation system; executing mapping conversion of the logical address of the upper-level module to the virtual NAND address through the mapping table management module of the SSD firmware simulation system; and executing read, write and erase operations of the virtual NAND through the back-end module of the SSD firmware simulation system.

5. The SSD firmware simulation verification system according to claim 4, characterized in that: The simulation module is also used for: Applying for space from the host's memory for use in the L2P mapping table and the read / write buffer; An area is requested from the memory of the host side to simulate the DIE / Block / Page composition of NAND to store the user data of the upper layer driver.

6. The SSD firmware simulation verification system according to claim 4 or 5, characterized in that: The system further comprises: A data storage module, wherein the data storage module is used to write the NAND Array data in the host memory to other hard disk entities of the host through the bus when the SSD firmware simulation process exits; The data recovery module is used to load data from the hard disk file corresponding to the host and fill it into the NAND Array in the memory after the host allocates the corresponding NAND Array Memory space when the SSD firmware simulation process is restarted.

7. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 are implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 are implemented.