Handling multiple interrupts in a data processing system utilising multiple operating systems

• US 7,448,050 B2
• Filed: 11/17/2003
• Issued: 11/04/2008
• Est. Priority Date: 11/18/2002
• Status: Active Grant

• Current Assignee: Arm Limited (SoftBank Group Corp.)
• Original Assignee: Arm Limited (SoftBank Group Corp.)
• Inventors: Symes, Dominic Hugo, Orion, Luc, Chaussade, Nicolas, Watt, Simon Charles, Belnet, Lionel, Brochier, Stephane Eric Sebastien, Dornan, Christopher Bentley, Nonweiler, Michael Robert
• Primary Examiner(s): Zhen; Li B.
• Assistant Examiner(s): Seye; Abdou K
• Application Number:
  US10/714,484
• Publication Number:
  US 20040153593A1
• Time in Patent Office: 1,814 Days
• Field of Search: 719/319, 710/26, 710/200, 711/163, 711/200, 718/103
• US Class Current: 719/319
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 21/6281 at program execution time, where the protection is within the operating system
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/4812 by interrupt, e.g. masked
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system

Abstract

In a data processing system using multiple operating systems, an interrupt which itself may be interrupted by a subsequent interrupt which will be serviced in a different operating system, guards itself against being overlooked when that subsequent interrupt has been handled by starting a stub interrupt handling routine in that other operating system before executing the main handling routine in the originating operating system. Thus, the stub interrupt handling routine will be recognised in the other operating system irrespective of other interrupt events which may occur and accordingly the interrupted interrupt handling may be restarted.

Claims

1. A method of processing data with execution of data processing operations under control of either a first operating system or a second operating system, said method comprising the steps of:

receiving an interrupt for suspending execution of data processing operations;

in response to said interrupt, starting a stub interrupt handling routine executing under control of said first operating system;

as commanded by said stub interrupt handling routine, suspending execution of said stub interrupt handling routine and starting a main interrupt handling routine executing under control of said second operating system;

executing said main interrupt handling routine under control of said second operating system to handle said interrupt;

as commanded by said main interrupt handling routine, resuming execution of said stub interrupt handling routine under control of said first operating system; and

as commanded by said stub interrupt handling routine, resuming said data processing operations, wherein

if said main interrupt handling routine is interrupted by a further interrupt which when handled leaves processing under control of said first operating system, then said first operating system detects that said stub interrupt handling routine has been interrupted and resumes said stub interrupt handling so as to trigger resumption of said main interrupt handling routine.

2. A method as claimed in claim 1, wherein when said interrupt occurs while data processing under said first operating system is suspended following data processing operations under control of said first operating system executing a call instruction calling data processing operations under control of said second operating system, said stub interrupt handling routine appears to said first operating system to be handling an interrupt which occurred during execution of said call instruction.

3. A method as claimed in claim 2, wherein said resumption of data processing operations as commanded by said stub interrupt handling routine is performed by re-executing said call instruction.

4. A method as claimed in claim 2, wherein said call instruction is a software interrupt instruction.

5. A method as claimed in claim 1, wherein said second operating system executes in a secure domain and said first operating system executes in a non-secure domain, wherein a data processing operations executing in said secure domain have access to secure data which is not accessible to a data processing operating executing in said non-secure domain.

6. A method as claimed in claim 1, wherein switches between processing under control of said first operating system and processing under control of said second operating system take place via a monitor mode of operation executing a monitor mode program.

13. A computer program product stored on a computer-readable storage medium, said computer program product arranged to control a data processing apparatus in accordance with a method as claimed in claim 1.

7. Apparatus having a processor for processing data with execution of data processing operations under control of either a first operating system or a second operating system, said apparatus comprising:

receiving circuitry for receiving an interrupt to suspend execution of data processing operations;

handling circuitry for starting a stub interrupt handling routine executing under control of said first operating system in response to said interrupt;

suspending circuitry for suspending execution of said stub interrupt handling routine as commanded by said stub interrupt handling routine, and starting a main interrupt handling routine executing under control of said second operating system;

execution circuitry for executing said main interrupt handling routine under control of said second operating system to handle said interrupt;

resumption circuitry for resuming execution of said stub interrupt handling routine under control of said first operating system as commanded by said main interrupt handling routine; and

resumption circuitry for resuming said data processing operations, as commanded by said stub interrupt handling routine, wherein

if said main interrupt handling routine is interrupted by a further interrupt which when handled leaves processing under control of said first operating system, then said first operating system detects that said stub interrupt handling routine has been interrupted and resumes said stub interrupt handling so as to trigger resumption of said main interrupt handling routine.

8. Apparatus as claimed in claim 7, wherein when said interrupt occurs while data processing under said first operating system is suspended following data processing operations under control of said first operating system executing a call instruction calling data processing operations under control of said second operating system, said stub interrupt handling routine appears to said first operating system to be handling an interrupt which occurred during execution of said call instruction.

9. Apparatus as claimed in claim 8, wherein said resumption of data processing operations as commanded by said stub interrupt handling routine started by said handling circuitry is performed by re-executing said call instruction.

10. Apparatus as claimed in claim 8, wherein said call instruction is a software interrupt instruction.

11. Apparatus as claimed in claim 7, wherein said second operating system executes in a secure domain and said first operating system executes in a non-secure domain, wherein a data processing operations executing in said secure domain have access to secure data which is not accessible to a data processing operating executing in said non-secure domain.

12. Apparatus as claimed in claim 7, wherein switches between processing under control of said first operating system and processing under control of said second operating system take place via a monitor mode of operation executing a monitor mode program.