Processor Core Secure Execution Without Dedicated Core Reservation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing multi-threaded processors face performance degradation when permanently reserving a core for secure work, as it reduces overall processor performance and does not scale with varying workloads requiring secure environments.
Innovation Solution
A method and system for operating a secure code segment on a processor core, involving exclusive secure execution, uninterruptable execution, and wiping architectural and non-architectural states to ensure undisturbed processing, with hardware-controlled state management and restoration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a core is permanently reserved for secure work, then security isolation is improved, but overall processor performance deteriorates
Solution Approach 1:
The system dynamically switches the processor core between secure execution mode and normal execution mode based on workload requirements. Instead of permanently reserving a core for secure work, the same core can be allocated to secure code segments when needed and released for general-purpose use when not needed, making the resource allocation flexible and adaptive to varying security requirements.
Solution Approach 2:
The system changes the execution state parameters of the processor core by setting specific flags (such as the Secure Flag) to transition between secure and normal execution modes. This allows the core to operate in different security contexts without permanent structural changes, enabling efficient resource utilization while maintaining security isolation when required.
2Reliability
If a core is permanently reserved for secure work, then security isolation is improved, but scalability deteriorates
Solution Approach 1:
The processor core is designed to serve multiple functions by supporting both secure execution mode and normal execution mode. The same physical core can be universally used for different purposes depending on the security requirements of the workload, eliminating the need for dedicated secure cores and enabling the system to scale security capabilities without proportionally increasing hardware resources.
Solution Approach 2:
The system dynamically adapts the core's function based on runtime requirements. When secure code segments need to execute, the core transitions to secure mode; when they don't, the core returns to normal mode. This dynamic adaptability allows the system to scale security support flexibly without being constrained by fixed hardware allocations.
3Productivity
If threads share the same physical core, then resource utilization is improved, but security isolation deteriorates
Solution Approach 1:
The system applies different security qualities to different code segments executing on the same physical core. By identifying secure code segments and transitioning the core to secure execution mode when these segments run, the system ensures that security-critical operations receive enhanced protection while non-critical operations can share the core without compromising overall security isolation.
Solution Approach 2:
The security isolation level dynamically changes based on the type of code being executed. When secure code segments are detected, the core transitions to a more isolated secure mode; when running non-secure code, it operates in normal mode. This dynamic adjustment allows threads to share the core for resource efficiency while maintaining security isolation when required by the workload.
Data Source
AI summary
A computer-implemented method, a computer system and a computer program product operate a secure code segment on a processor core of a processing unit, wherein the processing unit is configured with at least one processor core. The method comprises requesting exclusive secure execution of a secure code segment of the program code on the at least one processor core. The method also comprises setting the at least one processor core to exclusive secure execution for the secure code segment. The method further comprises executing the secure code segment on the at least one processor core uninterruptably. In addition, the method comprises wiping an architected state and a non-architected state of a physical processor core from the at least one processor core. Lastly, the method comprises setting the at least one processor core to the first execution mode for program code on the at least one processor core.