File system deployment method and device and computer program product
Through the identification code, the security and stability problems during file system deployment on the unified compilation and development platform are solved, and flexible and secure deployment strategies are realized, and the stability of the operating system and user trust are improved. .
Patent Information
- Application Number
- CN202411084306.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-07
- Publication Date
- 2024-11-12
AI Technical Summary
When building and deploying file systems on a unified compilation and development platform, there are system resource insecurity problems, the possibility of illegal intrusion increases, and the flexibility of file system instructions and kernel configuration items leads to system instability.
Identify the operating mode of the file system through the preset identification code. If it is in debug mode, execute the debug deployment program. If it is in formal mode, automatically remove the file system instructions and programs in debug mode, and execute the official release program, using pre-generated The controller is deployed and defect repaired.
It effectively solves the problem of system resource insecurity, improves the credibility of caller authorization, simplifies the deployment process, enhances the adaptability and maintenance of the system, and significantly improves the stability of the operating system and the trust of users.
Smart Images

Figure CN118939273A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of computer operating systems, and in particular to a file system deployment method, device and computer program product. Background Art
[0002] Embedded Linux operating systems have been widely used in a variety of business scenarios. The design of this operating system adopts a layered decoupling model, modularizing the functional units of different components such as the kernel, file system, and application. This design method not only promotes the healthy development of the operating system ecosystem, but also improves the flexibility and scalability of the system through component service-oriented.
[0003] Linux embedded operating systems are usually built using build platforms such as buildroot and yocto. These platforms can decouple the various components of the operating system into independent modules, thereby achieving independent design of the Linux kernel, file system, and application programs. This independence allows the file system instructions and programs of the operating system to be flexibly deployed on heterogeneous multi-core chips, or solidified in independent storage locations, to achieve automatic booting of the kernel after power-on.
[0004] However, this design also has some disadvantages and limitations. First, due to the traditional operating system file system architecture and user permission settings, there are certain risks to the security of the system. The possibility of illegal intrusion increases, especially in the login account, authorization, instruction installation and execution, etc., the permission settings are relatively loose, which may lead to a decrease in the security of system resources, and it is expected that the insecurity may increase by more than 20%. Secondly, although the flexibility of file system instructions and kernel configuration items on the operating system has been improved, it also increases the risk of system instability and unreliability. When executing file system business instructions and programs on the operating system, its reliability and stability may be affected, which is where the design needs to be weighed and optimized. Summary of the invention
[0005] The technical problem to be solved by the embodiments of the present invention is to provide a file system deployment method, device and computer program product to eliminate the system resource insecurity generated when building and deploying a file system on a unified compilation development platform and improve the credibility of caller authorization.
[0006] In order to solve the above technical problems, the present invention provides a file system deployment method, comprising the following steps:
[0007] Identify the operation mode of the compiled file system according to a preset identification code;
[0008] If the identified file system operation mode is the debugging mode, the debugging deployment program is executed through the pre-generated controller to obtain the file system instructions and program packages pre-stored in the compilation stage, and install or restore the file system instructions and program packages;
[0009] If the identified file system operation mode is the official mode, the file system instructions and program packages in the debugging mode are automatically removed, and the official release program is executed through the pre-generated controller.
[0010] Preferably, the identification code is any one of a configuration parameter, an environment variable, a startup parameter, the existence of a specific file, and a binary code.
[0011] Preferably, before identifying the operation mode of the compiled file system according to the preset identification code, the method further includes:
[0012] Use buildroot or yocto compilation and development platform technology to build business instructions and programs for heterogeneous multi-core operating systems;
[0013] The root file system generated after the compilation is completed is stored in a predetermined location in the compilation environment.
[0014] Preferably, if the identified file system operation mode is the formal mode, the method further includes: obtaining a patch that is pre-generated and integrated into the file system, and applying the patch to repair the defect.
[0015] Preferably, the method further comprises: pre-generating a third-party compilation tool chain for compiling and generating the patch.
[0016] Preferably, the method further comprises: integrating the patch generated by the third-party compilation tool chain with the root file system to form instructions and programs for overall file system deployment.
[0017] Preferably, the controller is specifically a software component including a series of instructions and programs, which is stored in a predetermined location of a compilation environment after being generated and is in a state of waiting for an external trigger or call.
[0018] Preferably, after executing the debugging deployment program or the formal release program, the method further includes:
[0019] The controller checks whether the system has entered the correct operating mode and whether the deployment process has been successfully completed;
[0020] If the controller detects an anomaly or the deployment process is not completed successfully, it will automatically switch to remote debugging mode;
[0021] In remote debugging mode, the controller uses a secure transmission channel to communicate with the remote debugging tool or service and re-executes the debugging deployment program or the formal release program.
[0022] The present invention also provides a file system deployment device, comprising:
[0023] one or more processors;
[0024] Memory;
[0025] One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, and the one or more application programs are configured to execute the file system deployment method.
[0026] The present invention also provides a computer program product, comprising computer instructions, wherein the computer instructions instruct a computer device to execute operations corresponding to the method.
[0027] The implementation of the present invention has the following beneficial effects: the present invention realizes automatic switching of file system instructions and program calls in the two modes by identifying the identification codes of the debug mode and the formal mode during the code startup phase. This design makes full use of the advantages of the respective deployment and calling methods of the debug mode and the formal mode, and effectively solves the problem of system resource insecurity caused by the coexistence of the file caller of the debug mode and the callee of the formal mode in the same operating system when the file system is built and deployed on a unified compilation and development platform, and improves the credibility of the caller authorization. Through a unified compilation and development platform, the present invention not only simplifies the deployment process, but also enhances the adaptability and maintainability of the system, allowing the system to quickly respond to different operation and maintenance requirements while ensuring safety, significantly improving the stability of the operating system and the trust of users, and providing a flexible and secure deployment strategy for heterogeneous multi-core operating systems. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0029] Figure 1 It is a flowchart of a file system deployment method according to an embodiment of the present invention.
[0030] Figure 2 It is a schematic diagram of the composition and working principle of the host operating system in an embodiment of the present invention. DETAILED DESCRIPTION
[0031] The following descriptions of the embodiments refer to the accompanying drawings to illustrate specific embodiments in which the present invention may be implemented.
[0032] Please refer to Figure 1 As shown, the first embodiment of the present invention provides a file system deployment method, comprising the following steps:
[0033] Identify the operation mode of the compiled file system according to a preset identification code;
[0034] If the identified file system operation mode is the debugging mode, the debugging deployment program is executed through the pre-generated controller to obtain the file system instructions and program packages pre-stored in the compilation stage, and install or restore the file system instructions and program packages;
[0035] If the identified file system operation mode is the official mode, the file system instructions and program packages in the debugging mode are automatically removed, and the official release program is executed through the pre-generated controller.
[0036] Through the above steps, it can be known that the present invention realizes the automatic switching of the calling of file system instructions and programs in the two modes by identifying the identification codes of the debug mode and the formal mode in the code startup stage. This design makes full use of the advantages of the deployment and calling methods of the debug mode and the formal mode, effectively solves the problem of system resource insecurity caused by the coexistence of the file caller in the debug mode and the callee in the formal mode in the same operating system when the file system is built and deployed on a unified compilation and development platform, and improves the credibility of the caller authorization.
[0037] Please refer to Figure 2 As shown in the figure, the host operating system Host OS is an operating system that runs on some physical hardware and serves as the basis for other virtual environments (such as virtual machines or containers), providing necessary services and interfaces for upper-layer applications or virtual environments. Host OS can be common operating systems such as Windows and Linux.
[0038] Figure 2 The main modules and functions of Host OS are shown as follows:
[0039] Host OS building module: responsible for the traditional compilation process, converting source code into executable files, and producing file systems, that is, creating the root file system of the operating system;
[0040] Host OS command and program control module: contains the logic for controlling and executing file system deployment commands and programs, and is responsible for managing and scheduling various tasks during the deployment process;
[0041] Third-party tool chain module: provides a third-party tool chain, including various compilation and debugging tools, to supplement or enhance the default compilation and deployment capabilities of the Host OS;
[0042] Host OS identification module: responsible for identifying the operating system's operating mode (such as debugging mode or formal mode) and other system status information;
[0043] Host OS security identification and automated deployment module: It combines the functions of security identification and automated deployment. It first verifies the security of the deployment operation and then automatically executes the corresponding deployment strategy based on the security identification results.
[0044] Host tool chain storage module: used to centrally store various tool chains required by Host OS, including compilation, linking, debugging tools, etc., for quick access and use.
[0045] Third-party toolchain module: Similar to the Host OS third-party toolchain module, it contains third-party toolchains for specific purposes or optimizations, providing additional functionality based on the Host OS default toolchain.
[0046] The workflow of each module is as follows:
[0047] Compile and build: Use the HostOS build module and the compiler and other tools in the Host toolchain to compile the source code into executable files and build the file system;
[0048] Identification and control: The Host OS identification module determines the operating mode of the operating system, and the Host OS instruction and program control module controls the deployment process based on the identification results;
[0049] Security and deployment: Host security identification and automated deployment modules ensure the security of deployment operations and automatically perform deployment based on identification results;
[0050] Supplement of third-party toolchains: If necessary, the third-party toolchain module and Host OS third-party toolchain module provide additional toolchains to support special compilation or deployment requirements.
[0051] The above process ensures that the construction and deployment of the operating system is automated, secure, and customizable, and the deployment strategy can be flexibly adjusted according to different operating modes and requirements.
[0052] Specifically, it can be understood that the construction of the operating system is not only to compile the kernel, but also to compile and integrate various business-related applications and instructions. In an embodiment of the present invention, the business instructions and programs of the heterogeneous multi-core operating system are first constructed using the buildroot or yocto compilation development platform technology. These business instructions and programs are functions provided by the operating system to users or system services. After the compilation is completed, the generated root file system (including all files and directory structures of the operating system) will be stored in a predefined location in the compilation environment. The root file system is the basis of the operating system and contains all files, directories, configurations, etc. required for the operating system to start and run. It is usually a complete, self-contained file system image that can exist independently of the kernel and can be loaded into memory when the system starts.
[0053] The above-mentioned construction of the root file system provides a foundation for subsequent deployment and pattern recognition.
[0054] In order to create a control mechanism that can manage and execute file system deployment tasks, an embodiment of the present invention pregenerates a software component, namely a "controller", which contains a series of instructions and programs for controlling the deployment process of the file system. Similarly, the controller is stored in a predetermined location in the compilation environment. After storage, the controller is in a standby state, waiting for external triggers or calls. When the controller is triggered, it will initialize and start scanning all functional points in the entire business system, and then compare the scan results with the required configuration to identify any defects or omissions that do not meet expectations. The controller can ensure that the deployment process is carried out in accordance with the predetermined requirements and configuration, and can also discover and report potential problems.
[0055] In an embodiment of the present invention, the predetermined location of the compilation environment specifically refers to one or more predefined storage spaces, such as a directory or folder of a local file system. For the aforementioned root file system, the predetermined location of the compilation environment where it is stored is usually organized based on the directory structure of the project, and can be a subdirectory under the project directory, such as rootfs or filesystem. For the generated controller, the predetermined location of the compilation environment where it is stored is set to store the executable files or library files generated by the compilation, such as build, bin or out directories. In short, the predetermined location of the compilation environment is a safe, easy-to-access location that can ensure data integrity, and can support efficient data read and write operations, so as to quickly load the required files when the system is deployed or updated.
[0056] In order to supplement and improve the default compilation and deployment process of the build platform and solve possible defects, the embodiment of the present invention pre-generates a third-party compilation tool chain that can form an independent system, which can work with existing build platforms such as buildroot or yocto to compile and generate components missing in the file system of the default compilation and deployment of Buildroot or Yocto. These components can be optimizations for specific hardware, specific drivers, security patches, etc.
[0057] After that, the file system compiled and deployed by the Buildroot or Yocto build platform is integrated with the patches generated by the third-party compilation toolchain to ensure that the components in the two file systems can work together to form an overall file system deployment. After the patches are merged, new deployment instructions and programs will be generated, which will guide the subsequent file system deployment and configuration. Through the patch merging step, it can be ensured that the final deployment of the operating system can meet all business needs and key links of specific scenarios.
[0058] Next, use a dedicated partitioning tool to dynamically create partitions on the file system. Unlike static partitions, dynamic partitions can be created when needed and deleted or resized when not needed, which is more flexible. Specifically, create a storage partition for the file system business deployment tool chain. You can create a dedicated storage partition for the file system business deployment tool chain. The business deployment tool chain includes a series of software, scripts, configuration files, etc., which are used to deploy and configure services in the file system. By storing these tool chains in a dedicated partition, they can be better managed to ensure that they are not confused or conflicted with other parts of the file system.
[0059] It should be noted that the aforementioned controller generation, patch generation and merging, dynamic partitioning and other steps are preparations for pattern recognition and its subsequent execution steps to ensure that all necessary components and tools are ready and can be correctly identified and used when the system starts and the pattern is recognized. Specifically, the generated controller is responsible for identifying whether the file system is in debug mode or formal mode according to the preset identification code when the system starts. The generation and merging of patches ensure that the file system contains necessary updates and fixes, which may be targeted at specific defects or optimization requirements. After pattern recognition, the system can decide whether to apply these patches based on the recognized mode (debug or formal). The creation of dynamic partitions provides storage space for the file system business deployment tool chain. After pattern recognition, the system can load the corresponding tool chain from these partitions as needed to perform debugging or formal release deployment tasks.
[0060] After completing the above preparations, the system starts and begins to identify the identification codes of the debug mode and the formal mode. In an embedded Linux system, "system" usually refers to the software environment on the entire embedded device, including the operating system kernel, device drivers, middleware, applications, and all necessary configuration files and startup scripts. The system startup phase means that the embedded Linux system is starting from the power-on or restart state, and undergoes a series of initialization processes until it reaches a state where it can run normally. In this process, the system will load the kernel, initialize device drivers, configure the network, start various services, etc., until the end user can see a usable operating system interface or application interface. Pattern recognition occurs in this process, and it is responsible for determining whether the system should be started and run in debug mode or formal mode.
[0061] The debug mode and the official mode each have unique identifiers, which are explicitly set and embedded in the root file system during the system compilation phase, or stored in the system firmware, UEFI variables, or dedicated configuration storage areas, and then read when the system starts and used to determine subsequent behavior. These identifiers can be:
[0062] Configuration parameters: Configuration parameters are one of the most common types of identification codes and are usually stored in configuration files. During system startup or deployment, the controller can read these parameters to determine the operating mode. They have the advantage of being easy to modify and maintain, and are suitable for distinguishing different deployment requirements.
[0063] Environment variables: Environment variables provide a flexible way to set and pass runtime configuration information. Both the operating system and the application can access environment variables. By setting specific environment variables, you can switch between debug mode and formal mode.
[0064] Startup parameters: Startup parameters are parameters passed to the operating system or application when the system starts. They can be used to indicate the specific configuration or deployment program that the system should load, thereby achieving automatic recognition of the operating mode.
[0065] Existence of specific files: In the file system, the existence of specific files (such as configuration files with extensions of `.cfg` or `.env`) can be used as identification codes. The controller can identify the operating mode by checking the existence of these files.
[0066] Binary code: For scenarios with higher security requirements, binary codes or hash values can be used as identification codes. They can be generated by a specific algorithm and verified when the system starts.
[0067] In some cases, the system may find identifiers for both debug mode and official mode at the same time, in which case you need to set the priority of the identifiers. Usually, the debug mode identifier is set to a higher priority to ensure that debug mode is used first during development and testing. If an identifier conflict occurs, the system will select the mode that should be started according to the preset priority rules.
[0068] Identify the operating mode of the file system through the identification code, and then execute the operating mode:
[0069] (I) Debug mode
[0070] If the identified file system operation mode is debug mode, the debug deployment procedure is executed after passing the security authentication procedure:
[0071] First, the file system instructions and program packages pre-stored during the compilation phase are automatically decompressed, such as debugging tools, configuration files, test scripts, etc.
[0072] Then enter the installation and restoration process to install or restore these instructions and packages to the system to configure the debugging environment. The system will copy the decompressed files to the specified directory according to the preset configuration and script. The installation process involves operations such as configuring environment variables, updating system link libraries, and registering services. The restoration process also includes restoring databases, configuration files, and other system states.
[0073] (II) Formal Mode
[0074] If the identified file system operation mode is the official mode, the official release procedure will be executed after passing the security certification procedure.
[0075] In the official mode, you need to ensure that you are using an optimized, tested, and verified file system deployment to ensure system stability and security, so you automatically remove file system instructions and programs in debug mode. Automatic removal operations generally involve deleting specific files in debug mode, stopping services in debug mode, and replacing configuration files in debug mode to clean up temporary files, test data, and unoptimized code that may be left in debug mode, ensuring that the file system in the official environment is clean, tidy, and efficient, and preventing debugging tools and programs from interfering with the official operating environment.
[0076] Then enter the defect repair process:
[0077] Firstly, automatically decompress the patch that was previously generated and integrated into the file system;
[0078] The patch is then applied to perform a defect fix, such as replacing a file, updating a database record, or modifying an in-memory data structure.
[0079] After executing the corresponding debugging deployment procedure or formal release procedure, the controller will perform status confirmation: that is, the controller will check whether the system has entered the correct operating mode as expected and whether the deployment process has been successfully completed. If everything is normal, the system will continue to run in the currently confirmed mode without further intervention. If the controller detects an anomaly or the deployment process is not successfully completed, it will automatically switch to remote debugging mode.
[0080] In remote debugging mode, the controller uses a secure transmission channel to communicate with remote debugging tools or services for troubleshooting and system recovery. A secure transmission channel refers to an encrypted communication connection that ensures the security and integrity of data transmission during remote debugging. In remote debugging mode, you can re-execute the debug deployment program or the official release program to try to correct the problem. In some cases, such as when the system environment is limited or only a single test is required, it may not be necessary to solidify the debugging tool or program into the system's storage partition. At this time, the system can choose to enter remote debugging mode directly to quickly respond to and handle problems without waiting for the system to load the debugging tool from the storage medium.
[0081] Through the above-mentioned monitoring of execution results and automatic processing mechanism in abnormal situations, the stability and reliability of the system are ensured, and even when problems arise, they can be debugged and repaired in time.
[0082] The present invention proposes an innovative file system deployment solution, which realizes the deep integration of unified construction, removal and restoration deployment of debug mode and formal mode. Specifically, the present invention can automatically identify whether the system is in debug mode or formal mode during the code startup phase, and this identification is completed based on a preset identification code. According to the identification result, the system will automatically select and call the corresponding file system instructions and programs, thereby giving play to the advantages of the two mode deployment methods. In a heterogeneous multi-core operating system environment, the present invention allows the file system business to use a unified pure version of the file system, rather than relying on a fixed file system deployment or factory burning and solidification. This method not only improves the flexibility and adaptability of the system, but also builds and deploys the file system through a unified compilation and development platform, effectively solving the system resource security problem that may arise due to the coexistence of different modes in the same operating system. In addition, the present invention further improves the security of the system by enhancing the credibility of the caller authorization. The present invention is more flexible and secure by dynamically identifying and switching modes compared to the traditional file system deployment solution that usually adopts a fixed file system deployment strategy.
[0083] Corresponding to the file system deployment method described in the first embodiment of the present invention, the second embodiment of the present invention further provides a file system deployment device, including:
[0084] one or more processors;
[0085] Memory;
[0086] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the file system deployment method described in the aforementioned embodiment 1 of the present invention.
[0087] Corresponding to the file system deployment method described in the aforementioned embodiment 1 of the present invention, embodiment 3 of the present invention further provides a computer program product, including computer instructions, wherein the computer instructions instruct a computer device to execute operations corresponding to the file system deployment method described in the aforementioned embodiment 1 of the present invention.
[0088] Preferably, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor. The processor is the control center of the device, and various parts of the device are connected using various interfaces and lines.
[0089] The memory mainly includes a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function, etc., and the data storage area can store related data, etc. In addition, the memory can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard disk, a smart memory card (SmartMedia Card, SMC), a secure digital (Secure Digital, SD) card, and a flash card (Flash Card), etc., or the memory can also be other volatile solid-state storage devices.
[0090] It should be noted that the above-mentioned device may include but is not limited to a processor and a memory, which can be understood by those skilled in the art.
[0091] For the working principle and process of the above embodiment, please refer to the description of the above embodiment of the present invention, which will not be repeated here.
[0092] It can be seen from the above description that compared with the prior art, the beneficial effect of the present invention is that the present invention realizes the automatic switching of the calling of the file system instructions and programs in the two modes by identifying the identification codes of the debug mode and the formal mode in the code startup stage. This design makes full use of the advantages of the respective deployment and calling methods of the debug mode and the formal mode, effectively solves the problem of system resource insecurity caused by the coexistence of the file caller of the debug mode and the callee of the formal mode in the same operating system when the file system is built and deployed on a unified compilation and development platform, and improves the credibility of the caller authorization. Through a unified compilation and development platform, the present invention not only simplifies the deployment process, but also enhances the adaptability and maintainability of the system, allowing the system to quickly respond to different operation and maintenance requirements while ensuring safety, significantly improving the stability of the operating system and the trust of users, and providing a flexible and secure deployment strategy for heterogeneous multi-core operating systems.
[0093] The above disclosure is only the preferred embodiment of the present invention, which certainly cannot be used to limit the scope of the present invention. Therefore, equivalent changes made according to the claims of the present invention are still within the scope of the present invention.
Claims
1. A file system deployment method, characterized in that: The following steps are involved: Identify the operation mode of the compiled file system according to a preset identification code; If the identified file system operation mode is the debugging mode, the debugging deployment program is executed through the pre-generated controller to obtain the file system instructions and program packages pre-stored in the compilation stage, and install or restore the file system instructions and program packages; If the identified file system operation mode is the official mode, the file system instructions and program packages in the debugging mode are automatically removed, and the official release program is executed through the pre-generated controller.
2. The method according to claim 1, characterized in that The identification code is specifically any one of a configuration parameter, an environment variable, a startup parameter, the existence of a specific file, and a binary code.
3. The method according to claim 1, characterized in that Before identifying the operation mode of the compiled file system according to the preset identification code, the method further includes: Use buildroot or yocto compilation and development platform technology to build business instructions and programs for heterogeneous multi-core operating systems; The root file system generated after the compilation is completed is stored in a predetermined location in the compilation environment.
4. The method according to claim 1, characterized in that: If the identified file system operation mode is the formal mode, the method further includes: obtaining a patch that is pre-generated and integrated into the file system, and applying the patch to repair the defect.
5. The method according to claim 4, characterized in that Also includes: A third-party compilation tool chain is pre-generated for compiling and generating the patch.
6. The method according to claim 5, characterized in that Also includes: The patch generated by the third-party compilation tool chain is integrated with the root file system to form instructions and programs for overall file system deployment.
7. The method according to claim 1, characterized in that The controller is specifically a software component including a series of instructions and programs, which is stored in a predetermined location of a compilation environment after being generated and is in a state of waiting for an external trigger or call.
8. The method according to claim 1, characterized in that After executing the debug deployment procedure or the official release procedure, it also includes: The controller checks whether the system has entered the correct operating mode and whether the deployment process has been successfully completed; If the controller detects an anomaly or the deployment process is not completed successfully, it will automatically switch to remote debugging mode; In remote debugging mode, the controller uses a secure transmission channel to communicate with the remote debugging tool or service and re-executes the debugging deployment program or the formal release program.
9. A file system deployment device, characterized in that: include: one or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more applications are configured to execute the file system deployment method according to any one of claims 1 to 8.
10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions instruct a computer device to execute operations corresponding to the method according to any one of claims 1 to 8.
Citation Information
Cited By
Resource allocation isolation system and method of heterogeneous operating system, and storage medium
CN120429110A
