CommonIO 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111
  1. S/390 common I/O-Layer - command line parameters and /proc entries
  2. ==================================================================
  3. Command line parameters
  4. -----------------------
  5. * cio_msg = yes | no
  6. Determines whether information on found devices and sensed device
  7. characteristics should be shown during startup, i. e. messages of the types
  8. "Detected device 0.0.4711 on subchannel 0.0.0042" and "SenseID: Device
  9. 0.0.4711 reports: ...".
  10. Default is off.
  11. * cio_ignore = {all} |
  12. {<device> | <range of devices>} |
  13. {!<device> | !<range of devices>}
  14. The given devices will be ignored by the common I/O-layer; no detection
  15. and device sensing will be done on any of those devices. The subchannel to
  16. which the device in question is attached will be treated as if no device was
  17. attached.
  18. An ignored device can be un-ignored later; see the "/proc entries"-section for
  19. details.
  20. The devices must be given either as bus ids (0.0.abcd) or as hexadecimal
  21. device numbers (0xabcd or abcd, for 2.4 backward compatibility).
  22. You can use the 'all' keyword to ignore all devices.
  23. The '!' operator will cause the I/O-layer to _not_ ignore a device.
  24. The command line is parsed from left to right.
  25. For example,
  26. cio_ignore=0.0.0023-0.0.0042,0.0.4711
  27. will ignore all devices ranging from 0.0.0023 to 0.0.0042 and the device
  28. 0.0.4711, if detected.
  29. As another example,
  30. cio_ignore=all,!0.0.4711,!0.0.fd00-0.0.fd02
  31. will ignore all devices but 0.0.4711, 0.0.fd00, 0.0.fd01, 0.0.fd02.
  32. By default, no devices are ignored.
  33. /proc entries
  34. -------------
  35. * /proc/cio_ignore
  36. Lists the ranges of devices (by bus id) which are ignored by common I/O.
  37. You can un-ignore certain or all devices by piping to /proc/cio_ignore.
  38. "free all" will un-ignore all ignored devices,
  39. "free <device range>, <device range>, ..." will un-ignore the specified
  40. devices.
  41. For example, if devices 0.0.0023 to 0.0.0042 and 0.0.4711 are ignored,
  42. - echo free 0.0.0030-0.0.0032 > /proc/cio_ignore
  43. will un-ignore devices 0.0.0030 to 0.0.0032 and will leave devices 0.0.0023
  44. to 0.0.002f, 0.0.0033 to 0.0.0042 and 0.0.4711 ignored;
  45. - echo free 0.0.0041 > /proc/cio_ignore will furthermore un-ignore device
  46. 0.0.0041;
  47. - echo free all > /proc/cio_ignore will un-ignore all remaining ignored
  48. devices.
  49. When a device is un-ignored, device recognition and sensing is performed and
  50. the device driver will be notified if possible, so the device will become
  51. available to the system.
  52. You can also add ranges of devices to be ignored by piping to
  53. /proc/cio_ignore; "add <device range>, <device range>, ..." will ignore the
  54. specified devices.
  55. Note: While already known devices can be added to the list of devices to be
  56. ignored, there will be no effect on then. However, if such a device
  57. disappears and then reappeares, it will then be ignored.
  58. For example,
  59. "echo add 0.0.a000-0.0.accc, 0.0.af00-0.0.afff > /proc/cio_ignore"
  60. will add 0.0.a000-0.0.accc and 0.0.af00-0.0.afff to the list of ignored
  61. devices.
  62. The devices can be specified either by bus id (0.0.abcd) or, for 2.4 backward
  63. compatibilty, by the device number in hexadecimal (0xabcd or abcd).
  64. * /proc/s390dbf/cio_*/ (S/390 debug feature)
  65. Some views generated by the debug feature to hold various debug outputs.
  66. - /proc/s390dbf/cio_crw/sprintf
  67. Messages from the processing of pending channel report words (machine check
  68. handling), which will also show when CONFIG_DEBUG_CRW is defined.
  69. - /proc/s390dbf/cio_msg/sprintf
  70. Various debug messages from the common I/O-layer; generally, messages which
  71. will also show when CONFIG_DEBUG_IO is defined.
  72. - /proc/s390dbf/cio_trace/hex_ascii
  73. Logs the calling of functions in the common I/O-layer and, if applicable,
  74. which subchannel they were called for, as well as dumps of some data
  75. structures (like irb in an error case).
  76. The level of logging can be changed to be more or less verbose by piping to
  77. /proc/s390dbf/cio_*/level a number between 0 and 6; see the documentation on
  78. the S/390 debug feature (Documentation/s390/s390dbf.txt) for details.
  79. * For some of the information present in the /proc filesystem in 2.4 (namely,
  80. /proc/subchannels and /proc/chpids), see driver-model.txt.
  81. Information formerly in /proc/irq_count is now in /proc/interrupts.