Lock free streaming of executable code data

Abstract

A disassembler receives instructions and disassembles them into a plurality of separate opcodes. The disassembler creates a table identifying boundaries between each opcode. Each opcode is written to memory in an opcode-by-opcode manner by atomically writing standard blocks of memory. Debug break point opcodes are appended to opcode to create a full block of memory when needed. The block of memory may be thirty-two or sixty-four bits long, for example. Long opcodes may overlap two or more memory blocks. Debug break point opcodes may be appended to a second portion of the long opcode to create a full block of memory. A stream fault interceptor identifies when a requested data page is not available and retrieving the data page.

Description

Background technique [0001] A race condition occurs when commands to read and write data are received at the same time. This can also occur, for example, when a thread is executing an executable data packet from memory while a write thread is delivering data to memory. The result could be computer crashes, program shutdowns, read / write errors, or other problems. In one solution, the executing thread can be suspended while waiting for the writing thread to provide data. However, hanging a thread can cause performance problems for the associated process. For example, there can be tens or hundreds of threads running for a process, and only one or a few threads access the data, but every time a stream failure occurs, all threads must be suspended to wait for data delivery. Contents of the invention [0002] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not inten...

AI Technical Summary

Problems solved by technology

However, hanging a thread can cause p...

Images