CN115495158B - Dynamic construction method for system service in microkernel operating system - Google Patents

Dynamic construction method for system service in microkernel operating system Download PDF

Info

Publication number
CN115495158B
CN115495158B CN202211226300.2A CN202211226300A CN115495158B CN 115495158 B CN115495158 B CN 115495158B CN 202211226300 A CN202211226300 A CN 202211226300A CN 115495158 B CN115495158 B CN 115495158B
Authority
CN
China
Prior art keywords
elf
system service
module
dynamic link
executable file
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202211226300.2A
Other languages
Chinese (zh)
Other versions
CN115495158A (en
Inventor
肖堃
易佳佳
罗蕾
陈丽蓉
李蒙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
University of Electronic Science and Technology of China
China Mobile IoT Co Ltd
Original Assignee
University of Electronic Science and Technology of China
China Mobile IoT Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by University of Electronic Science and Technology of China, China Mobile IoT Co Ltd filed Critical University of Electronic Science and Technology of China
Priority to CN202211226300.2A priority Critical patent/CN115495158B/en
Publication of CN115495158A publication Critical patent/CN115495158A/en
Application granted granted Critical
Publication of CN115495158B publication Critical patent/CN115495158B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Devices For Executing Special Programs (AREA)

Abstract

The invention discloses a dynamic construction method of system service in microkernel operating system, which comprises compiling required system service module, device driver and application program into ELF executable file or ELF dynamic link library, deploying system service loader in user mode, compiling system service loader into mirror image file and integrating with kernel mirror image; the system service loader starts after the kernel starts, reads an ELF executable file of a module to be loaded according to a typed instruction and loads the ELF executable file, and the module operates in an address space isolated from other modules as an independent task after loading is completed, and dynamically links a shared library required by the module to the address space of the module; the system service loader may also complete the uninstallation and updating of executable program modules, shared libraries. The invention can dynamically load the ELF executable file and the dynamic link shared library of the module under the condition of not restarting the microkernel operating system, thereby realizing the dynamic construction of the system service.

Description

Dynamic construction method for system service in microkernel operating system
Technical Field
The invention belongs to the technical field of microkernel operating systems, and particularly relates to a dynamic construction method for system services in a microkernel operating system.
Background
With the higher requirements on the safety and reliability of embedded systems in the internet of things and industrial control scenes, the operating system of the micro-kernel architecture is greatly focused. Although the kernel of the micro-kernel operating system is tiny, abundant system service modules can be realized in a user mode to adapt to the complex requirements on the functions of the operating system, and the modularized design ensures the safety and fault isolation of the operating system.
In microkernel operating systems, the kernel only retains the reduced functionality, and most of the services in the operating system are decoupled and run as independent user-mode applications in isolated user-mode address spaces, so that the microkernel operating system needs to consider what method to use to build system services. In the current microkernel operating system construction process, system services and kernels are often integrated, namely, part of service modules are statically selected to be compiled to an operating system according to requirements, and the greatest disadvantage of the method is that if one module needs to be upgraded or replaced, the system needs to be recompiled, released and started, so that the rapid construction of the system and the dynamic expansion of resources cannot be met. In the internet of things and industrial control environments, an operating system is often required to support dynamic increase or decrease of system services so as to adapt to dynamic changes of hardware resources or adapt to various node environments in a distributed processing environment, and the existing technical scheme cannot meet the requirement.
In the prior art, the research on dynamically constructing an operating system is very lack, and ELF (Executable and Linkable Format, executable connection format) files compiled on Linux are loaded when the microkernel system runs in an L4/Fiasco microkernel operating system in the literature of the design and research of an ELF file mechanism directly loaded by the microkernel system, but only the loading method of the executable files with static links is researched. In the static construction method, the system service modules are compiled into target files, and then the linker links the system service modules and the kernel into an operating system mirror image, and then execution is started. The greatest disadvantage of this approach is that if one system module needs to be upgraded or replaced, the operating system needs to be recompiled, released and started. In addition, in the static construction method, the system service is a static linked executable file, the mapping and loading processes are relatively simple, but the codes and data of the common shared library need to have copies in each system service module, and great system resource waste exists.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a dynamic construction method of system services in a microkernel operating system, which is characterized in that a system service loader is deployed to be packaged and released with a kernel, and ELF executable files and dynamic link shared libraries of a dynamic loading module are dynamically loaded under the condition that the microkernel operating system is not required to be restarted, so that the dynamic construction of the system services of the microkernel operating system is realized.
In order to achieve the above object, the method for dynamically constructing the system service in the microkernel operating system of the present invention comprises the following steps:
s1: for the required system service module and equipment driver, if the condition of compiling into an ELF dynamic link library is met, compiling into the ELF dynamic link library, and calling an ELF executable file as a shared library, otherwise compiling into the ELF executable file; compiling the required application program into an ELF executable file;
s2: a user mode deployment system service loader in the microkernel operating system is used for loading ELF executable files and linking ELF dynamic link libraries, compiling the system service loader into image files and integrating the image files with the kernel images;
s3: in the starting process of the microkernel operating system, a system service loader is started after the kernel is started; for a system service module, a device driver and an application program compiled into ELF executable files, when any one of the modules needs to be loaded, a system service loader reads the corresponding ELF executable file and loads the ELF executable file, and the module operates in an address space isolated from other modules as an independent task after loading is completed; when a certain system service module or equipment driver compiled into an ELF dynamic link library needs to be linked in the module loading process, the system service loader dynamically links the ELF dynamic link library into the address space of the module, and then the module can be started to be executed, and the linked ELF dynamic link library can be called in the module executing process;
s4: when any one of a system service module, a device driver or an application program loaded in an ELF executable file form is required to be unloaded, the system service loader unloads the corresponding ELF executable file, and the mapping completed in the loading process is recovered and canceled;
when any one of the system service module and the device driver which are linked in the form of an ELF dynamic link library is not used any more, the system service loader disconnects the dynamic link with each relevant module depending on the system service loader and recovers the system resources of the system service module;
s5: when any one of a system service module, a device driver or an application program which is loaded in an ELF executable file form needs to be updated, unloading is firstly carried out, then the updated ELF executable file is reloaded, and dynamic link is carried out on the needed shared library again;
when any one of the system service module or the device driver linked in the form of an ELF dynamic link library needs to be updated, execution of the relevant module dependent thereon is disabled, and then the system service loader dynamically links the updated ELF dynamic link library to the relevant module.
The invention relates to a dynamic construction method of system service in a microkernel operating system, which comprises the steps of compiling a required system service module, equipment driver and application program into ELF executable files or ELF dynamic link libraries which are mutually independent, deploying a system service loader in a user mode in the microkernel operating system, compiling the system service loader into an image file and integrating the image file with a kernel image; the system service loader starts after the kernel starts, reads an ELF executable file of a module to be loaded according to a typed instruction and loads the ELF executable file, and the module operates in an address space isolated from other modules as an independent task after loading is completed, and dynamically links a shared library required by the module to the address space of the module; the system service loader may also complete the uninstallation and updating of executable program modules, shared libraries.
The invention has the following beneficial effects:
1) According to the invention, the system service module, the device driver and the application program are compiled into the ELF executable file, the system service is supported to be dynamically loaded or unloaded when the operating system is running, and each module is loaded and then runs in the mutually isolated address space as an independent task, so that the system service module can be independently maintained, the problem of lack of flexibility in static service construction can be effectively solved, and the flexibility in system service construction of the microkernel operating system is improved;
2) The invention constructs the sharable system service module and the device driver as the ELF dynamic link library, and a plurality of modules of the shared library are required to be linked with the ELF dynamic link library by adopting a dynamic link method, thereby solving the problem of resource waste of the shared library in static service construction and greatly saving memory space resources.
Drawings
FIG. 1 is a flow chart of a method for dynamically building system services in a microkernel operating system according to an embodiment of the present invention;
FIG. 2 is a diagram of a dynamic framework of the system services of the present invention;
FIG. 3 is a flow chart of the loading of ELF executable files and linking of dynamically linked libraries by the system services loader in this embodiment;
fig. 4 is a flowchart of the loading main module in the present embodiment;
FIG. 5 is a flow chart of a dynamically linked ELF dynamically linked library in the present embodiment.
Detailed Description
The following description of the embodiments of the invention is presented in conjunction with the accompanying drawings to provide a better understanding of the invention to those skilled in the art. It is to be expressly noted that in the description below, detailed descriptions of known functions and designs are omitted here as perhaps obscuring the present invention.
Examples
FIG. 1 is a flow chart of a method for dynamically building system services in a microkernel operating system according to an embodiment of the present invention. As shown in FIG. 1, the method for dynamically constructing the system service in the microkernel operating system comprises the following specific steps:
s101: building an ELF file:
and for the required system service module and equipment driving, if the condition of compiling into the ELF dynamic link library is met, compiling into the ELF dynamic link library, and calling the ELF executable file as a shared library, otherwise compiling into the ELF executable file. The required application is compiled into an ELF executable file.
The system service module generally comprises a network protocol stack, a UI framework, a log system and the like, the device driver generally comprises a network card driver, a serial port driver and the like, and the system service module and the device driver are mostly compiled into ELF executable files at present. The system service modules that can be compiled into a shared library typically include a C library, a c++ library, a cryptographic library, and the like. In the compiling process, in order to facilitate the sharing of libraries for simultaneous use by different modules, address independent code (PIC) compiling is used when the ELF dynamic link libraries are compiled, and the ELF executable files are compiled by adopting a conventional compiling method.
S102: deploying a system service loader:
and the user mode deployment system service loader in the microkernel operating system is used for loading the ELF executable file and the linked ELF dynamic link library, compiling the system service loader into an image file and integrating the image file with the kernel image.
In general, in the user mode in the microkernel operating system, a small number of necessary basic services including file system, memory management, shell, error handling, etc. are deployed, and the system service loader also needs to use these basic services. Similarly, these basic services are compiled into image files and integrated with the kernel image to facilitate loading directly after the kernel is started.
S103: loading an ELF executable file and linking an ELF dynamic link library:
in the starting process of the microkernel operating system, a system service loader is started after the kernel is started. For a system service module, a device driver and an application program compiled into ELF executable files, when any one of the modules needs to be loaded, a system service loader reads the corresponding ELF executable file and loads the ELF executable file, and the module operates in an address space isolated from other modules as an independent task after loading is completed. When a certain system service module or device driver compiled into an ELF dynamic link library needs to be linked in the module loading process, the system service loader dynamically links the ELF dynamic link library into the address space of the module. The module may then begin executing, and the linked ELF dynamic link library may be invoked during execution of the module.
Generally, if execution of an application program needs to depend on a system service module or a device driver, the system service module or the device driver needs to be loaded in advance when loading.
S104: unloading an ELF executable file or ELF dynamic link library:
when any one of a system service module, a device driver or an application program loaded in the form of an ELF executable file needs to be unloaded, the system service loader unloads the corresponding ELF executable file, retrieves the cache and cancels the mapping completed in the loading process.
When any one of the system service module and the device driver linked in the form of an ELF dynamic link library is not used any more, the system service loader disconnects the dynamic link with each relevant module depending on the system service loader and recovers the system resources of the system service module.
S105: updating an ELF executable file or an ELF dynamic link library:
when any one of the system service module, the device driver or the application program loaded in the form of the ELF executable file needs to be updated, unloading is firstly carried out, then the updated ELF executable file is reloaded, and dynamic linking is carried out on the needed shared library again.
When any one of the system service module or the device driver linked in the form of an ELF dynamic link library needs to be updated, execution of the relevant module dependent thereon is disabled, and then the system service loader dynamically links the updated ELF dynamic link library to the relevant module.
FIG. 2 is a diagram of a dynamic framework of the system services of the present invention. As shown in fig. 2, the system service loader loads the system service module, the device driver and the application program, and dynamically connects the required shared library to the address space of the corresponding module while loading. Under the dynamic system service construction framework, the microkernel operating system supports dynamic loading or unloading of system services while running, so that hot plug of operating system functions is realized, and flexibility and scalability of the system are enhanced. In addition, the system service module is compiled into the shared library and then dynamically linked, so that the number of copies of the public service codes in the system can be reduced to reduce the waste of storage space resources, and the system service shared library is updated in a running mode, so that the convenience of the system is greatly improved.
In order to enable the system service loader to load and link the ELF executable file and the ELF dynamic link library more quickly, a preferred implementation method is provided in the embodiment. FIG. 3 is a flow chart of the loading of ELF executable files by the system service loader and the linking of ELF dynamic link libraries in this embodiment. As shown in fig. 3, the specific steps of loading the ELF executable file and linking the ELF dynamic link library by the system service loader in this embodiment include:
s301: creating an elf_task task:
in the microkernel operating system, a user requests a system service loader to load a system service, a device driver or an application program in an ELF executable file format by inputting a command in Shell or by a system call, after the system service loader receives the user request, an elf_task (loading and executing the ELF program) task is created for each loading process in the microkernel, the task is used for executing codes of the system service loader to load the ELF executable file and link the ELF dynamic link library, and after loading is completed, the system service, the device driver and the application program are all operated in an address space where the corresponding task and other tasks are isolated from each other.
S302: loading a main module:
the elf_task task starts the system service loader and loads the main module, which refers to the module where the ELF executable file is located. Fig. 4 is a flowchart of the loading master module in this embodiment. As shown in fig. 4, the specific steps of loading the main module in this embodiment include:
s401: checking ELF header validity:
and reading the ELF executable file, checking the validity of the ELF header, if the ELF header is legal, entering step S402, otherwise, carrying out error prompt.
S402: analyzing the file:
and analyzing the ELF executable file, and judging whether a PT_INTEP segment exists or not. In an ELF executable, the PT_INTEP segment is used to give the location and length of a string that is called as an interpreter, which is only meaningful to the executable, and which the dynamically linked executable is required to contain. Thus, if there is a PT_INTEP segment, then the ELF dynamically linked library needs to be linked, and if not, then the ELF dynamically linked library does not need to be linked. The parsed pt_load (loadable) and pt_dynamic (DYNAMIC link information) segments are then recorded.
S403: pt_load loading:
the pt_load segment is mapped and then loaded into memory. In this embodiment, an interface sys_mmap adapted to a system service loader is configured in the kernel, and is used to allocate a memory space for the ELF executable file and the ELF dynamic link library, map a memory, and load the memory into a physical memory.
S404: obtaining a dependency library:
traversing PT_DYNAMIC segment, searching and recording the dependent ELF DYNAMIC link library, and obtaining a dependency library list.
S405: searching a dynamic link table:
tables for dynamic linking, including dynamic symbol tables, dynamic string tables, hash tables, are looked up and recorded.
S406: analyzing the starting and stopping sections:
and analyzing and recording init segments and finish segments, wherein the init segments and the finish segments are used for initializing and ending in the execution process of the module corresponding to the ELF executable file.
S303: judging whether the step S302 detects that the ELF dynamic link library needs to be linked in the process of loading the main module, if so, proceeding to a step S304, otherwise, ending the loading.
S304: link ELF dynamic link library:
traversing the dependency library list in the ELF executable file, and sequentially linking the ELF dynamic link libraries. FIG. 5 is a flow chart of linking ELF dynamic link libraries in this embodiment. As shown in fig. 5, the specific steps of linking the ELF dynamic link library in this embodiment include:
s501: mapping an ELF dynamic link library:
and sequentially taking the ELF dynamic link libraries out of the dependency library list, adding the ELF dynamic link libraries into a loading set if the ELF dynamic link libraries are not loaded, and otherwise, performing no operation.
S502: redirecting:
traversing the header table of the section area, searching a redirection section area SHT_REL (redirection table section area) and SHT_RELA (redirection table section area), and redirecting external symbols (including variables and functions) in the redirection section area according to types, namely converting the relative address of the external symbols in an ELF dynamic link library into a determined address in an address space of an ELF executable file of dynamic link according to the address space.
S503: loading the ELF dynamic link library into a memory:
and sequentially taking out the code segments and the data segments of each ELF dynamic link library from the loading set, and loading the code segments and the data segments into the memory.
While the foregoing describes illustrative embodiments of the present invention to facilitate an understanding of the present invention by those skilled in the art, it should be understood that the present invention is not limited to the scope of the embodiments, but is to be construed as protected by the accompanying claims insofar as various changes are within the spirit and scope of the present invention as defined and defined by the appended claims.

Claims (3)

1. The dynamic construction method of the system service in the microkernel operating system is characterized by comprising the following steps:
s1: for the required system service module and equipment driver, if the condition of compiling into an ELF dynamic link library is met, compiling into the ELF dynamic link library, and calling an ELF executable file as a shared library, otherwise compiling into the ELF executable file; compiling the required application program into an ELF executable file;
s2: a user mode deployment system service loader in the microkernel operating system is used for loading ELF executable files and linking ELF dynamic link libraries, compiling the system service loader into image files and integrating the image files with the kernel images;
s3: in the starting process of the microkernel operating system, a system service loader is started after the kernel is started; for a system service module, a device driver and an application program compiled into ELF executable files, when any one of the modules needs to be loaded, a system service loader reads the corresponding ELF executable file and loads the ELF executable file, and the module operates in an address space isolated from other modules as an independent task after loading is completed; when a certain system service module or equipment driver compiled into an ELF dynamic link library needs to be linked in the module loading process, the system service loader dynamically links the ELF dynamic link library into the address space of the module, and then the module can be started to be executed, and the linked ELF dynamic link library can be called in the module executing process; the loading of the ELF executable file and the linking of the dynamic link library by the system service loader are carried out by adopting the following method:
s3.1: in the microkernel operating system, a user requests a system service loader to load system services, device drivers or application programs in an ELF executable file format through inputting commands in Shell or through system call, after the system service loader receives a user request, an elf_task task is created for each loading process in microkernel, the task is used for executing codes of the system service loader to load the ELF executable files and link an ELF dynamic link library, and after loading is completed, the system services, the device drivers and the application programs are all operated in address spaces where corresponding tasks and other tasks are isolated from each other;
s3.2: the elf_task task starts a system service loader and loads a main module, wherein the main module refers to a module where an ELF executable file is located;
s3.3: judging whether the step S3.2 detects that the ELF dynamic link library needs to be linked in the process of loading the main module, if so, entering the step S3.4, otherwise, ending the loading;
s3.4: traversing a dependency library list in the ELF executable file, and sequentially linking all ELF dynamic link libraries;
s4: when any one of a system service module, a device driver or an application program loaded in an ELF executable file form is required to be unloaded, the system service loader unloads the corresponding ELF executable file, and the mapping completed in the loading process is recovered and canceled;
when any one of the system service module and the device driver which are linked in the form of an ELF dynamic link library is not used any more, the system service loader disconnects the dynamic link with each relevant module depending on the system service loader and recovers the system resources of the system service module;
s5: when any one of a system service module, a device driver or an application program which is loaded in an ELF executable file form needs to be updated, unloading is firstly carried out, then the updated ELF executable file is reloaded, and dynamic link is carried out on the needed shared library again;
when any one of the system service module or the device driver linked in the form of an ELF dynamic link library needs to be updated, execution of the relevant module dependent thereon is disabled, and then the system service loader dynamically links the updated ELF dynamic link library to the relevant module.
2. The method for dynamically constructing the system service in the microkernel operating system according to claim 1, wherein the specific method for loading the main module in step S3.2 is as follows:
s3.2.1: reading an ELF executable file, checking the validity of an ELF header, if the ELF header is legal, entering a step S3.2.2, otherwise, performing error prompt;
s3.2.2: analyzing the ELF executable file, judging whether a PT_INTEP segment exists, if so, linking the ELF dynamic link library, and if not, linking the ELF dynamic link library; then recording the analyzed PT_LOAD section and PT_DYNAMIC section;
s3.2.3: mapping the PT_LOAD segment, and then loading the PT_LOAD segment into a memory;
s3.2.4: traversing the PT_DYNAMIC segment, and searching and recording the dependent ELF DYNAMIC link library to obtain a dependency library list;
s3.2.5: searching and recording a table for dynamic link, wherein the table comprises a dynamic symbol table, a dynamic character string table and a hash table;
s3.2.6: and analyzing and recording init segments and finish segments, wherein the init segments and the finish segments are used for initializing and ending in the execution process of the module corresponding to the ELF executable file.
3. The method for dynamically constructing the system service in the microkernel operating system according to claim 1, wherein the specific method for linking the dynamic link library in step S3.4 is as follows:
s3.4.1: sequentially taking the ELF dynamic link library from the dependency library list, adding the ELF dynamic link library into a loading set if the ELF dynamic link library is not loaded, otherwise, performing no operation;
s3.4.2: traversing the header table of the section area, searching the redirection section areas SHT_REL and SHT_RELA, and redirecting the external symbols in the redirection section area according to the type, namely converting the relative addresses of the external symbols in an ELF dynamic link library into determined addresses in an ELF executable file according to the address space of the dynamic link;
s3.4.3: and sequentially taking out the code segments and the data segments of each ELF dynamic link library from the loading set, and loading the code segments and the data segments into the memory.
CN202211226300.2A 2022-10-09 2022-10-09 Dynamic construction method for system service in microkernel operating system Active CN115495158B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211226300.2A CN115495158B (en) 2022-10-09 2022-10-09 Dynamic construction method for system service in microkernel operating system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211226300.2A CN115495158B (en) 2022-10-09 2022-10-09 Dynamic construction method for system service in microkernel operating system

Publications (2)

Publication Number Publication Date
CN115495158A CN115495158A (en) 2022-12-20
CN115495158B true CN115495158B (en) 2023-08-08

Family

ID=84472525

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211226300.2A Active CN115495158B (en) 2022-10-09 2022-10-09 Dynamic construction method for system service in microkernel operating system

Country Status (1)

Country Link
CN (1) CN115495158B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117421056B (en) * 2023-12-18 2024-03-05 美智纵横科技有限责任公司 System loading method and device, storage medium, computer program product and chip

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101697131A (en) * 2009-11-04 2010-04-21 中兴通讯股份有限公司 Method and device for dynamically loading relocatable file
CN101706725A (en) * 2009-11-20 2010-05-12 中兴通讯股份有限公司 Method and system for loading and debugging relocatable program
CN112328319A (en) * 2020-09-30 2021-02-05 北京空间飞行器总体设计部 Satellite-borne APP dynamic loading method supporting RAM file system
CN113641413A (en) * 2021-08-25 2021-11-12 Oppo广东移动通信有限公司 Target model loading and updating method and device, readable medium and electronic equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101697131A (en) * 2009-11-04 2010-04-21 中兴通讯股份有限公司 Method and device for dynamically loading relocatable file
CN101706725A (en) * 2009-11-20 2010-05-12 中兴通讯股份有限公司 Method and system for loading and debugging relocatable program
CN112328319A (en) * 2020-09-30 2021-02-05 北京空间飞行器总体设计部 Satellite-borne APP dynamic loading method supporting RAM file system
CN113641413A (en) * 2021-08-25 2021-11-12 Oppo广东移动通信有限公司 Target model loading and updating method and device, readable medium and electronic equipment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
袁鸿野.基于嵌入式操作***的动态链接器设计与实现.电子科技大学硕士电子期刊.2013,(第2014年第01期期),全文. *

Also Published As

Publication number Publication date
CN115495158A (en) 2022-12-20

Similar Documents

Publication Publication Date Title
US10606634B1 (en) System and method for application isolation
US10212230B1 (en) System and method for application isolation
US7930705B2 (en) Environment for executing legacy applications on a native operating system
US10496602B1 (en) System and method for maintaining mappings between application resources inside and outside isolated environments
US9396047B2 (en) Operating system distributed over heterogeneous platforms
JP4615971B2 (en) Driver specific context for kernel mode shimming
US10019598B2 (en) Dynamic service discovery
JP2006092544A (en) Dynamic link of module in pre-operating system environment
CN115495158B (en) Dynamic construction method for system service in microkernel operating system
CN113986402A (en) Function calling method and device, electronic equipment and storage medium
US7707392B2 (en) Accessing data in inaccessible memory while emulating memory access instruction by executing translated instructions including call to transfer data to accessible memory
US20030074656A1 (en) Program execution apparatus and method, computer program for performing the program execution method, image forming system, and address solution method
US20120005464A1 (en) Start up processing method, information processing apparatus, and computer-readable storage medium storing program
US20060230190A1 (en) Method and apparatus for executing application in system having NAND flash memory
CN111949301A (en) Application program hot updating method and device, computer readable storage medium and computer equipment
KR100727627B1 (en) Method for supporting application using dynamic linking library and system using the method
CN117234622B (en) Multi-language runtime on-demand calling method and system
CN116339920B (en) Information processing method, device, equipment and medium based on cloud platform
WO2024069678A1 (en) Electronic control device
US7743371B1 (en) System and method for dynamically loading object modules
KR20220135891A (en) System and method for operating camping car control platform based on docker container
JP2011076435A (en) Program for device driver
JP2006092173A (en) Information processing system and information processing method
KR20060118278A (en) Synchronous method for operating system and platform

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant