Intel iapx 432 manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182

Aller à la page of

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Intel iapx 432. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Intel iapx 432 ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Intel iapx 432 décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation Intel iapx 432 devrait contenir:
- informations sur les caractéristiques techniques du dispositif Intel iapx 432
- nom du fabricant et année de fabrication Intel iapx 432
- instructions d'utilisation, de réglage et d’entretien de l'équipement Intel iapx 432
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Intel iapx 432 ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Intel iapx 432 et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Intel en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Intel iapx 432, comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Intel iapx 432, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Intel iapx 432. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    inter iAPX 432 Interface Processor Architecture Reference Manual 171863-001[...]

  • Page 2

    INTEL iAPX 432 INTERFACE P~OR Manual Orner Number 171863-001 Release 1.1 Oamponents Cb~right (C) 1981, Intel Corporation Intel Corporation, 3065 Bowers Avenue, Santa Clara, California 95051[...]

  • Page 3

    Additional oopies of this manual or other Intel literature may be obtained from: Literature Department Intel Corporation 3065 BCMers Avenue Santa Clara, CA 95051 The information in this document is subject to change without notice. Intel Corporation makes no warranty of any kind with regard to this material, including, but not limited to, the inpli[...]

  • Page 4

    PREFACE Understanding any complex comp.lting system, such as the Intel iAPX 432, requires the assimilation of a great deal of technical information. Before reading this manual on the architecture of the 432 Interface Processor, the reader should have conmand of the general 432 concepts. Intel offers three documents which provide these prerequisites[...]

  • Page 5

    TABLE OF CCNl'ENI'S TITLE 1. KE'Y' crncEP'l'S ...•.....•.•..•....••.....•••.•••••••••...•..•.. 1-1. 1-2. 1-3. 1-4. 1-5. Peripheral Subsystems •••••••••••••••••••••••••••••••••••• Basic I/O ~e1 •••••[...]

  • Page 6

    3. ~ ••••••••••••••••••••••••••••••••••••••••••••••••••••• 3-1. WindCM AttribJtes 3-2. 3-3. 3-4. 3-5. Wioo~ Status ••••••••••••••.••••••••••••••••••••••••••• Subr[...]

  • Page 7

    APPENDICES APPENDICES A. SYS'm1 ~ S~ ••••••••••••••••••••••••••••••••••••••• A-I. A-2. A-3. Context Objects Process Objects Processor Objects . ......................................... . ........................................ B. FUNCTICN S~Y ......................[...]

  • Page 8

    TITLE 1-1. 2-1. 2-2. 2-3. 3-1. B-1. B-2. B-3. D-l. E-l. TABLES PAGE Printer Example Legend ••••••••••••••••••••••••••••••••••• 1-18 IP/GDP System Object Comparison •••••••••••••••••••••••••• 2-3 IP/GDP Operator Comparison ••[...]

  • Page 9

    TITLE 1-1. 1-2. 1-3. 1-4. 1-5. 1-6. 1-7. 1-8. 3-1. 3-2. 3-3. 3-4. 3-5. 3-6. 4-1. 4-2. 4-3. 4-4. 4-5. 4-6. 6-1. 0-1. E-l. F-l. F-2. F-3. F-4. F-5. F-6 viii FIGURES 432 System and Peripheral Subsystems ••••••••••••••••••••• Basic I/O Service Cycle ••••••••••••••••••••?[...]

  • Page 10

    CHAPTER 1 KEY CCNCEPTS This chapter introduces the iAPX 432 Interface Processor (IP). The first four sections cover the IP as it is used normally in connection with inIXlt/output operations. Section 1-1 distinguishes Peripheral Subsystems (PS), which are responsible for the bulk of I/O operations, fran the 432 data processing system, and shows how [...]

  • Page 11

    iAPX 432 Interface Processor Architecture Reference Manual 432 Memory 432 System/Peripheral Subsystem Boundary Figure 1-1 432 System and Peripheral SljbSystems 1-2[...]

  • Page 12

    KEY CCHE?TS In a 432-based system, the bulk of processing required to support inplt/out];Xlt operations is delegated to Peripheral Subsystems; this includes device control, timing, interrupt handling and buffer ing • A Peripheral Subsystem is an autonomous computer system with its own memory, I/O devices am controllers, at least one processor, an[...]

  • Page 13

    iAPX 432 Interface Processor Architecture Reference Manual It is ~rtant to note that both the window and function facilities utilize and strictly enforce the standard 432 addressing and protection systems. Thus, a window provides protected access to an object, and a function provides a E.rotected way for Peripheral Subsystem software to interact wi[...]

  • Page 14

    432 System o Procesa O. Process running on GDP needs I/O service 1. Process formulates message describing service, sends it to device task 2. Device task receives service order, interprets it Service Order Messaqe Service Reply Message KEY CONCEP'IS Peripheral Subayatem ------------------- Device Task (:;' -V 3. Device task transfers dat[...]

  • Page 15

    1-6 iAPX 432 Interface Processor Architecture Reference Manual 432 System -------Peripheral Subsystem ------------ Figure 1-3 Peripheral Subsystem Interface Device Task f[...]

  • Page 16

    1- 3. PERIPHERAL SUBSYS'lm INTERFACE A Peripheral Subsystem interface is a collection of hardware and software that acts as an ad.aptor which enables message-based oammunication between a process in the 432 system and a device task in a Peripheral Subsystem. Viewed from the 432 side, the Peripheral Subsystem interface appears to be a set of pr[...]

  • Page 17

    432 Memory 1-8 iAPX 432 Interface Processor Architecture Reference Manual 432 System "tt H o (1 en UI UI o H I 3: (1) :I o H '< H ::s rt en H (1 o ::s ::s (1) n rt --------.~ ~~~--------- Peripheral Subsystem "tt co t1 Optional DMA ontrolle ~. ~---- ..... ---. :J" (1) t1 I» I-' ~ ~Attached ~ ~Iprocessor rt' (1) EJ [...]

  • Page 18

    KEY COOCEPTS Continuing the notion of the logical I/O processor, the Attached Processor fetches instructions, provides the instructions needed to alter the flow of execution, and performs arithmetic, logic and data transfer operations within the Peripheral Subsystem. INTERFACE P~SSOR The IP completes the logical I/O processor by providing data path[...]

  • Page 19

    iAPx 432 Interface Processor Architecture Reference Manual To sunmar ize, the Attached Processor and the Interface Processor interact with each other by means of address references generated by the AP and interrupts generated by the IP. Since the Interface Processor respoms to memory references, other active Peripheral Subsystem agents (bus masters[...]

  • Page 20

    KEY CXNCEP'IS The Interface Processor provides a process addressing environment within the 432 system which supports the operation of the I/O controller in the 432 system. This environment is embodied as a set of system objects that ·"are used and manipulated by the IP. At any t~e, the I/O controller is represented in 432 memory by IP pr[...]

  • Page 21

    iAPX 432 Interface Processor Architecture Reference Manual -f-Peripheral Subsystem Memory space---"I ~ 432 System Memory Space --. Local Memory Addresses Interface Processor ( IP window maps a subrange of peripheral subsystem addresses onto an object in 432 memory ..... ---- ... - --- I Subrange I 0, Object windowed Memory Reference"~&quo[...]

  • Page 22

    KEY CCNCEPTS Since a windCM is referenced like memory, any individual transfer may be between an obj ect and PS memory, an object and a PS processor register, or an object and an I/O device. The latter may be appealing from the standpoint of "efficiency," rut it should be used with caution. Using a windCM to directly "connect" a[...]

  • Page 23

    iAPX 432 Interface Processor Architecture Reference Manual The IP's function set permits the I/O controller to: o alter windows; o exchange messages with GOP processes via the standard 432 interprocess communication facility; o manitulate objects. These functions may be viewed as extensions to the Attached Processor's instruction set, whi[...]

  • Page 24

    KEY CONCEPTS _ Peripheral Sub8 Y 8tem_l_ Peripheral Subsystem Interface --lI-1 0+- 432 < Port Object> (1) System -. Action Data Location Input --- ...... ~. I ~.~-----output I Message 0 0 ~ ____ J~--"··~_B_u_~_~_e_r_~··IIf-----1·"O""4:l------I"·1(M~~~:~!)I""-----I··O _____ C_o_p.Y __ D_a_ta ____ 1 ..[...]

  • Page 25

    iAPx 432 Interface Processor Architecture Reference Manual I/O EXAMPLE To illustrate the operation of the 432 I/O model more specifically, this section provides a simple example which shows how line printer output might be implemented. Of course, the example describes only one of many possible awroaches that might be taken. Furthermore, the example[...]

  • Page 26

    CDP Proeeaa KEY CONCEPTS 432 Memory Peripheral subayatem Memory 432 'Syat_---- --- ____ .eripheral Subayatelll Intertace-----I_ .eripheral .ubayaUIII ____ _ Figure 1-7 Printer EKarnple 'rinter Task 1-17 8[...]

  • Page 27

    iAPX 432 Interface Processor Architecture Reference Manual Item SEND,/R:ErnIVE .Table 1-1 Pr inter Example Legend Description Object (message) descr ibing pr int operation fram requesting process's point of view (see figure 1-8). 432 communications port assigned by convention to queue print objects. 432 communicat ions port where GOP process w[...]

  • Page 28

    KEY <XNCEPTS Figure 1-8 shows hOil the message sent by the GOP process might be organized. It oonsists of two parts, an object reference part and a text part. The object references are for the text part of the object, the 432 port at which the process will wait for the message to be returned, arrl a reference for the process itself (GOP or IP). [...]

  • Page 29

    iAPX 432 Interface Processor Architecture Reference Manual Text~ Print Data CI Object References".,.;; __ Print Status Text Command Figure 1-8 Example Print Object 1-20[...]

  • Page 30

    KEY CONCEPTS Printer Server Task Perspective The printer server task may be viewed as a "front end" to the pr inter task which is responsible for translating the message sent by the GOP process into the form expected by the printer task. The printer server loops through the following steps: 1. RECEIVE a message from the print_request-POrt[...]

  • Page 31

    iAPX 432 Interface Processor Architecture Reference Manual 1-5. SUPPLEMENTARY INTERFACE ProcESSOR FACILITIES The preceding sections have described the Interface Processor as it is used most of the time. The IP provides two additional capabilities which are typically used less frequently, often only in exceptional circumstances. These are physical r[...]

  • Page 32

    The IP (like a GOP) requires two register interconnect space to be defined for any system: o the processor ID register (interconnect o the interprocessor communication (interconnect address 2) KEY CONCEPTS locations address 0) (IPC) in the register The remainder of the interconnect address space may be used to store or acquire other infoonation suc[...]

  • Page 33

    [...]

  • Page 34

    rnAPTER 2 CBJOCTS AND OPERA'lORS This chapter describes the 432 environment as it appears to the I/O controller software. It :r;x:>ints out what the I/O controller can, and cannot, do in the 432 system. The first section broadly compares the facilities provided by the Interface Processor to those available on the General Data Processor. The[...]

  • Page 35

    iAPX 432 Interface Processor Architecture Reference Manual To permit the I/O controller to function in the 432 system as well as in the Peripheral Subsystem, the IP provides an environment, and operators that it executes within this environment.· The environment is embodied in the system objects that the Interface Processor recognizes and manipula[...]

  • Page 36

    CI3JECrS AND OPERATORS Table 2-1 IP/GOP System Object Comparison Object Processor Object Process Obj ect Context Object Operand Stack Instruction Segment Object Table IkInain Port Carrier Storage Resource Type Definition Communication Segment Descriptor Controller Refinement Controller Legend: IP Implementation- similar similar similar none none id[...]

  • Page 37

    iAPX 432 Interface Processor Architecture Refer.ence Manual Through its windows, an IP provides the basic ability to read and wr i te the contents of objects composed of data segments. However, using its function request facility an IP can manipulate an access descriptor which references an object. The IP can examine a complex (multi-segment) objec[...]

  • Page 38

    CBJECrS AND OPERATORS Table 2-2 IP/GDP Operator Comparison (Part 1 of 2) Qe.erator WINIXJW DEFINITIOO OPERATOR Alter Map and Select Data Segment AOCESS DESCRIP'IOR M:NEMENl' OPERATORS Copy Access Deser iptor Null Access Descriptor RIGHTS ~IPUIATICN OPERATORS Amplify Rights Restr ict Rights TYPE DEFINITIOO MANIPUIATIOO OPERATORS Create Pub[...]

  • Page 39

    2-6 iAPX 432 Interface Processor Architecture Reference Manual Table 2-2 continued IP/GOP Operator Canparison (Part 2 of 2) ProcESS Cl:H1UNICATICN OPERA'IORS Send Receive Conditional Send Conditional Receive Surrogate Send Surrogate Receive Delay Read Process Clock fII PR)CESSOR (X)[MJNICATIGl OPERATORS Send to Processor Broadcast to Processo[...]

  • Page 40

    CBJECl'S AND OPERATORS 2- 2. CBJECl' ADDRESSING AND GLCBAL SIDRAGE MANAGEMENT Object addressing on the IP follows the same three level sequence as on a GOP. The steps taken to address an object are: 1. Given an access descriptor, a processor uses the directory index field to index the object table directory and gain a storage descr iptor [...]

  • Page 41

    iAPX 432 Interface Processor Architecture Reference Manual 2-4. FACILITIES FUR ASYNCHRCNOUS CDMJNlCATICN The IP offers the same set of operators for asynchronous interprocess communication as does a GOP, with the excey;>tion that the DEIAY operator ls not implemented. The DEIAY operator, used in scheduling to delay a process from being dispatche[...]

  • Page 42

    0BJECrS AND OPERATORS Contained in each obj ect ' s storage descr iptor is an I/O lock which is applied by the IP when a window is opened on the object. This lock serves 'bNo purposes: first it guarantees that only one IP window can be opened on a particular 432 object at a time; second it prevents IIDvement of the object (e.g. by a memor[...]

  • Page 43

    iAPX 432 Interface Processor Architecture Reference Manual Direct vs. Indirect Accessibility If a copy of an access descriptor for an object is in one of t.he four entry access segments, the object it references is dir.ectly accessible. To reference such an object, two values must be specified: o The number (0 to 3) of the entry access segment in w[...]

  • Page 44

    CEJECrS AND OPERATORS Table 2-3 Direct/lndirect Accessibility Viewpoint of IP/GDP in 432 System . Directly Accessible 432 Infor.mation o access descriptors All access descriptors in the four Entry Access Segments. o data All objects of type data segment referenced b¥ access descriptors in the four Entry Access Segments. Indirectly Accessible 432 I[...]

  • Page 45

    iAPx 432 Interface Processor Architecture Reference Manual Object Selectors An object selector identifies an object by specifying an access descriptor contained in one of the four entry access segments. The object selector oonsists of a double byte quantity composed of two fields: 1. The low order two bits of the object selector specify which entry[...]

  • Page 46

    The Interface Processor windCM mechanism provides the Per ipheral Subsystem with protected access to the contents of objects located in the 432 system. There are five windows, labeled 0-4. Each windCM can be used to access one (single segment) object. To prevent the possible manipulation of access descriptors as ordinary data and corruption of the [...]

  • Page 47

    iAPX 432 Interface Processor Architecture Reference Manual 3-1. WINJX)W ATl'RIBUl'ES Each window has a set of attributes which define its state at a given rnanent; these are sumnarized in table 3-1. The IP sets the attributes of all five windows when it performs processor qualification. The attributes of the control windcw are obtained fr[...]

  • Page 48

    Table 3-1 Window Attribute Summary Attribute Description Window Status Window is open/closed/faulted Subr ange Base Address Start of windowed subr ange in the PS Subrange Size Length of windowed subrange in the PS Obj ect Reference Obj ect Selector for windowed 432 obj ect Base Displacement Displacement in bytes into windowed 432 object Direction R[...]

  • Page 49

    iAPX 432 Interface Processor. Architecture Reference Manual SUBRANGE BASE AIDRESS AND SUBRANGE SIZE A windCM's subrange is defined by a subrange base address and a subrange size, in bytes. The subra~ is the contiguous set of Peripheral SUbsystem memory addresses that are mapped by the windCM. A Per ipheral Subsystem bus master that references [...]

  • Page 50

    WINOOWS <l3JECI' REFERENCE An open window's object reference begins as an object selector and is converted by the IP into an access descriptor for the windowed 432 object. Each open IP window must map a different object in 432 memory, am each obj ect must be represented as a sing Ie segment of base type data segment (functions may be u[...]

  • Page 51

    iAPX 432 Interface Processor Architecture Reference Manual DIRECl'ICN The direction attribute specifies whether the windowed object may be read, written, both read and written, or neither read nor written. When the window is opened the IP checks the requested direction attribute with the access rights granted by the object reference. The acces[...]

  • Page 52

    00 meaning for windows 2-4, which suWOrt random transfers to 432 system memory only; the random transfer mode is described in section 3-2. Attempting to set the transfer mode of windows 2-4 will cause a fault. OVERIAY Sane Peripheral Subsystems (e.g., those based on processors with limi ted address spaces) may not be able to dedicate a block of mem[...]

  • Page 53

    3-8 iAPX 432 Interface Processor Architecture Reference Manual -64K-:!::: I~~! ,::" -36K- )}js';ilirange of windo,:" opened iiiiii!i!! wl.th overlay attrl.bute set :-:-:-:.:. }} -32K- I :::: Illlllll _~_Illi! Memory IP E:J Enabled addresses t;~;~tl Disabled addresses Figure 3-1 Memorv Overlay[...]

  • Page 54

    WINOOWS 3- 2. W1NIXM OPERATI(lJ This section descr ibes the IP' s response to an address reference that falls into the windowed subrange of an open windGl. The discussion covers random mode transfers to and from ordinary memory-based objects; the special cases of block mode, interconnect objects and function requests are covered in subsequent[...]

  • Page 55

    %P 64K Byt Rang e e Access iAPX 432 Interface Processor Architecture Reference Manual PS ADDRESS SPACE 432 ADDRESS SPACE -r- --.-.----- , ~ SOBRANGE LENGTH .. p- I Transfer 1 Displacement _ .... _---- 1 Initial Computations o Adjusted Object Length = Object Length - Base Displacement o Visible Object Length = Minimum (Adjusted Object Length, Byte C[...]

  • Page 56

    MAPPED IP WINDOW 432 OBJECT 0 ----0 ----- LJ /// 0 ----· ------- O ----c/// ---- //// LJ ", ----0 ........ -- WINDOW - OBJECT WINDOW -: OBJECT WINDOW a REFINEMENT OBJECT oc: WINDOW WINOOW> REFINEMENT ~ PORTION OF OBJECT INACCESSIBLE TO IP ~ -- PORTION OF WINDOW INACCESSIBLE TO AP Figure 3-3 Valid Window/Object Mapping 3-11[...]

  • Page 57

    LAPX 432 Interface Processor Architecture Reference Manual 3- 3. RANOOM mOE DATA TRANSFER Given that an IP address reference has passed the consistency checks, the IP finishes the Peripheral Subsystem bus cycle just as a menory oomponent would, accepting data from the bus in a wr i te operation, and placing data on the bus in a read operation. It f[...]

  • Page 58

    41 03 ... .... 4096 Windot'-1ed Subrange Legend -.., ...... 3 1 2 - - - - Reference Sequence: - - - - - - Byte disP1acement~ I - - - Windowed Object G) (7) (6) (5) (4 ) ( 3) (2) (1) (0) <Y G) Subrange Address Referenced: 4'97 4102 Reference Operation: 4'99 Read Byte 3 Write Byte Read Double-byte Object Byte Accessed (disp.) 1 6,7 [...]

  • Page 59

    iAPX 432 Interface Processor Architecture Reference Manual 3-4. BIOCK MJDE MTA TRANSFER Window 0 can be opened in random m::Xie or in block mode. Block mode allows the Peripheral Subsystem to take advantage of software instructions (e.g. iAPx 86 str:i.ng operations) and devices such as ~ controllers, which are capable of generating consecutive addr[...]

  • Page 60

    WINOOWS BLOCK MODE CCNSIS'lENCY CHEr!K Since the byte count and base displacement effectively predefine the transfer from the perspective of the 432 object, the IP can perform most of the required consistency checks when the window is opened. The only checks made during a transfer are direction and byte count. BI.D:K moE OPERATICN From the p::[...]

  • Page 61

    iAPX 432 Interface Processor Architecture Reference Manual Canpleting a block node write transfer which is shorter than the byte count is a two-step process. First, the AP must issue an ALTER MAP AND SELECl' DATA SEGmNI' function with the entry state operand to "force termination" on window o. This causes the IP to empty its FIF[...]

  • Page 62

    WINOOWS BLOCK MODE ADDRESS ING As mentioned earlier, in a block mode transfer the IP determines the displacement of a transf€r inbo the windowed object b¥ means of its on-chip displacement counter. Unlike random mode, then, the object displacement is independent of the subrange displacement. This gives rise to two addressing techniques that may [...]

  • Page 63

    iAPx 432 Interface Processor Architecture Reference Manual ----------- 41 03 Byte diSPlacement~ (7) (6) 3-18 4 096 Windowed Subrange 3 2 1 - - - - - - Windowed Object (5) (4) (3) (2) T 3 (1) ! (0) - (Base Displacement) Legend <D G) G) Reference Sequence: Subrange Address Referenced: Reference Operation: Object Byte Accessed (disp.): 4,99 4100 41[...]

  • Page 64

    4096 Legend ..... ----,," Windowed Subrange Reference Sequence: " " ,,'- , , Sub range Address Referenced: Reference Operation: Object Byte Accessed (disp.): Byte displacement, ,,,, (7)~ ""'- ""'- ,~---~ Windowed Object (6) (5) (4) ( 3) (2) (1) Tf;Base (,) 1 Displacement) G) CD 4'96 Read Byte 2[...]

  • Page 65

    iAPx 432 Interface Processor Architecture Reference Manual 3-5. INTE~ TRANSFERS Window 1 may be opened onto either the 432 memory space or the 432 processor-memory interconnect space. The address space is selected by the transfer JlDde attribute when window 1 is opened; it may be changed at any time ~ closing the window and re~pening it with the tr[...]

  • Page 66

    OiAPTER 4 FONcrIOOS This chapter describes the common facility that supports the execution of all Interface Processor functions. The first section shows hCM windCM 4 is used to provide access to the facility. The next section explains how a function is requested by writing operands and an o~""Ode through the windCM. The last two sections [...]

  • Page 67

    4-2 iAPX 432 Interface Processor Architecture Reference Manual Operands (reserved) Opcode Function State Process Selection Index Processor Data Segment Figure 4-1 Function Request Area 9 8 7 6[...]

  • Page 68

    IP WINDOWS 432 SYSTEM 0--- --_~ IP __ ......... PROCESSOR DATA SEGMENT 0 ------0 ---- ---- 0 ------0 -_ .... ---- 0 ------0 ...--- ---- 0 --- ---0 fI ___ ____ B D DATA SEGMENTS FUNCTICNS IP WINDOWS 432 SYSTEM ORIGINAL MAPPING ALTERED WINDOW ~ MAP Figure 4-2 Function Example 4-3[...]

  • Page 69

    iAPX 432 Interface Processor Architecture Reference Manual 4- 2. FUNCrICN REC.UFSTS The performance of a function may be considered fram the AP point of view as a sequence of three phases, as shown in figure 4-3. The IP controller, running on the AP, performs the first phase, requesting the execution of a function. The IP executes functions seriall[...]

  • Page 70

    • • • Read function state Write operands Write opcode I " Perform other processing,' ---------. I I _____ __ ~ Interrupt • from IP ~ - - ,.-_-_-_~ __ ... I Read function state • • • Read return- value FUNCl'ICNS Request Phase Execution Phase Completion Phase Figure 4- 3 Function Performance Phases - AP View [...]

  • Page 71

    iAPX 432 Interface Processor Architecture Reference Manual FUNCl'IOO OPERANDS An Interface Processor function may require fran zero to seven <DubIe-byte operands. The IP controller specifies a function's operands by writing values into locations of the operands field in the function request area. The first operarrl goes in the lcwest-a[...]

  • Page 72

    FONcrICNS I I 15 , Short Ordinal ~~ ________ ~y _______ -J' l~-------------(16-bit unsigned integer) 15 , I : : : i : : : : : : : : ! : :] , v,------I Bit Field 15 l .., l,------(Subfields defined by function) 21! I f I~ Object Selector ~Entered Access Segment Identifier ~, = Context Access Segment gl = Entered Access Segment 1 l' = Enter[...]

  • Page 73

    ~ 432 Interface Processor Architecture Reference Manual 15 , p0000000000001Il~ Object Selector Operand d ° fO Entere Access Segment Identl. l.er - - - --- - - - - - - - - - -, Access Descriptor Index --------- - - - - - - - - - - r---~-----"'" L 1 L ~ L o 0 (2) o 0 (1) L o 0 UI> 0 ~----------~ ~------------ ::L [...]

  • Page 74

    FUNcrIONS 4- 3. FUNcrICN EXOCUTICN The IP per forms the actual execution of a function independent of the IP controller. Therefore the IP controller (an Attached Processor with associated IP control software) is free do other work after it has requested execution of a function (except that it must refrain from requesting a second function). Altr~ug[...]

  • Page 75

    4-10 iAPX 432 Interface Processor Architecture Reference Manual Qualify Selected Process Decode Opcode Perform operation Update destinations Update Return-value Update function completion state Gener~ 1nt:~J no Figure 4-6 Basic IP Function Execution Flow[...]

  • Page 76

    FUNCl'IONS Successful execution of a function typically causes the alteration of a destination operand (that is, an actual operand~ the operands field of the function request area is never changed by function execution). In addition, or alternatively, same functions produce a return-value. For example, the READ PR:CESSOR STATUS AND CLOCK funct[...]

  • Page 77

    [...]

  • Page 78

    • 'it' n CHAPTER 5 PHYSICAL REEKRENCE MJOE The preceding chapters of this manual have Dmplicitly described the Interface Processor's logical reference node, its mrmal nnde of oper ation. The IP also provides ptzsical reference mode. Physical reference mode is distinguished rom logical reference mode by direct 24-bit base-plus-displ[...]

  • Page 79

    iAPX 432 Interface Processor Architecture Reference Manual 5-2. PHYSICAL REFERENCE mDE ADDRESSING In physical reference mode the object reference attribute of a window is replaced b¥ a 24-bit segment base address. Upon recognition of a subrange address reference the IP determines the transfer displacement as in logical reference node. It forms the[...]

  • Page 80

    CHAPTER 6 FAULTS . This chapter describes IP faults, exceptional corrlitions which can occur as the IP performs functions. In general, the IP fault philosophy follows that of the GOP: the processor detects and contains faults so they do not affect other processes or processors in the 432 system. The response to a fault, i.e. fault handling, is not [...]

  • Page 81

    iAPx 432 Interface Processor Architecture Reference Manual The IP records fault information in various areas of IP process and processor objects (refer to Appendix A for detailed description of these fault information areas). There are three categories of IP operation in which faults may be generated: physical reference node, logical reference node[...]

  • Page 82

    FAULTS· Context-Level Faults Context-level faults are the least severe of the IP logical node faults. A context-level fault arises fran exceptions which can be confined to the context in which the IP is operating. The IP may fault when attempting to execute a function or during the movement of data through one of the windows. One example of a cont[...]

  • Page 83

    iAPX 432 Interface Processor Architecture Reference Manual The fault port is serviced by a 432 fault handling process where one of four actions may be taken: o Correct the reason for the fault and OOmplete any partially perfonmed function by completing the unfinished steps. o Correct the reason for the fault, rewind any partially performed function[...]

  • Page 84

    processor ipsor.psor process i prcs. prcs . context iprcs.ctxt. LEGEND: FAUL TED STATE ~ ~ 4~ .. ~~ FAULTS "FATAL" . , ,~ ~~ FLT FLT FLT FLT processor processor processor ipsor .psor ipsor.psor ipsor.psor .4~ ~. ~~ FLT FLT FLT PRO FAU process ; prcs . prcs . . , FLT FLT ~ . es BO~ND no 4, PROCESS FAULT CONTEXT FAULT FAULT INFORMATION AREA[...]

  • Page 85

    iAPX 432 Interface Processor Architecture Reference Manual 6-2. FAULT HANDLING When an IP process encounters a process-level fault, it is autanatically sent to a 432 fault port to await service. A fault handling 432 process is designated to service the faulted processes waiting at the fault port. By design, IPs and GOPs share a cormnon base archite[...]

  • Page 86

    APPENDIX A SYSTEM OBJECT STRUCTURES The object structures of Interface Processors are described belOil. The only objects structures described are for those whose form or interpretation differ fran GOP object structures. Note that the values found in the length fields in the var ious objects descr ibed belOil are encoded as "actual length minus[...]

  • Page 87

    iAPX 432 Interface Processor Architecture Reference Manual A context object is represented by a context access segment and an associated context data segment. Context Access Segments Diagranmatically, a context access segment is structured as shown belCM. context access = = entry 1 1----------------1 8 domain AD -1---> domain of definition 1----[...]

  • Page 88

    SYSTEM OBJECI'S STRUCIURES A- 2. PROCESS <l3JEC'IS Logically, a process is the execution by a processor of an instruction stream within a specific environment. In a combined Attached Processor/Interface Processor system, the IP process object extends the execution environment of an AP process to logically include a specific domain in t[...]

  • Page 89

    iAPX 432 Interface Processor Architecture Reference Manual process access entry = = 1----------------1 = refined context access segment = 12 1 1----------------1 11 1 carrier AD -1---> surrogate carrier 1----------------1 1 carrier AD -1---> current carrier 1----------------1 port AD -1---> current port 1----------------1 AD -1---> curr[...]

  • Page 90

    SYSTEM 0BJECrS STRUCTURES Process Data Segments The basic structure of a process data segment is shown below. = = double byte 1 displacement 1----------------1 = refined context data segment = 1 1 90 1----------------1 process = fault = information 1 1 77 1----------------1 context = fault = information 64 1----------------1 = reserved = 9 1-------[...]

  • Page 91

    iAPX 432 Interface Processor Architecture Reference Manual The organization of the process status field is shown below. !x!x! 9 bits !x1x!x1x1xl II! 1 1 1- bound 1 1---- waiting for message 1------ process faulted 1-------- reserved 1--------- context faulted 1------------------ reserved 1------------------------- one vector only 1-----------------[...]

  • Page 92

    SYSTEM. 0BJECl'S STRUClURES A- 3. PROCF.5SOR CBJECTS An 432 Interface Processor consists of two cxx:>perating processing elements: a mapping facility and a function request facility. The mapping facility translates Peripheral Subsystem addresses into 432 system addresses. The function request facility executes the operator set described in [...]

  • Page 93

    A-a iAPX 432 Interface Processor Architecture Reference Manual processor access entry 21 20 segment --> 0 = = 1----------------1 1 1 process = selection = list 1----------------1 1- -1 1 1- mapped -1 data 1- segments -1 1 1- -1 1----------------1 1 AD -1---> reserved 1----------------1 AD -1---> reserved 1----------------1 1 AD -1---> r[...]

  • Page 94

    SYSTEM 0BJECrS STRUCTURES The base rights field of a processor access segment access descriptor is interpreted in the same manner as for all objects of base type access segment. The la-l order bi t of the system rights field of a processor access descriptor is interpreted as follows: o - an interprocessor message may not be broadcast via the global[...]

  • Page 95

    iAPX 432 Interface Processor Architecture Reference Manual double byte = = displacement 1----------------1 = control window area = 1 4 1----------------1 reserved 1----------------1 ! cur. prcs idx. 1 1----------------1 processor 1 psor status 1 data 1----------------1 segment -->! object lock ! a 1----------------1 The processor status field is[...]

  • Page 96

    SYSTEM 0BJECl'S STRUCl'URFS The stowed bit is interpreted as follows: o - running I - stopped The broadcast acceptance mode bit is interpreted as follows: o - broadcast interprocessor messages are not being accepted and acknowledged I - broadcast interprocessor messages are being accepted or acknowledged Note that the processor ID fields [...]

  • Page 97

    A-l2 LAPX 432 Interface Processor Architecture Reference Manual control window area double byte = = displacement 1----------------1 80 = reserved = 77 1----------------1 ! ! processor = fault = information 64 !----------------1 1 selected state ! 63 1----------------1 1 selected idx. 62 1----------------1 mapping facility = fault = information 65 1[...]

  • Page 98

    SYSTEM 0BJECrS STRUCl'URES Peripheral Subsystem State Field - The organization of the Peripheral Subsystem state field is shown belCM. 1 12 bits lxlxxlxl 1 1 1 1-- write sample delay ! 1--- xack delay 1 1------- interrupt inhibit 1------------- reserved The write sample delay field and the xack delay field program the characteristics of the IP[...]

  • Page 99

    • iAPX 432 Interface Processor Architecture Reference Manual Alarm, Dispatching, and Reconfiguration State Fields - The alarm, dispatching ("select process"), and reconfiguration state fields are used to indicate that the processor has responded to that type of signal and signalled the associated Peripheral Subsystem via interrupt. Each[...]

  • Page 100

    SYSTEM 0BJECl'S STRt.CIURES Function State Field - The function state field is used to describe the current state of the function request facility. It has the following organization. 8 bits lxxlxlxlxxxxl 1 1 1 1-- function completion state 1 1----- SEND completion state 1 1------- RECEIVE completion state 1--------- fault level 1--------------[...]

  • Page 101

    iAPX 432 Interface Processor Architecture Reference Manual current status information. When operands are read from this subr ange or wr i tten into this subr ange, the processor data segment is accessed. Data written into the part of the subrange representing the function request facility is captured when no function is in progress. During function[...]

  • Page 102

    SYSTEM OBJECTS STRUCTURES Above the block transfer information, a copy of the information contained in each of the processor-resident map entr ies (0 through 4) is represented by a data structure with the following organization. = = double byte 1----------------1 displacement 1 base disp. 4 1----------------1 1 mask 1 1--------7-------1 base addres[...]

  • Page 103

    iAPX 432 Interface Processor Architecture Reference Manual The 2-bit transfer direction subfield indicates the types of read/write requests from the associated Peripheral Subsystem which are valid with respect to this map entry. The low order bit of the transfer direction subfield is interpreted as follows: o - reading may not occur 1 - reading may[...]

  • Page 104

    SYSTEM OBJECl'S STRUCTURFS The base displacement field contains the byte displacement into the 432 segment used to construct a refinement of a data segment. See Figure 3-2 for an illustration of the role of a window's base displacement in forming a refinement. Mapping Facility Fault Information Area - The mapping facili ty fault informati[...]

  • Page 105

    iAPX 432 Interface Processor Architecture Reference Manual The I-bit segment bound subfield indicates whether or not the associated fault was caused by a segment bounds violation. A value of zero indicates that the fault was not caused by a segment bounds violation. A value of one indicates that the fault was caused by a segment bounds violation. T[...]

  • Page 106

    SYSTEM 0BJECrS srRUCTURES Selected Index and Selected State Fields - The selected index and selected state fields are filled in by the processor fram information found in the process carrier data segment at process selection time, i. e when a "select process" IPC is received. The selected index is a process selection index used to conmuni[...]

  • Page 107

    iAPX 432 Interface Processor Architecture Reference Manual 4 - Clear broadcast acceptance mode 5 - Flush object table 6 - Suspend and fully requalify processor 7 - Suspend and requalify processor 8 - 14 - Unused 15 - Close (Invalidate) Windows and Unlock I/O Locks (on windows 0-3) 16 - Generate PS Reset 17 - Close (Invalidate) Windows and Unlock I/[...]

  • Page 108

    APPENDIX B FUNcrIOO SUMMARY Ap;>endix B sumnarizes the Interface Processor functions. Three lists are provided to assist in locating the page which contains a particular functioo description. One list, Table B-1, organizes the function set by alphabetical order. Table B-2 organizes the function set by increasing function code number and is -r;&g[...]

  • Page 109

    iAPx 432 Interface Processor Architecture Reference Manual TABLE B-1 ALPHABEl'ICAL INDEX TO IP FUNcrICNS HEX DECIMAL FUNCTICN OPERATOR FUNcrICN NAME CODE ID PAGE (Logical Mode Functions) ALTER MAP AND SEI..:OCT DATA SEG1ENT 00 3 B-6 AMPLIFY RIGHTS 08 11 B-8 BIDAOCAST TO P~SORS 18 27 B-9 CCNDITIOOAL ROCEIVE 15 24 B-I0 roIDITICNAL SEND 13 22 B-1[...]

  • Page 110

    FUNCTIOO SUMMARY 'mBLE B-2 IP FUNcrICN SUMMARY BY FUNcrICN CODE HEX DECIMAL FUNCTICN OPERATOR CDDE FUNCrICN NAME ID PAGE (Logical Mode Functions) 00 ALTER MAP AND SELECr DATA SEGiENI' 3 B-6 01 SEND TO PKOSSOR 4 B-29 02 SET PERIPHERAL SUBSYSTEM ~DE 5 B-31 03 READ P~SSOR STATUS AND CLOCK 6 B-21 04 CDPY ACCESS DESCRIPTOR 7 B-12 05 NUIL ACCES[...]

  • Page 111

    iAPX 432 Interface Processor Architecture Reference Manual TABLE B-3 IP FUNCl'ICN SUMMARY BY OPERATOR ID DEX::IMAL HEX OPERATOR FUNCl'ICN ID FUNcrIOO NAME (DDE PAGE (logical Mode Functions) 3 ALTER MAP AND SELECT DATA SEG1ENI' 00 B-6 4 SEND TO PROCESSOR 01 B-29 5 SRI' PERIPHERAL SUBSYSTEM MDE 02 B-31 6 READ PROCESSOR STATUS AND [...]

  • Page 112

    FUNCl'IOO StM1ARy FUNCl'ICN 'IEMPIA'IE Operator ID: ID Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1 1------------------------1 operand 6 1 reserved 1------------------------1 oper and 5 1 reserved . 1 1------------------------1 operand 4 1 reserved 1------------------------1 oper[...]

  • Page 113

    iAPX 432 Interface Processor Architecture Reference Manual ALTER MAP AND SELECr DATA SEGmNI' Operator ID: 3 Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1 1------------------------1 operand 6 1 BLOCK COON!' 1------------------------1 operand 5 1 BASE DISPIACEMENI' 1---------------------[...]

  • Page 114

    FUNCrlOO SUMMARY ArlIER MAP AND SELECI' PHYSICAL SEG1ENI' Operator ID: 3 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 0 through 9 1 reserved 20H-33H 1------------------------1 oper am 6 1 reserved lEH 1------------------------1 operam 5 IPHYSICAL ADDRESS (high 8) 1 lCH 1------------------------1 op[...]

  • Page 115

    iAPX 432 Interface Processor Architecture Reference Manual AMPLIFY RIGHTS Operator 10: 11 Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1------------------------1 operarrl 6 1 reserved 1------------------------1 oper arrl 5 1 reserved 1------------------------1 operand 4 1 reserved 1-------------------[...]

  • Page 116

    FUNCl'ICN Sl:M-1ARY BroAOCAST TO POCCESSORS Operator ID: 27 Contents Function Request Facility 1------------------------1 results I through 9 1 reserved 1 1------------------------1 result 0 1 BOOLEAN 1------------------------1 oper arrl 6 1 reserved 1------------------------1 operarrl 5 1 reserved 1 1------------------------1 oper and 4 1 res[...]

  • Page 117

    iAPX 432 Interface Processor Architecture Reference Manual <DNDITIOOAL ROCEIVE Operator ID: 24 Contents Function Request Facility 1------------------------1 results I through 9 1 reserved 1 1------------------------1 . . result 0 1 BOOLEAN 1 1------------------------1 oper and 6 1 reserved 1------------------------1 operand 5 1 reserved 1-------[...]

  • Page 118

    FUNCrIOO Sm.f.1ARY CCNDITlOOAL SEND Operator ID: 22 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 1 through 9 1 reserved 1 22H-33H 1------------------------ result 0 1 BOOLEAN 20H 1------------------------ oper am 6 1 reserved lEH 1------------------------ oper am 5 1 reserved lCH 1------------------------1 o[...]

  • Page 119

    iAPX 432 Interface Processor Architecture Reference Manual COpy ACCESS DESCRIPTOR Operator 10: 7 Contents Function Request Facility 1------------------------1 results 0 through 9 ! reserved ! 1------------------------1 oper and 6 1 reserved 1------------------------1 operand 5 1 reserved 1------------------------1 oper and 4 1 reserved 1-----------[...]

  • Page 120

    EN'lER ACCESS SEG1ENI' Operator ID: 10 Contents Function~est Facility Hex Byte Offset 1------------------------ results 0 through 9 ! reserved 20H-33H 1------------------------ operand 6 ! reserved lEH 1------------------------ operand 5 1 reserved lCH 1------------------------, oper and 4 1 reserved lAH 1------------------------ oper and[...]

  • Page 121

    iAPX 432 Interface Processor Architecture Reference Manual ENrER GLOBAL AOCESS SEG1Em' Operator ID: 9 Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1 1------------------------1 oper am. 6 1 reserved 1 1------------------------1 oper am. 5 1 reserved 1 1------------------------1 oper and 4 1 reserv[...]

  • Page 122

    FUNCTICN SUI+1ARY INDIVISIBLE ADD SHORI' ORDINAL Operator ID: 28 Contents Function Request Facility Hex Byte Offset 1------------------------1 results I through 9 ! reserved 1 22H-33H 1------------------------1 result 0 ! ORIGINAL VALUE 20H 1------------------------1 oper and 6 1 reserved lEH 1------------------------1 operand 5 ! reserved ICH[...]

  • Page 123

    iAPx 432 Interface Processor Architecture Reference Manual INDIVISmLE INSERr SHORT ORDINAL Operator ID: 29 Contents Function Request Facility 1------------------------1 results I through 9 1 reserved 1------------------------1 result 0 1 ORIGINAL VALUE 1 1------------------------1 oper am 6 ! reserved 1------------------------1 operand 5 1 reserved[...]

  • Page 124

    FUNcrICN St.M1ARy INSPECr ACCESS Operator ID: 18 Contents Function Request Facility 1------------------------1 results 2 through 9 1 OBJECT DESCRIPTOR IMAGE! 1------------------------1 results 0 through 1 1 ACCESS DESCRIPTOR IMAGEI 1------------------------1 oper and 6 1 reserved 1 !------------------------1 operand 5 1 reserved 1------------------[...]

  • Page 125

    iAPX 432 Interface Processor Architecture Reference Manual INSPECr AOCESS DESCRIPTOR Operator ID: 17 Contents Function Request Facility 1------------------------1 results 2 through 9 1 reserved 1------------------------1 1 SOURCE ACCESS Hex Byte Offset 24H-33H results 0 through 1 1 DESCRIPTOR IMAGE 20H 1------------------------1 operand 6 1 reserve[...]

  • Page 126

    FUNcrION SUMMARY ~K 0BJECl' Operator ID: 19 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 1 through 9 1 reserved 1 22H-33H 1------------------------1 result 0 1 BOOLEAN 1 20H 1------------------------1 operam 6 1 reserved 1 lEH 1------------------------1 oper am 5 ! reserved lCH 1------------------------[...]

  • Page 127

    iAPX 432 Interface Processor Architecture Reference Manual NULL AOCESS DESCRIPTOR Operator ID: 8 . Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1 1------------------------1 oper and 6 1 reserved 1 1------------------------1 operand S 1 reserved 1------------------------1 oper and 4 1 reserved 1 1-----[...]

  • Page 128

    READ P~OR STATUS AND cra:K (IDgical and Physical Mode) Operator ID: 6 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 2 through 9 1 reserved 1------------------------1 result I 1 SYSTEM cra:K 1 24H-33H 22H 1-- ____ -------------- ____ 1 . . resul t 0 1 PRDCESSOR STATUS 1 20H 1------------------------1 oper am 6[...]

  • Page 129

    iAPX 432 Interface Processor Architecture Reference Manual ~IVE Operator ID: 23 Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1------------------------1 . . oper am 6 1 reserved 1------------------------1 operam 5 1 reserved 1------------------------ Hex Byte Offset 20H-33H lEH ICH oper and 4 1 reserve[...]

  • Page 130

    FUNcrION S~ RESl'RIcr RIGHTS Operator ID: 12 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 0 through 9 1 reserved 20H-33H 1------------------------ oper and 6 1 reserved lEH 1------------------------ oper and 5 1 reserved ICH 1------------------------ oper and 4 1 reserved lAB 1------------------------1 [...]

  • Page 131

    iAPX 432 Interface Processor Architecture Reference Manual REl'RIEVE PUBLIC TYPE REPRFSENI'ATICN Operator ID: 14 Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1------------------------1 oper and 6 1 reserved 1------------------------1 oper am 5 1 reserved 1------------------------1 Hex Byte O[...]

  • Page 132

    FUNcrIOO St.Mo1ARY REl'RIEVE TYPE REPRESENTATICN Operator ID: 13 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 0 through 9 1 reserved 1 20H-33H 1------------------------1 operam 6 1 reserved lEH 1------------------------1 operam 5 1 reserved 1 ICH 1------------------------1 oper am 4 1 reserved lAB 1----[...]

  • Page 133

    iAPX 432 Interface Processor Architecture Reference Manual REI'RI1WE REFINED CBJEcr Operator ID: 16 Contents Function Request Facility 1------------------------1 results a through 9 ! reserved ! 1------------------------ operand 6 1 reserved 1------------------------ oper and 5 1 reserved 1------------------------ Hex Byte Offset 20H-33H lEH l[...]

  • Page 134

    RErRIEVE TYPE DEFINITICN Operator ID: 15 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 0 through 9 1 reserved 1 20H-33H 1------------------------ oper am 6 1 reserved lEH 1------------------------ oper am 5 1 reserved lCH 1------------------------ oper and 4 1 reserved lAB 1------------------------1 oper and [...]

  • Page 135

    iAPX 432 Interface Processor Architecture Reference Manual SEND Operator ID: 21 Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1------------------------1 oper and 6 1 reserved 1 1------------------------1 oper am 5 1 reserved 1------------------------1 operand 4 1 reserved 1 1------------------------1 H[...]

  • Page 136

    FONcrION Sl.Mo1ARY SEND TO PROCESSOR (IDgical Mode) Operator ID: 4 Contents Function Request Facility Hex Byte Offset 1------------------------1 results I through 9 1 reserved 1 22H-33H 1------------------------ result 0 1 BOOLEAN 20H 1------------------------ oper and 6 1 reserved lEH 1------------------------ operaoo 5 1 reserved ICH 1-----------[...]

  • Page 137

    iAPX 432 Interface Processor Architecture Reference Manual SEND TO PRX:ESSOR (Physical· Mode) Operator ID: 4 Contents Function Request Facility 1------------------------1 results 1 through 9 1 reserved 1 1------------------------1 result 0 1 BOOLEAN 1------------------------1 oper and 6 1 reserved 1------------------------ Hex Byte Offset 22H-33H [...]

  • Page 138

    FUNcrIOO SUl+1ARY SEI' PERIPHERAL SUBSYSTEM MODE (logical and Physical Mode) Operator ID: 5 Contents Function Request Facility Hex Byte Offset 1------------------------1 results 0 through 9 1 reserved 1 20H-33H 1------------------------1 oper and 6 1 reserved lEH 1------------------------1 oper and 5 1 reserved ICH 1------------------------1 o[...]

  • Page 139

    iAPx 432 Interface Processor Architecture Reference Manual StJRROGATE ROCEIVE Operator ID: 26 Contents Function Request Facility 1------------------------1 results 0 through 9 1 reserved 1------------------------1 oper am 6 1 reserved 1 1------------------------1 oper am 5 1 reserved 1------------------------1 oper am 4 1 reserved 1----------------[...]

  • Page 140

    FUNcrICN S~ SURroGA'lE SEND Operator 10: 25 Contents Function Request Facility Hex Byte Offset 1------------------------ results 0 through 9 1 reserved 20H-33H 1------------------------ oper and 6 . 1 reserved lEH 1------------------------ oper and 5 1 reserved ICH 1------------------------ oper and 4 1 reserved l.AH 1------------------------ [...]

  • Page 141

    iAPX 432 Interface Processor Architecture Reference Manual UNLOCK 0BJECr Operator 10: 20 Contents Function Request Facility 1------------------------ resul ts 0 through 9 ! reserved 1------------------------ operand 6 1 reserved 1------------------------ oper and 5 1 reserved 1------------------------ Hex Byte Offset 20H-33H 1EH ICH operand 4 1 res[...]

  • Page 142

    C-l. FAULT REPORTING APPENDIX C FAULT SUMMARY Both logical ana physical mode faults are reported in fault information areas as descr ibed belON. The faul t information area for oontext, process, and processor level faults has the same organization. Process objects contain fault information for context and process level faults which occur in logical[...]

  • Page 143

    iAPX 432 Interface Processor Architecture Reference Manual fault information area = = double byte 1 displacement 1----------------1 1 execution statel n+12 1----------------1 1 operator id 1 1----------------1 1 system tbner 1 1----------------1 1 psor status 1----------------1 1 cxt/prcs statusl 1----------------1 1 PS status 1 1---------------- f[...]

  • Page 144

    FAULT SUMMARY The Peripheral Subsystem status, context/process status, processor status, and system timer fields contain the values of the the corresponding on-chip registers at the time of the fault. The o:perator id, which differs fran the opcode field in an instruction, specifies the operator that causes the fault. If a fault occurs during instr[...]

  • Page 145

    iAPX 432 Interface Processor Architecture Reference Manual The W field specifies whether the fault was on a read or write access. A value of zero indicates a read access. A value of one indicates a write access. The faulted displacement is recorded in the fault displacement (in access memory, or interconnect), and in the object index field of the f[...]

  • Page 146

    FAULT SUMMARY The TT and EEEE fields specifY the fault level and the fault type. The TT bits are interpreted as follows: TT Description 00 Context Level Faults 01 Process Level Faults (group 1) 10 Process Level Faults (group 2) 11 Processor Level Faults There are 16 fault types within each of the 4 groups. The encoding column of the tables in the f[...]

  • Page 147

    iAPX 432 Interface Processor Architecture Reference Manual Sub-operations Faults FAULT GroUPS Sbore Access Descriptor Faults => Level Fault Destination Delete Rights Fault Object Qualification Faults => Access Descripbor Validity Fault Obj ect Descr iptor Fault Object Descripbor Type Fault Memory Overflow Fault Read/Write Rights Fault Port Op[...]

  • Page 148

    Operator Faults OPERATOR Alter Map and Select Data Segment Interconnect Descriptor Fault I/O Lock Fault Transfer Direction Fault Length Validity Fault Window Subrange Overlap Fault lnoamplete Block Transfer Fault Operand Validity Fault Forced Termination Fault Oopy Access Descriptor => Store Access Descriptor Faults Null Access Descriptor Destin[...]

  • Page 149

    iAPX 432 Interface Processor Architecture Reference Manual Retrieve Refined Object Refinement Control Object System Rights Fault => Object Qualification Faults (Refinement Ctl Obj) Source Object Validity Fault Type Fault => Store Access Descriptor Faults Inspect Access Descriptor no explicit fault cases Inspect Access Access Path Object Descr[...]

  • Page 150

    Broadcast be Processors Processor System Rights Fault => Object Qualification Faults (Processor AS) => Object Qualification Faults (CAXmDO Segment) Communication Segment Lock Fault Read Processor Status and Clock no explicit fault cases FAULT S'f.M.1ARY FF 01 0110 TS I 00000110 TS 00001010 FE' 01 1001 C-9[...]

  • Page 151

    iAPX 432 Interface Processor Architecture Reference Manual C-4. tOCN- INSTIUCTICN INTERFACE FAULTS OPERATOR Initialization => => Object Qualification Faults (processor AS) => Object Qualification Faults (object table directory) => Object Qualification Faults (processor OS) Processor Object Lock Fault => IPC Faults Base/Mask Incampati[...]

  • Page 152

    APPENDIX D INTERRUPT HANDLING ] Whenever the Interface Processor detects an event that may require attention from the IP controller, it records the nature of the event in the current IP processor data segment and e.mi ts a pulse on 1. ts interrupt line. There are several different types of events which may be sources of interrupts, and their occurr[...]

  • Page 153

    0-2 iAPX 432 Interface Processor Architecture Reference Manual yes Mask IP interrupt Reset latch Save interrupted environment Enable higher- priority . interrupts Restore interrupted environment Unmask IP interrupt C Return ) Respond to event Figure 0-1 Interrupt Handler Reset event indicator[...]

  • Page 154

    INTERRlJPI' HANDLING The central logic of this approach assumes that there is a "list" of poosible interrupt sources to be scanned, and that passing through this list may uncover one (the usual case), multiple, or zero events that require responses. To illustrate the second two cases, assume that the possible events are labelled A th[...]

  • Page 155

    iAPX 432 Interface Processor Architecture Reference Manual Processor Data Segment Subfield Function state field Table 0-1 Interrupt Sources Value Event Function completion state subfield OOOOs Function completed normally (this interrupt may be masked) Fault level subfield OIB Context-level fault lOs Process-level fault lIB Processor-level fault Ent[...]

  • Page 156

    APPENDIX E SYSTEM INITIALIZATICN System initialization may be considered as a sequence of activities that brings a 432-based system from an arbitrary state to a known state where execution can begin. Although the initialization sequence will vary widely among applications, this appendix outlines the basic procedure. The first section describes how [...]

  • Page 157

    iAPX 432 Interface Processor Architecture Reference Manual An Interface Processor responds to an INIT pulse by aborting any current operation, entering physical reference mode, configuring its windows as shown in table E-l, clear ing broadcast acceptance node, and then issuing an interrupt request to its Attached Processor. The interrupt request si[...]

  • Page 158

    SYSTEM INITIALIZATION L ~ Processor .... ,... .... ..., Object (n) Storage Descriptor (Processor Number n) Processor ~ ~ :: ~ Object (Processor Number 1) (1) Storage Descriptor ([I) Object Table Header ..... ~ Object Table J; 1 (1) Storage Descriptor ~ ([I) Object Table Header ~Physical Address 8 Initial Object Table Directory Figure E-l Processor [...]

  • Page 159

    iAPX 432 Interface Processor Architecture Reference Manual Note that the term "processor obj ect" above is meant to include ccmnunication segments, am a processor carrier, in addition to processor access and data segments. Likewise, "process object" includes a domain, instruction segments, context objects, etc. This environment [...]

  • Page 160

    SYSTEM INITIALIZATION Before any function request is made by the IP, enough 432 memory must be initialized to allCM Ip· execution. This is necessary because the IP will attempt to update the segment maWed by windCM 4 in response to the function request. Once this path to mennry has been established, windCM I can be opened onto another 32K byte seg[...]

  • Page 161

    iAPX 432 Interface Processor Architecture Reference Manual Having established its identity, the processor proceeds to locate its processor object. It does this by assuming that the initial object table directory is located at physical mennry address 8 (see figure E-I). A segment header field of eight bytes precedes the initial object table director[...]

  • Page 162

    SYSTEM INITIALIZATION Table E-l Window Configuration Following !NIT Attt"ibute WindCM 0 Window 1 WindCM 4 Window Status Open Open Open Transfer Mode Block Interconnect Random Subrange Base Address 07EOO H 08000H 07FOOH Subrange Size OOIOOH 08000H OOIOOH Segment Base 0 0 0 Segment Length 65,535 65,535 65,535 Direction Write Read/Write Read/Writ[...]

  • Page 163

    [...]

  • Page 164

    APPENDIX F INTERPROCESS CCMruNICATICN AND DISPA'lCHIt.;x; EXAMPLE In Chapter 1, a printer example was used to demonstrate the flow of data between 432 processes and AP tasks. In this appendix, the printer example is again discussed. However, this time the view taken is that of a programmer writing an Attached Processor task to direct an IP to [...]

  • Page 165

    F-2 iAPX 432 Interface Processor Architecture Reference Manual IP PROCESSOR OBJECT IP DISPATCHING PORT PRINT OBJECT CONTEXT PRINT REQUEST PORT 432 OBJECTS 432 PROCESS Figure F-l Print Example Objects IP AP PHYSICAL PROCESSORS[...]

  • Page 166

    INTERPIO::FSS mHlNlCATICN AND DISPA'lCHING EXAMPLE Procedures in the utilities section demonstrate how a programmer can construct facilities to invoke IP functions. Recall from the function sunmary in Aweooix B that an AP requests an IP function by writing a process selection index, all required operands, and finally depositing a function code[...]

  • Page 167

    iAPX 432 Interface Processor Architecture Reference Manual Printer task: Procedure: /*****~******************************************/ /* */ /* Data Structures and Constants * / /* */ /************************************************/ /**************************************************************************************/ /* Declare the 256 byte st[...]

  • Page 168

    INTERPR:nSS C(l.MJNICATICN AND DISPATCHING EXAMPLE /**************************************************************************************/ /* Seven object selectors are required. One for the message slot in the COntext */ /* Acx:ess Segment, sioce this is where the hardware will put the Access * / /* Descriptor (AD) for the Print Request Message f[...]

  • Page 169

    iAPX 432 Interface Processor Architecture Reference Manual Dispatch: Procedure~ /**********************************************************************************/ /* This procedure hangs the IP's processor carrier on the IP's dispatching */ /* port. This allcws blocking sends and receives to be handled.*/ 1* This example assumes that th[...]

  • Page 170

    INTERPRXESS exM-UNICATICN AND DISPA'ICHING EXAMPLE Get-print_message: Procedure: /**********************************************************************************/ /* Attempt to Receive a message fran the Print Request Port, Figure F-2 */ /**********************************************************************************/ W~ndow_4.frf-prcs_i[...]

  • Page 171

    iAPX 432 Interface Processor Architecture Reference Manual Clooe wirrlow: ProCedure~ /**********************************************************************************/ /* Close windCM, note only ~ operarrls are Ie<;uired. * / /**********************************************************************************/ Window_4.frf-prcs_idx Window 4. fr[...]

  • Page 172

    INTERP:rocESS CGMJNICATICN AND DISPATCHING EXAMPLE Return-print_message: Procedure; /**********************************************************************************/ /* Sem message to Print Reply Port. See Figure F-6 */ /**********************************************************************************/ W~ndow_4.frf-prcs_idx Window 4.frf.operand[...]

  • Page 173

    iAPX 432 Interface Processor Architecture Reference Manual /************************************************/ P ~ /* Initialization */ /* */ /*****************************************k******/ Call Disable_Interrupts: /* Busy waiting will be used, not the interrupt mechanism */ /* Also assume that 00 faults will occur */ Call Dispatch ~ /***********[...]

  • Page 174

    IP DISPATCHI G PORT INTERPROCESS a::MruNICATIGl AND DISPAroIING EXAMPLE IP OCESSOR PR o BJECT ~ IPI PR~ESS ~ iF c1r" PRINT REQUEST PORT (f4 CARRI~4 432 PROCESS ~. P P RINT REPLY ORT PRINT OBJECT IP Figure F-2 IP Performs Blocking Receive --EJ "RECEIVE" function F-ll[...]

  • Page 175

    iAPX 432 Interface Processor Architecture Reference Manual IP DISPATCHING PORT IP AP C~ .:- / -.tIo "c, / CARRIER - IP ~/ IP ~~/ 4 PROCESSOR PROCESS ~ /~<v OBJECT ~'v«;/': ~Cj/ / 1 / / / / ( I PRINT I PRINT REQUEST f REPLY PORT I PORT I , .. CARRIER I ...... ~ rJl I ~ 0 I J 432 PROCESS ..... PRINT OBJECT· Figure F- 3 GOP Execut[...]

  • Page 176

    INTERP~S ~ICATIrn AND DISPATCHING EXAMPLE INTERRUPT ,----, ;' ... 1/ '- IP AP IP -- A.~ SELECTED (- DISPATCHING v -v PORT STATE SELECTED INDEX £ARRIEB J IP IP -- PROCESSOR J PROCESS OBJECT - i PRINT PRINT REQUEST REPLY PORT PORT CARRIER STATE INDEX 432 PROCESS PRINT OBJECT Figure F-4 IP Resporrls to IPC F-13[...]

  • Page 177

    F-l4 iAPX 432 Interface Processor Architecture Reference Manual PRINT REQUEST PORT IP PROCESS - PRINT REPLY PORT ,fA CARRIE' (~ 432 PROCESS IP r ~ WINDOW III' ~ PRINT OBJECT ~ EJ "ALTER SELECT SEGMEN MAP AND DATA T" function Figure F-S Window Manipulation[...]

  • Page 178

    PRINT REQUEST PORT INTERPRXESS <XMvIDNICATIOO AND DISPATCHING EXAMPLE .-.--_/ IP .J PROCES, I f - - 432 PROCESS ,,- / PRINT REPLY PORT r I ,~ PRINT OBJECT IP ·SEND" function Figure F-6 Print Reply AP F-15[...]

  • Page 179

    [...]

  • Page 180

    infel" REQUEST FOR READER'S COMMENTS IAt-'X 40~ Interrace t-'rocessor Architecture Reference Manual 171863-001 Intel Corporation attempts to provide documents that meet the needs of all Intel product users. This form lets you participate directly in the documentation process. Please restrict your comments to the usabi lity, accu[...]

  • Page 181

    E'O LIKE YOUR COMMENTS ... lis document is one of a series describing Intel products. Your comments on the back of this form II help us produce better manuals. Each reply will be carefully reviewed by the responsible rson. All comments and suggestions become the property of Intel Corporation. BUSINESS REPLY MAIL FIRST CLASS PERMIT NO. 79 BEAVE[...]

  • Page 182

    inter INTEL CORPORATION, 3585 SW 198th Avenue , Aloha , Oregon 97007 • (503) 681-8080 Printed in U,SA1Y63 / 1 K / 0781 1 AP[...]