Lines Matching refs:IO

13 390 IO in any detail. It is intended to complement the documents in the
30 s/390 & z/Architecture IO Overview
31 Debugging IO on s/390 & z/Architecture under VM
389 Thankfully because Linux doesn't have support for nested IO interrupts
1043 till a driver is open before you start tracing IO, but know in your
1053 TR IO 7c08-7c09 inst int run
1054 or whatever the IO channels you wish to trace are & hit b
1084 If you are running on a guest with several cpus & you have a IO related problem
1293 s/390 & z/Architecture IO Overview
1296 I am not going to give a course in 390 IO architecture as this would take me
1297 quite a while and I'm no expert. Instead I'll give a 390 IO architecture
1302 Unlike other bus architectures modern 390 systems do their IO using mostly
1307 Here is some of the common IO terminology:
1310 This is the logical number most IO commands use to talk to an IO device. There
1315 Under Linux for s390 we use these as IRQ's and also when issuing an IO command
1319 START SUBCHANNEL (to start IO), TEST SUBCHANNEL (to check whether the IO
1320 completed successfully) and HALT SUBCHANNEL (to kill IO). A subchannel can have
1334 command along with the subchannel number for the IO subsystem to process
1340 Each IO typically gets 1 or 2 interrupts, one for channel end (primary status)
1342 Sometimes you get both concurrently. You check how the IO went on by issuing a
1345 without channel checks etc. your IO probably went okay. If you didn't you
1353 TPI (Test pending interrupt) can also be used for polled IO, but in
1355 checking special cases (i.e. non looping checks for pending IO etc.).
1360 Other IO related Terms:
1362 QDIO: S390's new high speed IO architecture to support devices such as gigabit
1371 burden of communicating with IO devices directly, this allows the CPU's to
1375 IO device. It first checks for path availability & chooses an available one,
1376 then starts ( & sometimes terminates IO ).
1377 There are two types of channel path: ESCON & the Parallel IO interface.
1379 IO devices are attached to control units, control units provide the
1380 logic to interface the channel paths & channel path IO protocols to
1381 the IO devices, they can be integrated with the devices or housed separately
1414 The 390 IO systems come in 2 flavours the current 390 machines support both
1457 Debugging IO on s/390 & z/Architecture under VM
1460 Now we are ready to go on with IO tracing commands under VM
1493 A good trick is tracing all the IO's and CCWS and spooling them into the reader
1500 TR IO 7c08-7c09 INST INT CCW PRT RUN