Difference between revisions of "Glossary"
m (update conAsm links to match uses elsewhere (still red)) | |||
| (23 intermediate revisions by 2 users not shown) | |||
| Line 32: | Line 32: | ||
<div style="font-size: 10pt; font-weight: bold;" id="a">a</div> | <div style="font-size: 10pt; font-weight: bold;" id="a">a</div> | ||
| + | [[genAsm_(code_representation)|Abstract Code]] - general data flow code for the Mill architecture, distribution format<br /> | ||
| + | [[genAsm_(language)|Abstract Assembly]] - general data flow code for the Mill architecture in human readable form, mainly used as compiler output<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="b">b</div> | <div style="font-size: 10pt; font-weight: bold;" id="b">b</div> | ||
| − | [[Belt]] | + | [[Memory#Backless_Memory|Backless Memory]] - allocating memory happens in cache initially and often no DRAM and system bus needs to be involved at all<br /> |
| − | [[Belt#Belt_Position_Data_Format|Belt Position/Belt Location]] | + | [[Belt]] - provides the functionality of general purpose registers<br /> |
| − | [[Bundle]] | + | [[Belt#Belt_Position_Data_Format|Belt Position/Belt Location]] - the read only data source for machine operations<br /> |
| + | [[Block]] - a subsection of an instruction that contains a subset of the operations or data in a defined encoding format.<br /> | ||
| + | [[Encoding#Instructions_and_Operations_and_Bundles|Bundle]] - a collection of instructions that get fetched from memory together<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="c">c</div> | <div style="font-size: 10pt; font-weight: bold;" id="c">c</div> | ||
| + | [[conAsm (code representation)|Concrete Code]] - specialized executable code for a specific Mill processor<br /> | ||
| + | [[conAsm|Concrete Assembly]] - specialized executable code for a specific Mill processor in human readable form, mainly used for testing and in the debugger<br /> | ||
| + | [[Crossbar]] - the interconnecting framework that routes the data sources to the functional units<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="d">d</div> | <div style="font-size: 10pt; font-weight: bold;" id="d">d</div> | ||
| + | [[Decode]] - turning instruction stream bit patters into requests to functional units<br /> | ||
| + | [[Domains]] - operand value types, i.e. different interpretations of bit patterns by operations<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="e">e</div> | <div style="font-size: 10pt; font-weight: bold;" id="e">e</div> | ||
| − | [[EBB]] – | + | [[Encoding#Extended_Basic_Block|EBB]] - extended basic block, a batch or sequence of instructions with one entry point and one or more exit points<br /> |
| − | [[Exit]] | + | [[Encoding]] – the semantic bit patterns representing operations<br /> |
| + | [[Events|Event]] - an asynchronous diversion from normal program flow<br /> | ||
| + | [[Prediction#Exit_Table|Exit]] - a point where the instruction stream can leave the EBB<br /> | ||
| + | [[Prediction#Exit_Table|Exit Table]] - a hardware hash table containing exit point usage for EBBs, used to predict control flow<br /> | ||
| + | [[ExuCore]] - the collection of functional units and facilities serving operations from the exu instruction stream<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="f">f</div> | <div style="font-size: 10pt; font-weight: bold;" id="f">f</div> | ||
| + | |||
| + | [[Events#Faults|Fault]] - an interrupt normal program flow cannot recover from in a meaningful way<br /> | ||
| + | [[Execution#fwr|First Winner Rule]] - only the first successful conditional branch operation in an instruction is taken<br /> | ||
| + | [[FlowCore]] - the collection of functional units and facilities serving operations from the flow instruction stream<br /> | ||
| + | [[Functional Unit|FU, Functional Unit]] - the hardware module that provides the functionality to perform an operation<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="g">g</div> | <div style="font-size: 10pt; font-weight: bold;" id="g">g</div> | ||
| + | [[Ganging]] - combining more than two belt operands in more than one slot to perform a more complex operation<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="h">h</div> | <div style="font-size: 10pt; font-weight: bold;" id="h">h</div> | ||
<div style="font-size: 10pt; font-weight: bold;" id="i">i</div> | <div style="font-size: 10pt; font-weight: bold;" id="i">i</div> | ||
| − | [[Implicit Zero]] - | + | [[Memory#Implicit_Zero_and_Virtual_Zero|Implicit Zero]] - loads from new stack frames are implicitly zero<br /> |
| − | [[Instruction]] | + | [[Events#Interrupts|Interrupt]] - an event that has predefined but configurable handling code in the form of a function<br /> |
| − | [[Instruction Stream]] | + | [[Encoding#Instructions_and_Operations_and_Bundles|Instruction]] - a collection of operations that get executed together<br /> |
| + | [[Encoding#Split_Instruction_Streams|Instruction Stream]] - a sequence of instructions, the Mill has 2 working in parallel<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="j">j</div> | <div style="font-size: 10pt; font-weight: bold;" id="j">j</div> | ||
| Line 64: | Line 84: | ||
<div style="font-size: 10pt; font-weight: bold;" id="m">m</div> | <div style="font-size: 10pt; font-weight: bold;" id="m">m</div> | ||
| − | [[Metadata]] | + | [[Metadata]] - tags attached to belt slots that describe the data in it<br /> |
| + | [[Decode#Morsels|Morsel]] - the amount of bits needed to address all belt locations on a core<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="n">n</div> | <div style="font-size: 10pt; font-weight: bold;" id="n">n</div> | ||
| − | [[None]] | + | [[Metadata#None_and_NaR|None]] - undefined data in a slot that is silently ignored by operations<br /> |
| − | [[NaR]] | + | [[Metadata#None_and_NaR|NaR]] - Not a Result, undefined data that traps when used in certain operations<br /> |
<div style="font-size: 10pt; font-weight: bold;" id="o">o</div> | <div style="font-size: 10pt; font-weight: bold;" id="o">o</div> | ||
| − | [[Operation]] – the most basic semantically defined hardware unit of execution<br /> | + | [[Encoding#Instructions_and_Operations_and_Bundles|Operation]] – the most basic semantically defined hardware unit of execution<br /> |
<div style="font-size: 10pt; font-weight: bold;" id="p">p</div> | <div style="font-size: 10pt; font-weight: bold;" id="p">p</div> | ||
| − | [[Phase]] - sequenced execution of different operations within one instruction<br /> | + | [[Phasing|Phase, Phasing]] - sequenced execution of different operations within one instruction<br /> |
| − | [[PLB]] | + | [[Protection#Protection_Lookaside_Buffer|PLB]] - on chip cache for looking up protection regions for a virtual address<br /> |
| − | [[Portal]] | + | [[Pipeline]] - a logical and physical grouping of functional units sharing infrastructure for sequential step by step processing each cycle, emphasis on the physical aspect<br /> |
| − | [[Protection Region]] | + | [[Pipelining]] - arrangeing operations in the instruction stream in such a way as to maximize functional unit utilization<br /> |
| + | [[Protection#Portals|Portal]] - a gateway between different protection domains or turfs a thread can pass through<br /> | ||
| + | [[Prediction]] - deciding which branch to take in advance to prefetch the right code<br /> | ||
| + | [[Protection#Protection_Lookaside_Buffer|PLB]] - Protection Lookaside Buffer<br /> | ||
| + | [[Protection#Portals|Portal]] - a cross turf call destination<br /> | ||
| + | [[Protection#Regions_and_Turfs|Protection Region]] - specified continuous memory region with attached permissions<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="q">q</div> | <div style="font-size: 10pt; font-weight: bold;" id="q">q</div> | ||
<div style="font-size: 10pt; font-weight: bold;" id="r">r</div> | <div style="font-size: 10pt; font-weight: bold;" id="r">r</div> | ||
| − | [[Replay]] - the way the hardware restores machine state after being interrupted<br /> | + | [[Memory#Retire_Stations|Retire Station]] - the piece of hardware that implements loads from memory, and where those loaded values end up<br /> |
| + | [[Protection#Region_Table|Region Table]] - the memory backing for the PLB<br /> | ||
| + | [[Pipeline#Result_Replay|Replay]] - the way the hardware restores machine state after being interrupted<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="s">s</div> | <div style="font-size: 10pt; font-weight: bold;" id="s">s</div> | ||
| − | [[SAS]] | + | [[Scratchpad]] - Temporary buffer for operands from the belt<br /> |
| − | [[Service]] | + | [[Virtual Address#Single_Address_Space|SAS]] - Single Address Space<br /> |
| − | [[Specializer]] | + | [[Protection#Services|Service]] - a stateful call interface that can cross protection barriers<br /> |
| − | [[Spiller]] | + | [[Slot]] - a logical and physical grouping of functional units sharing infrastructure for sequential step by step processing each cycle, emphasis on the logical aspect<br /> |
| − | [[Stacklet]] | + | [[Specializer]] - turns general/abstract Mill code into concrete hardware specific machine instructions<br /> |
| + | [[Speculation]] - computing several paths in branches in parallel only to later throw away the unneeded results<br /> | ||
| + | [[Spiller]] - securely manages temporary memory used by certain operations in hardware<br /> | ||
| + | [[Protection#Stacklets|Stacklet]] - hardware managed memory line used in fragmented stacks<br /> | ||
| + | [[Protection#Stacklet_Info_Block|Stacklet Info Block]] - preserves stacklet state for a thread across portal calls<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="t">t</div> | <div style="font-size: 10pt; font-weight: bold;" id="t">t</div> | ||
| − | [[TLB]] | + | [[Protection#Threads|Thread]] - a contained and ID'd flow of execution<br /> |
| − | [[Turf]] | + | [[Memory#Address_Translation|TLB]] - Translation Lookaside Buffer<br /> |
| + | [[Events#Traps|Trap]] - an interrupt that afterwards is intended to resume normal program flow<br /> | ||
| + | [[Protection#Regions_and_Turfs|Turf]] - memory protection domain on the Mill, a collection of regions<br /> | ||
<div style="font-size: 10pt; font-weight: bold;" id="u">u</div> | <div style="font-size: 10pt; font-weight: bold;" id="u">u</div> | ||
<div style="font-size: 10pt; font-weight: bold;" id="v">v</div> | <div style="font-size: 10pt; font-weight: bold;" id="v">v</div> | ||
| + | [[Memory#Implicit_Zero_and_Virtual_Zero|Virtual Zero]] - loads from all uninitialized memory yield zero<br /> | ||
| + | |||
<div style="font-size: 10pt; font-weight: bold;" id="w">w</div> | <div style="font-size: 10pt; font-weight: bold;" id="w">w</div> | ||
| + | [[Protection#Well_Known_Regions|WKR, Well Known Region]] - protection regions not defined in the PLB but in registers, automatically managed by hardware<br /> | ||
| + | |||
<div style="font-size: 10pt; font-weight: bold;" id="x">x</div> | <div style="font-size: 10pt; font-weight: bold;" id="x">x</div> | ||
<div style="font-size: 10pt; font-weight: bold;" id="y">y</div> | <div style="font-size: 10pt; font-weight: bold;" id="y">y</div> | ||
<div style="font-size: 10pt; font-weight: bold;" id="z">z</div> | <div style="font-size: 10pt; font-weight: bold;" id="z">z</div> | ||
Latest revision as of 21:25, 9 June 2015
0 a b c d e f g h i j k l m n o p q r s t u v w x y z
Abstract Code - general data flow code for the Mill architecture, distribution format
Abstract Assembly - general data flow code for the Mill architecture in human readable form, mainly used as compiler output
Backless Memory - allocating memory happens in cache initially and often no DRAM and system bus needs to be involved at all
Belt - provides the functionality of general purpose registers
Belt Position/Belt Location - the read only data source for machine operations
Block - a subsection of an instruction that contains a subset of the operations or data in a defined encoding format.
Bundle - a collection of instructions that get fetched from memory together
Concrete Code - specialized executable code for a specific Mill processor
Concrete Assembly - specialized executable code for a specific Mill processor in human readable form, mainly used for testing and in the debugger
Crossbar - the interconnecting framework that routes the data sources to the functional units
Decode - turning instruction stream bit patters into requests to functional units
Domains - operand value types, i.e. different interpretations of bit patterns by operations
EBB - extended basic block, a batch or sequence of instructions with one entry point and one or more exit points
Encoding – the semantic bit patterns representing operations
Event - an asynchronous diversion from normal program flow
Exit - a point where the instruction stream can leave the EBB
Exit Table - a hardware hash table containing exit point usage for EBBs, used to predict control flow
ExuCore - the collection of functional units and facilities serving operations from the exu instruction stream
Fault - an interrupt normal program flow cannot recover from in a meaningful way
First Winner Rule - only the first successful conditional branch operation in an instruction is taken
FlowCore - the collection of functional units and facilities serving operations from the flow instruction stream
FU, Functional Unit - the hardware module that provides the functionality to perform an operation
Ganging - combining more than two belt operands in more than one slot to perform a more complex operation
Implicit Zero - loads from new stack frames are implicitly zero
Interrupt - an event that has predefined but configurable handling code in the form of a function
Instruction - a collection of operations that get executed together
Instruction Stream - a sequence of instructions, the Mill has 2 working in parallel
Metadata - tags attached to belt slots that describe the data in it
Morsel - the amount of bits needed to address all belt locations on a core
None - undefined data in a slot that is silently ignored by operations
NaR - Not a Result, undefined data that traps when used in certain operations
Operation – the most basic semantically defined hardware unit of execution
Phase, Phasing - sequenced execution of different operations within one instruction
PLB - on chip cache for looking up protection regions for a virtual address
Pipeline - a logical and physical grouping of functional units sharing infrastructure for sequential step by step processing each cycle, emphasis on the physical aspect
Pipelining - arrangeing operations in the instruction stream in such a way as to maximize functional unit utilization
Portal - a gateway between different protection domains or turfs a thread can pass through
Prediction - deciding which branch to take in advance to prefetch the right code
PLB - Protection Lookaside Buffer
Portal - a cross turf call destination
Protection Region - specified continuous memory region with attached permissions
Retire Station - the piece of hardware that implements loads from memory, and where those loaded values end up
Region Table - the memory backing for the PLB
Replay - the way the hardware restores machine state after being interrupted
Scratchpad - Temporary buffer for operands from the belt
SAS - Single Address Space
Service - a stateful call interface that can cross protection barriers
Slot - a logical and physical grouping of functional units sharing infrastructure for sequential step by step processing each cycle, emphasis on the logical aspect
Specializer - turns general/abstract Mill code into concrete hardware specific machine instructions
Speculation - computing several paths in branches in parallel only to later throw away the unneeded results
Spiller - securely manages temporary memory used by certain operations in hardware
Stacklet - hardware managed memory line used in fragmented stacks
Stacklet Info Block - preserves stacklet state for a thread across portal calls
Thread - a contained and ID'd flow of execution
TLB - Translation Lookaside Buffer
Trap - an interrupt that afterwards is intended to resume normal program flow
Turf - memory protection domain on the Mill, a collection of regions
Virtual Zero - loads from all uninitialized memory yield zero
WKR, Well Known Region - protection regions not defined in the PLB but in registers, automatically managed by hardware
