Apparatus and methods for recordation of device history across multiple software emulations
First Claim
1. A method for modifying a size of a virtualized memory associated with an emulation program, the method comprising:
- loading the emulation program that maintains;
first usage information associated the virtualized memory, andsecond usage information associated with an underlying physical memory to which the virtualized memory corresponds, wherein the second usage information corresponds to (i) the emulation program, and (ii) at least one different emulation program; and
processing an update that involves modifying the size of the virtualized memory associated with the emulation program, wherein, when the size is increased, aspects of the second usage information are populated into corresponding aspects of the first usage information to account for the updated size of the virtualized memory.
0 Assignments
0 Petitions
Accused Products
Abstract
Apparatus and method for maintaining hardware history profiles for a software-based emulator. In one embodiment, the disclosed software-based emulator monitors the history of the actual hardware device in a secondary device history, the history of the emulated hardware is presented within a primary device history. However, the primary device history is linked to the secondary device history, and receives the device wear history therefrom. In another aspect of the present invention, wear-leveling strategies are disclosed for handling various update sizes. Unlike existing solutions which are optimized for a single SIM that receives small data updates; various embodiments of the present invention are suitable for handling varying data sizes.
34 Citations
20 Claims
-
1. A method for modifying a size of a virtualized memory associated with an emulation program, the method comprising:
-
loading the emulation program that maintains; first usage information associated the virtualized memory, and second usage information associated with an underlying physical memory to which the virtualized memory corresponds, wherein the second usage information corresponds to (i) the emulation program, and (ii) at least one different emulation program; and processing an update that involves modifying the size of the virtualized memory associated with the emulation program, wherein, when the size is increased, aspects of the second usage information are populated into corresponding aspects of the first usage information to account for the updated size of the virtualized memory. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A non-transitory computer readable storage medium configured to store instructions that, when executed by a processor included in a computing device, cause the computing device to modify a size of a virtualized memory associated with an emulation program, by carrying out steps that include:
-
loading the emulation program that maintains; first usage information associated the virtualized memory, and second usage information associated with an underlying physical memory to which the virtualized memory corresponds, wherein the second usage information corresponds to (i) the emulation program, and (ii) at least one different emulation program; and processing an update that involves modifying the size of the virtualized memory associated with the emulation program, wherein, when the size is increased, aspects of the second usage information are populated into corresponding aspects of the first usage information to account for the updated size of the virtualized memory. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computing device configured to modify a size of a virtualized memory associated with an emulation program, the computing device comprising:
a processor configured to cause the computing device to carry out steps that include; loading the emulation program that maintains; first usage information associated the virtualized memory, and second usage information associated with an underlying physical memory to which the virtualized memory corresponds, wherein the second usage information corresponds to (i) the emulation program, and (ii) at least one different emulation program; and processing an update that involves modifying the size of the virtualized memory associated with the emulation program, wherein, when the size is increased, aspects of the second usage information are populated into corresponding aspects of the first usage information to account for the updated size of the virtualized memory. - View Dependent Claims (16, 17, 18, 19, 20)
Specification