Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.
In order to illustrate the technical scheme of the invention, the following description is made by specific examples.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
In addition, in the description of the present application, the terms "first," "second," "third," etc. are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance.
Embodiment one:
Fig. 1 shows a flowchart of a first Linux system device starting method according to an embodiment of the present application, which is described in detail below:
in S101, a start instruction is received, and a quick start identifier is acquired.
And receiving a starting instruction through a target physical key or a target remote control signal, and triggering the Linux system equipment to start executing the starting action. And after receiving the starting instruction, automatically acquiring the quick starting identification. The quick start identifier is an identifier of a target storage unit stored in Linux system equipment in advance, wherein the target storage unit can be stored when any one of the target storage units is powered off, and a storage unit which can be accessed by both a Bootloader and a Linux system kernel is started, for example, a partition such as u-boot, kernel, root, user, vendor in a Linux file system can be used as the target storage unit for storing the quick start identifier. Preferably, the quick start identifier is stored in a vendor partition, and since u-boot, kernel, root, user and other partitions store a large amount of necessary information for system operation, storing the quick start identifier in these partitions may risk covering important operation information of the system, while the vendor partition is a partition for storing basic information (including a device self-setting identifier, a serial number, a model number and the like) of the device, the partition usually reserves enough storage space for a user, so that storing the quick start identifier in the vendor partition can avoid covering other important information of the system.
Specifically, after receiving a starting instruction, automatically reading a target storage unit according to a preset program to obtain a quick starting identifier, wherein the preset program is a code segment written in a boot program in advance and is used for indicating a Linux operation kernel to automatically access data of the target storage unit when the starting is triggered each time.
Optionally, after receiving the start instruction, the method further includes:
if the current starting is detected to be the first starting, the Linux system equipment is directly started in a normal starting mode, wherein the normal starting mode is at least a starting mode comprising loading, decompressing a kernel image file and initializing a process.
If the quick start identification cannot be obtained currently or the Swap partition data is detected to be empty, the current start is judged to be the first start, and the start of the Linux system equipment is completed directly in the normal start mode. The normal starting mode at least comprises loading and decompressing the kernel image file and various initialization processes. Specifically, the normal start-up mode may include the steps of:
a1: the hardware equipment is initialized, including self-checking of various hardware equipment and acquisition of hard disk information.
A2: and starting the loading Bootloader to load the Kernel image file OS Kernel and decompressing.
A3: and executing an init process, and acquiring default running level information run-level.
A4: executing/etc/rc.d/rc.sysinit file, preparing operating system environment (such as information of network, time zone, etc.);
A5: and loading the kernel peripheral module and starting the kernel peripheral module.
A6: executing the service script corresponding to runlevel and starting the service process.
A7: user-defined bootstrap/etc/rc.d/rc.local are performed.
A8: executing/bin/logic program, waiting for user to log in, and completing starting of Linux system equipment.
Optionally, after the Linux system device is started, a preset program can be written, the quick start identifier is stored in the target storage unit, and meanwhile, the contents of the DDR and CPU registers are stored in the Swap partition when the Linux system device is shut down, so that the target storage unit can be automatically accessed to acquire the quick start identifier when the Linux system device is started next time.
In S102, if the quick start identifier is the first identifier value, the Swap partition data is read, and the device start is completed in a quick start mode, where the Swap partition data is the content of the DDR and CPU registers stored before the last shutdown.
The quick start identifier is specifically a first identifier value or a second identifier value, and the first identifier value can be represented by characters such as "true" or "yes" or "1", and the like, and is used for indicating that the expected start mode started at this time is a quick start mode; the second identification value may be represented by a character such as "false" or "no" or "0" for indicating that the desired start-up mode for this start-up is a non-fast start-up mode, i.e. a normal start-up mode.
When the first identification value of the current quick start identification bit is detected, the expected start mode of the start is indicated to be the quick start mode, at the moment, the data of the Swap partition in the Linux file system is read, and the equipment start is completed in the quick start mode. Specifically, the fast start mode is a mode of reading data of the Swap partition into a Linux double data rate synchronous dynamic random access memory (Double Data Rate Synchronous Dynamic Random Access Memory, DDR) and a CPU register to finish the fast start of the Linux equipment. The Swap partition data read during starting is the content in the DDR and the CPU which are automatically stored before the last shutdown and power-off, and the content comprises the context information of all running processes of the system before the last shutdown.
The program running process of the Linux system device is specifically a process of loading binary codes and data corresponding to the program into the DDR for the CPU to call, so that the DDR and the contents in the CPU stored in the Swap partition before the last shutdown contain all necessary running process contents capable of enabling the Linux system device to work normally, the data of the Swap partition is read into the DDR and the CPU when the Linux system device is started, the running state of the Linux system device before the last shutdown can be quickly recovered, and the quick start of the Linux system device is completed.
Optionally, after the step S101, the method further includes:
And if the quick start identifier is a second identifier value, starting the Linux system equipment in a normal start mode, wherein the normal start mode is a start mode at least comprising loading, decompressing the kernel image file and initializing a flow.
When the obtained quick start mark is the second mark value, the expected start mode of the start is the normal start mode, at the moment, the process of starting to execute the normal start mode is triggered, and the Linux system equipment is started. The normal startup mode is a startup mode at least comprising loading and decompressing the kernel image file and various initialization processes, and the specific startup process can be seen from the steps A1 to A8.
Optionally, after the Linux system device is started in the normal start mode if the fast start identifier is the second identifier value, the method further includes:
If the normal starting mode fails to start, the Swap partition data is read, and the equipment is started in the fast starting mode.
In the last working and running process of the Linux system device, the image file of the system kernel or other starting files may be illegally changed due to some illegal operations, so that the situation that the system operation kernel cannot execute or execute errors or system crashes may exist when the device is started in the normal starting mode at this time, and the normal starting mode fails to start. At this time, the Swap partition data is read, and the system running state of the device before the last shutdown is directly restored, so that the illegal execution of the kernel image file or other starting files is avoided, and the device starting is completed in a quick starting mode.
In the embodiment of the invention, the contents of the DDR and CPU registers stored before the last shutdown and stored in the Swap partition can be automatically read according to the quick start identifier, so that the state of the device before the last shutdown is immediately restored to finish the device start without loading the decompressed kernel image file and other initialization processes, thereby greatly shortening the start time of the Linux system device and improving the start efficiency of the Linux system device.
Embodiment two:
fig. 2 shows a flowchart of a second Linux system device starting method according to an embodiment of the present application, which is described in detail below:
in S201, a start instruction is received, and a quick start identifier is acquired.
In this embodiment, S201 is the same as S101 in the previous embodiment, and please refer to the description related to S101 in the previous embodiment, which is not repeated here.
In S202, if the quick start identifier is the first identifier value, the Swap partition data is read, and the device start is completed in a quick start mode, where the Swap partition data is the content of the DDR and CPU registers stored before the last shutdown.
In this embodiment, S202 is the same as S102 in the previous embodiment, and detailed descriptions of S102 in the previous embodiment are omitted here.
Optionally, after the step S202, the method further includes:
and receiving a setting instruction of a user and setting the quick start identifier.
And receiving a setting instruction of a user through input equipment such as physical keys, a mouse, a keyboard and the like or through a mode of receiving touch gestures on a screen or a mode of receiving remote control signals and the like, wherein the setting instruction is used for setting an identification value of a quick start identification. And setting the quick start identifier as a first identifier value or a second identifier value according to the setting instruction so as to indicate that the device start is finished according to the quick start mode or the normal start mode when the Linux system device is started next time.
In S203, if a shutdown instruction is received, the contents of the current DDR and CPU registers are stored in the Swap partition, and shutdown is performed.
And starting the Linux system equipment and keeping the Linux system equipment in a working running state. In the working operation process, if a shutdown instruction is received, for example, if a preset shutdown physical key is detected to be pressed or a shutdown icon is detected to be clicked, the contents of the current DDR and CPU registers are stored into the Swap partition, and the contents of the DDR and CPU registers comprise process context information of the system operation, for example, the state of a process, the contents in a stack and the like. After the storage is finished, the shutdown power-off operation is executed, so that the system running state can be quickly recovered according to the Swap partition data when the Linux system equipment is started again. Specifically, the preset program may be set so that the action of storing the contents of the current DDR and CPU registers to the Swap partition is automatically performed after the shutdown instruction is received.
Optionally, if the shutdown instruction is received, storing contents of the current DDR and CPU registers to the Swap partition, and shutting down the processor includes:
if a shutdown instruction is received, all the ordinary user processes are ended, and resources occupied by the ordinary user processes are released;
Storing the contents of the current DDR and CPU registers into the Swap partition, and shutting down.
In the Linux system, the system comprises three user types of a common user, a super user and a system user, wherein the common user cannot rewrite system key files (such as kernel mirror files, necessary drive files and other necessary files for normal operation of the system), so that the operation of the common user process is a non-key file, namely the common user process is not a necessary process in the system operation.
Because the ordinary user process is not an essential process when the system runs, if a shutdown instruction is received, all ordinary user processes are ended, resources occupied by the ordinary user processes are released, and only the superuser with root rights and the system key process corresponding to the system user are reserved, so that the system resources can be saved as much as possible on the premise of retaining essential information.
After all the common user processes are terminated, only the context information of the key processes of the system, including the key processes of the Linux system, such as init processes, ksoftirqd processes, events processes and the like, and the root daemon and the like of the device customization, are left in the content of the current DDR and CPU registers. And storing the contents of the current DDR and CPU registers into the Swap partition, and executing shutdown and outage operation so that the system running state can be quickly restored according to the data of the Swap partition when the Linux system equipment is started again.
Optionally, if the shutdown instruction is received, storing contents of the current DDR and CPU registers to the Swap partition, and shutting down the processor includes:
If a shutdown instruction is received, detecting whether a key file of the system is changed or not;
if the system key file is changed, setting the quick start identifier as a second identifier value;
Storing the contents of the current DDR and CPU registers into the Swap partition, and shutting down.
If a shutdown instruction is received, detecting whether the current system key file is changed, wherein the system key file comprises a kernel mirror image file in a disk, a loaded module driving file and executable files of all system key processes. Specifically, whether the key file of the system is changed can be judged through Inotify mechanisms or according to the running time of the process and the modification time of the file.
If the system key files are changed, the context information of the system key process of the current DDR and CPU register is not the latest system key information, and the next time the equipment is started, the system key files are needed to be reloaded, executed and initialized, so that the system operates according to the latest system key information. At this time, the quick start identifier is set to a second identifier value to instruct the Linux system device to start in a normal start mode next time, so that the latest executable program is used for next start-up, and the latest key process of the system is operated.
Although the contents of the current DDR and CPU registers are not the latest system key information, the contents of the DDR and CPU registers are still stored in the Swap partition and then shut down, so that when the equipment cannot be started normally due to the error of the changed system key file in the next equipment start-up, the old system key process can be restored according to the Swap partition data, and the equipment start-up can be completed in a quick start-up mode.
In the embodiment of the invention, the DDR and the CPU register are stored in the Swap partition before the Linux system device is shut down, so that the running state of the system can be automatically and quickly restored through the data of the Swap partition when the Linux system device is started next time, the Linux system device can be ensured to be started in a quick starting mode next time, and the starting efficiency of the Linux system device is improved.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
Embodiment III:
fig. 3 shows a schematic structural diagram of a Linux system device starting apparatus according to an embodiment of the present application, and for convenience of explanation, only parts related to the embodiment of the present application are shown:
The Linux system equipment starting device comprises: a quick start identifier acquisition unit 31, a quick start unit 32. Wherein:
the quick start identifier obtaining unit 31 is configured to receive a start instruction and obtain a quick start identifier.
And receiving a starting instruction through a target physical key or a target remote control signal, and triggering the Linux system equipment to start executing the starting action. And after receiving the starting instruction, automatically acquiring the quick starting identification. The quick start identifier is an identifier of a target storage unit stored in Linux system equipment in advance, wherein the target storage unit can be stored when any one of the target storage units is powered off, and a storage unit which can be accessed by both a Bootloader and a Linux system kernel is started, for example, a partition such as u-boot, kernel, root, user, vendor in a Linux file system can be used as the target storage unit for storing the quick start identifier. Preferably, the quick start identifier is stored in a vendor partition, and since u-boot, kernel, root, user and other partitions store a large amount of necessary information for system operation, storing the quick start identifier in these partitions may risk covering important operation information of the system, while the vendor partition is a partition for storing basic information (including a device self-setting identifier, a serial number, a model number and the like) of the device, the partition usually reserves enough storage space for a user, so that storing the quick start identifier in the vendor partition can avoid covering other important information of the system.
Specifically, after receiving a starting instruction, automatically reading a target storage unit according to a preset program to obtain a quick starting identifier, wherein the preset program is a code segment written in a boot program in advance and is used for indicating a Linux operation kernel to automatically access data of the target storage unit when the starting is triggered each time.
Optionally, the Linux system device starting apparatus further includes:
And the first starting unit is used for directly completing the starting of the Linux system equipment in a normal starting mode if the current first starting is detected, wherein the normal starting mode is at least a starting mode comprising loading, decompressing the kernel image file and initializing the process.
And the quick start unit 32 is configured to read the Swap partition data if the quick start identifier is the first identifier value, and complete the device start in a quick start mode, where the Swap partition data is the contents of the DDR and CPU registers stored before the last shutdown.
The quick start identifier is specifically a first identifier value or a second identifier value, and the first identifier value can be represented by characters such as "true" or "yes" or "1", and the like, and is used for indicating that the expected start mode started at this time is a quick start mode; the second identification value may be represented by a character such as "false" or "no" or "0" for indicating that the desired start-up mode for this start-up is a non-fast start-up mode, i.e. a normal start-up mode.
When the first identification value of the current quick start identification bit is detected, the expected start mode of the start is indicated to be the quick start mode, at the moment, the data of the Swap partition in the Linux file system is read, and the equipment start is completed in the quick start mode. Specifically, the fast start mode is a mode of reading data of the Swap partition into a DDR and CPU register of the Linux double data rate synchronous dynamic random access memory to finish the fast start of the Linux equipment. The Swap partition data read during starting is the content in the DDR and the CPU which are automatically stored before the last shutdown and power-off, and the content comprises the context information of all running processes of the system before the last shutdown.
The program running process of the Linux system device is specifically a process of loading binary codes and data corresponding to the program into the DDR for the CPU to call, so that the DDR and the contents in the CPU stored in the Swap partition before the last shutdown contain all necessary running process contents capable of enabling the Linux system device to work normally, the data of the Swap partition is read into the DDR and the CPU when the Linux system device is started, the running state of the Linux system device before the last shutdown can be quickly recovered, and the quick start of the Linux system device is completed.
Optionally, the Linux system device starting apparatus further includes:
And the normal starting unit is used for starting the Linux system equipment in a normal starting mode if the quick starting identifier is a second identifier value, wherein the normal starting mode is a starting mode at least comprising loading, decompressing a kernel image file and initializing a process.
Optionally, the fast boot unit 32 is further configured to read the Swap partition data if the normal boot mode fails to boot, and complete the device boot in the fast boot mode.
Optionally, the Linux system device starting apparatus further includes:
and the setting unit is used for receiving a setting instruction of a user and setting the quick start identifier.
Optionally, the Linux system device starting apparatus further includes:
and the storage unit is used for storing the contents of the current DDR and CPU registers into the Swap partition if a shutdown instruction is received, and shutting down.
Optionally, the storage unit includes a process end module and a first storage module:
The process ending module is used for ending all the ordinary user processes if a shutdown instruction is received, and releasing resources occupied by the ordinary user processes;
And the first storage module is used for storing the contents of the current DDR and CPU registers into the Swap partition and shutting down.
Optionally, the storage unit includes a detection module, a setting module, and a second storage module:
the detection module is used for detecting whether the key file of the system is changed or not if a shutdown instruction is received;
the setting module is used for setting the quick start identifier as a second identifier value if the system key file is changed;
And the second storage module is used for storing the contents of the current DDR and CPU registers into the Swap partition and shutting down.
In the embodiment of the invention, the contents of the DDR and CPU registers stored before the last shutdown and stored in the Swap partition can be automatically read according to the quick start identifier, so that the state of the device before the last shutdown is immediately restored to finish the device start without loading the decompressed kernel image file and other initialization processes, thereby greatly shortening the start time of the Linux system device and improving the start efficiency of the Linux system device.
Embodiment four:
Fig. 4 is a schematic diagram of a terminal device according to an embodiment of the present invention. As shown in fig. 4, the terminal device 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42, such as a Linux system device boot program, stored in said memory 41 and executable on said processor 40. The steps of the above embodiments of the method for booting a Linux system device are implemented when the processor 40 executes the computer program 42, for example, steps S101 to S102 shown in fig. 1. Or the processor 40, when executing the computer program 42, performs the functions of the modules/units of the device embodiments described above, such as the functions of the units 31 to 32 shown in fig. 3.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to complete the present invention. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions for describing the execution of the computer program 42 in the terminal device 4. For example, the computer program 42 may be divided into a quick start identifier acquisition unit, a quick start unit, each unit functioning specifically as follows:
The quick start identifier acquisition unit is used for receiving the start instruction and acquiring the quick start identifier.
And the quick starting unit is used for reading the Swap partition data and finishing equipment starting in a quick starting mode if the quick starting identifier is a first identifier value, wherein the Swap partition data is the content of the DDR and CPU registers stored before the last shutdown.
The terminal device 4 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The terminal device may include, but is not limited to, a processor 40, a memory 41. It will be appreciated by those skilled in the art that fig. 4 is merely an example of the terminal device 4 and does not constitute a limitation of the terminal device 4, and may include more or less components than illustrated, or may combine certain components, or different components, e.g., the terminal device may further include an input-output device, a network access device, a bus, etc.
The processor 40 may be a central processing unit (Central Processing Unit, CPU).
The memory 41 may be an internal storage unit of the terminal device 4, such as a hard disk or a memory of the terminal device 4. The memory 41 may also be an external storage device of the terminal device 4, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD) or the like, which are provided on the terminal device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the terminal device 4. The memory 41 is used for storing the computer program as well as other programs and data required by the terminal device. The memory 41 may also be used for temporarily storing data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other manners. For example, the apparatus/terminal device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present invention may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the computer readable medium contains content that can be appropriately scaled according to the requirements of jurisdictions in which such content is subject to legislation and patent practice, such as in certain jurisdictions in which such content is subject to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.