Interrupt service implementation method of partition operating system in tri-state system

Abstract

The invention belongs to the technical field of computer system software, and particularly relates to an interrupt service implementation method of a partition operating system in a three-state system, which comprises the following steps of: defining the name of an interrupt service and a partition number to which the interrupt service belongs in a configuration record of the three-state system, and then compiling the configuration record to generate an interrupt service configuration record information packet; after the three-state system is started, sharing the interrupt service configuration record information packet to partition operating systems of all system states; according to the method, the process can be directly triggered by the external event defined by the configuration record under the tri-state partition operating system, and the flexibility of system application is improved.

Description

Technical Field

[0001] The invention belongs to the technical field of computer system software, and in particular relates to an interrupt service implementation method of a partition operating system in a three-state system. Background Art

[0002] With the development of integrated and modular systems, operating systems with multi-partition structures that comply with ARINC653 are becoming more and more widely used, and the partition applications running on them are becoming more and more complex. There is an urgent need for an interrupt service implementation method for partitioned operating systems under three service states. Summary of the invention

[0003] In view of this, the present invention provides an interrupt service implementation method for a partitioned operating system in a three-state system. A series of interrupt service method logics in the three-state are given to the user-state process, which can enable the process to be directly triggered by a defined external event. The present invention implements a set of interrupt services to solve this problem.

[0004] The technical solution of the present invention is:

[0005] A method for implementing interrupt services of a partition operating system in a three-state system, wherein the three-state system complies with the ARINC653 standard; the three-state system includes a core operating system in a hypervisor state, a partition operating system in a system state, and a partition application in a user state;

[0006] The method comprises the following steps:

[0007] S101: defining the name of the interrupt service and the partition number to which it belongs in the configuration record of the three-state system, and then compiling the configuration record to generate an interrupt service configuration record information package;

[0008] S102: After the three-state system is started, the interrupt service configuration record information package is shared with all partition operating systems in the system state;

[0009] S103: In the user-state partition application, the interrupt service creation interface is called to create the interrupt service, and the validity of the parameters passed in by the interrupt service creation interface is examined. If valid, the user-state partition application performs a system call to enter the system state to check whether the interrupt service is legally configured, and then the passed-in parameters are verified with the interrupt service configuration record information packet, and then the interrupt service status is cleared and the waiting queue parameters are initialized.

[0010] Furthermore, after S103, the step further includes:

[0011] In the user-mode partition application, the interrupt service waiting interface is called to wait for the interrupt service, and the validity of the input parameters of the interrupt service waiting interface is examined. If valid, the user-mode partition application performs a system call to enter the system mode and then checks whether the interrupt service occupies the mutex; then the interrupt status is confirmed based on the name of the interrupt service and the partition number to which it belongs. If there is an interrupt notification sent from the Hypervisor mode, the waiting is successful and returned. If not, the interrupt service call is placed in the waiting queue according to the set timeout period and the process is suspended;

[0012] Furthermore, after S103, the step further includes:

[0013] In the core operating system, the interrupt service sending interface is called to send interrupt services to a specific partition. The validity of the parameters passed in by the interrupt service sending interface is reviewed according to the interrupt service information of the interrupt service configuration record information package. If valid, an interrupt notification is sent to the specified partition and then the interrupt bitmap information is updated.

[0014] Furthermore, after the interrupt bitmap information is updated, the partition operating system receives the interrupt service signal sent by the core operating system for processing, and obtains the interrupt service number from the incoming interrupt bitmap information; determines whether the interrupt service number matches the interrupt service of this partition, and returns if there is no match. If there is a match, the interrupt status is set. If there is a waiting process in the waiting queue of this interrupt service, the process is dequeued and the process is set to the ready state.

[0015] Furthermore, the interrupt bitmap information is protected by using 64-bit atomic read / write operations to ensure data consistency among multiple cores.

[0016] Furthermore, the implementation method supports the simultaneous execution of multiple interrupt services.

[0017] Beneficial effects of the present invention:

[0018] The present invention can enable a process to be directly triggered by an external event defined by a configuration record under a three-state partition operating system, thereby improving the flexibility of system application. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0020] Figure 1 The overall architecture diagram of the service implementation method. DETAILED DESCRIPTION

[0021] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0022] The following describes the embodiments of the present disclosure through specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.

[0023] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein can be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects described herein can be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein can be used to implement this device and / or practice this method.

[0024] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The illustrations only show components related to the present disclosure rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0025] Additionally, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects described may be practiced without these specific details.

[0026] In one embodiment of the present invention, a method for implementing interrupt service of a partition operating system in a three-state system is provided. Figure 1 , the three-state system complies with the ARINC653 standard; the three-state system includes a core operating system in a hypervisor state, a partition operating system in a system state, and a partition application in a user state;

[0027] The method comprises the following steps:

[0028] S101: defining the name of the interrupt service and the partition number to which it belongs in the configuration record of the three-state system, and then compiling the configuration record to generate an interrupt service configuration record information package;

[0029] S102: After the three-state system is started, the interrupt service configuration record information package is shared with all partition operating systems in the system state;

[0030] S103: In the user-state partition application, the interrupt service creation interface is called to create the interrupt service, and the validity of the parameters passed in by the interrupt service creation interface is examined. If valid, the user-state partition application performs a system call to enter the system state to check whether the interrupt service is legally configured, and then the passed-in parameters are verified with the interrupt service configuration record information packet, and then the interrupt service status is cleared and the waiting queue parameters are initialized.

[0031] In this embodiment, after S103, the following steps are further performed:

[0032] In the user-mode partition application, the interrupt service waiting interface is called to wait for the interrupt service, and the validity of the input parameters of the interrupt service waiting interface is examined. If valid, the user-mode partition application performs a system call to enter the system mode and then checks whether the interrupt service occupies the mutex; then the interrupt status is confirmed based on the name of the interrupt service and the partition number to which it belongs. If there is an interrupt notification sent from the Hypervisor mode, the waiting is successful and returned. If not, the interrupt service call is placed in the waiting queue according to the set timeout period and the process is suspended;

[0033] In this embodiment, after S103, the following steps are further performed:

[0034] In the core operating system, the interrupt service sending interface is called to send interrupt services to a specific partition. The validity of the parameters passed in by the interrupt service sending interface is reviewed according to the interrupt service information of the interrupt service configuration record information package. If valid, an interrupt notification is sent to the specified partition and then the interrupt bitmap information is updated.

[0035] In this embodiment, after the interrupt bitmap information is updated, the partition operating system receives the interrupt service signal sent by the core operating system for processing, and obtains the interrupt service number from the incoming interrupt bitmap information; determines whether the interrupt service number matches the interrupt service of this partition, and returns if there is no match. If there is a match, the interrupt status is set. If there is a waiting process in the waiting queue of this interrupt service, the process is dequeued and the process is set to the ready state.

[0036] In this embodiment, the interrupt bitmap information is protected by using 64-bit atomic read / write operations to ensure data consistency among multiple cores.

[0037] In this embodiment, the implementation method supports the simultaneous execution of multiple interrupt services.

[0038] Beneficial effects of the present invention:

[0039] The present invention can enable a process to be directly triggered by an external event defined by a configuration record under a three-state partition operating system, thereby improving the flexibility of system application.

[0040] The specific working steps of the interrupt service of the partition operating system in the three-state system of this embodiment are as follows:

[0041] 1) Define the name of the interrupt service and the partition number to which it belongs in the configuration record, and then compile the configuration record to generate an interrupt service configuration record information package.

[0042] 2) After the system is started, the interrupt service configuration record information is shared with the system states of all partitions.

[0043] 3) In the user-mode partition, call the interrupt service creation interface to create the interrupt service and examine the validity of the parameters passed in; then make a system call to check whether the interrupt service is legally configured, by verifying it with the interrupt service configuration record information in 2); then clear the interrupt service status and initialize the waiting queue parameters.

[0044] 4) In the user-mode partition, the interrupt service waiting interface is called to wait for the interrupt service and the validity of the incoming parameters is examined; after making a system call, a check is made to see whether the interrupt service occupies the mutex; the interrupt status is then confirmed. If there is an interrupt sent from the Hypervisor state, the process is waited for and returns successfully. If not, the process is placed in the waiting queue and the task is suspended according to the set timeout period.

[0045] 5) In the Hypervisor state, the interrupt service sending interface is called to send the interrupt service to the specific partition, and the validity of the input parameters is reviewed according to the configuration record of the interrupt service information; the updated virtual interrupt bitmap information is sent to the specified partition.

[0046] 6) Receive the interrupt service signal sent by the Hypervisor state in the system state for processing, and obtain the interrupt service number from the incoming virtual interrupt bitmap information; determine whether the interrupt service number matches the interrupt service of this partition, and return if there is no match; then set the interrupt status, and if there is a waiting task in the waiting queue of this interrupt service, dequeue the task.

[0047] 7) Multiple interrupt services can be executed at the same time, and the execution method of interrupt services in other partitions is similar to processes 3) to 6).

[0048] The above is only a specific implementation of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present disclosure should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A method for implementing interrupt service of a partition operating system in a three-state system, wherein the three-state system complies with the ARINC653 standard; the three-state system includes a core operating system in a hypervisor state, a partition operating system in a system state, and a partition application in a user state; It is characterized in that The method comprises the following steps: S101: defining the name of the interrupt service and the partition number to which it belongs in the configuration record of the three-state system, and then compiling the configuration record to generate an interrupt service configuration record information package; S102: After the three-state system is started, the interrupt service configuration record information package is shared with all partition operating systems in the system state; S103: In the user-state partition application, the interrupt service creation interface is called to create the interrupt service, and the validity of the parameters passed in by the interrupt service creation interface is examined. If valid, the user-state partition application performs a system call to enter the system state to check whether the interrupt service is legally configured, and then the passed-in parameters are verified with the interrupt service configuration record information packet, and then the interrupt service status is cleared and the waiting queue parameters are initialized.

2. The interrupt service implementation method of the partition operating system in the three-state system according to claim 1, characterized in that: After S103, the following steps are also included: In the user-state partition application, the interrupt service waiting interface is called to wait for the interrupt service, and the validity of the input parameters of the interrupt service waiting interface is examined. If valid, the user-state partition application performs a system call to enter the system state to check whether the interrupt service occupies the mutex; then the interrupt status is confirmed based on the name of the interrupt service and the partition number to which it belongs. If there is an interrupt notification sent from the Hypervisor state, the wait is successfully returned. If not, the call to the interrupt service is placed in the waiting queue and the process is suspended according to the set timeout period.

3. The interrupt service implementation method of the partition operating system in the three-state system according to claim 2, characterized in that: After S103, the following steps are also included: In the core operating system, the interrupt service sending interface is called to send interrupt services to a specific partition. The validity of the parameters passed in by the interrupt service sending interface is reviewed according to the interrupt service information of the interrupt service configuration record information package. If valid, an interrupt notification is sent to the specified partition and then the interrupt bitmap information is updated.

4. The method for implementing interrupt service of a partition operating system in a three-state system according to claim 3, characterized in that: After the interrupt bitmap information is updated, the partition operating system receives the interrupt service signal sent by the core operating system for processing, and obtains the interrupt service number from the incoming interrupt bitmap information; determines whether the interrupt service number matches the interrupt service of this partition, and returns if there is no match. If there is a match, the interrupt status is set. If there is a waiting process in the waiting queue of this interrupt service, the process is dequeued and the process is set to the ready state.

5. The method for implementing interrupt service of a partition operating system in a three-state system according to claim 4, characterized in that: The interrupt bitmap information is protected by using 64-bit atomic read / write operations to ensure data consistency between multiple cores.

6. The method for implementing interrupt service of a partition operating system in a three-state system according to claim 5, characterized in that: The implementation method supports the simultaneous execution of multiple interrupt services.

Images