€•:d      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ'/translations/zh_CN/arch/s390/common_io”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/zh_TW/arch/s390/common_io”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/it_IT/arch/s390/common_io”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/ja_JP/arch/s390/common_io”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/ko_KR/arch/s390/common_io”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ'/translations/sp_SP/arch/s390/common_io”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒS/390 common I/O-Layer”h]”hŒS/390 common I/O-Layer”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒA/var/lib/git/docbuild/linux/Documentation/arch/s390/common_io.rst”h Kubh¢)”}”(hhh]”(h§)”}”(hŒ3command line parameters, procfs and debugfs entries”h]”hŒ3command line parameters, procfs and debugfs entries”…””}”(hhºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh·hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒCommand line parameters”h]”hŒCommand line parameters”…””}”(hhËhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhÈhžhhŸh¶h K	ubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒUccw_timeout_log

Enable logging of debug information in case of ccw device timeouts.
”h]”(hŒ	paragraph”“”)”}”(hŒccw_timeout_log”h]”hŒccw_timeout_log”…””}”(hhæhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khhàubhå)”}”(hŒCEnable logging of debug information in case of ccw device timeouts.”h]”hŒCEnable logging of debug information in case of ccw device timeouts.”…””}”(hhôhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khhàubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÞhhÛhžhhŸh¶h Nubhß)”}”(hXC  cio_ignore = device[,device[,..]]

      device := {all | [!]ipldev | [!]condev | [!]<devno> | [!]<devno>-<devno>}

The given devices will be ignored by the common I/O-layer; no detection
and device sensing will be done on any of those devices. The subchannel to
which the device in question is attached will be treated as if no device was
attached.

An ignored device can be un-ignored later; see the "/proc entries"-section for
details.

The devices must be given either as bus ids (0.x.abcd) or as hexadecimal
device numbers (0xabcd or abcd, for 2.4 backward compatibility). If you
give a device number 0xabcd, it will be interpreted as 0.0.abcd.

You can use the 'all' keyword to ignore all devices. The 'ipldev' and 'condev'
keywords can be used to refer to the CCW based boot device and CCW console
device respectively (these are probably useful only when combined with the '!'
operator). The '!' operator will cause the I/O-layer to _not_ ignore a device.
The command line
is parsed from left to right.

For example::

      cio_ignore=0.0.0023-0.0.0042,0.0.4711

will ignore all devices ranging from 0.0.0023 to 0.0.0042 and the device
0.0.4711, if detected.

As another example::

      cio_ignore=all,!0.0.4711,!0.0.fd00-0.0.fd02

will ignore all devices but 0.0.4711, 0.0.fd00, 0.0.fd01, 0.0.fd02.

By default, no devices are ignored.

”h]”(hå)”}”(hŒ!cio_ignore = device[,device[,..]]”h]”hŒ!cio_ignore = device[,device[,..]]”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khj  ubhŒblock_quote”“”)”}”(hŒJdevice := {all | [!]ipldev | [!]condev | [!]<devno> | [!]<devno>-<devno>}
”h]”hå)”}”(hŒIdevice := {all | [!]ipldev | [!]condev | [!]<devno> | [!]<devno>-<devno>}”h]”hŒIdevice := {all | [!]ipldev | [!]condev | [!]<devno> | [!]<devno>-<devno>}”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j  hŸh¶h Khj  ubhå)”}”(hŒéThe given devices will be ignored by the common I/O-layer; no detection
and device sensing will be done on any of those devices. The subchannel to
which the device in question is attached will be treated as if no device was
attached.”h]”hŒéThe given devices will be ignored by the common I/O-layer; no detection
and device sensing will be done on any of those devices. The subchannel to
which the device in question is attached will be treated as if no device was
attached.”…””}”(hj4  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khj  ubhå)”}”(hŒWAn ignored device can be un-ignored later; see the "/proc entries"-section for
details.”h]”hŒ[An ignored device can be un-ignored later; see the â€œ/proc entriesâ€-section for
details.”…””}”(hjB  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khj  ubhå)”}”(hŒÑThe devices must be given either as bus ids (0.x.abcd) or as hexadecimal
device numbers (0xabcd or abcd, for 2.4 backward compatibility). If you
give a device number 0xabcd, it will be interpreted as 0.0.abcd.”h]”hŒÑThe devices must be given either as bus ids (0.x.abcd) or as hexadecimal
device numbers (0xabcd or abcd, for 2.4 backward compatibility). If you
give a device number 0xabcd, it will be interpreted as 0.0.abcd.”…””}”(hjP  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khj  ubhå)”}”(hXf  You can use the 'all' keyword to ignore all devices. The 'ipldev' and 'condev'
keywords can be used to refer to the CCW based boot device and CCW console
device respectively (these are probably useful only when combined with the '!'
operator). The '!' operator will cause the I/O-layer to _not_ ignore a device.
The command line
is parsed from left to right.”h]”hXz  You can use the â€˜allâ€™ keyword to ignore all devices. The â€˜ipldevâ€™ and â€˜condevâ€™
keywords can be used to refer to the CCW based boot device and CCW console
device respectively (these are probably useful only when combined with the â€˜!â€™
operator). The â€˜!â€™ operator will cause the I/O-layer to _not_ ignore a device.
The command line
is parsed from left to right.”…””}”(hj^  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khj  ubhå)”}”(hŒFor example::”h]”hŒFor example:”…””}”(hjl  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K&hj  ubhŒliteral_block”“”)”}”(hŒ%cio_ignore=0.0.0023-0.0.0042,0.0.4711”h]”hŒ%cio_ignore=0.0.0023-0.0.0042,0.0.4711”…””}”hj|  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1jz  hŸh¶h K(hj  ubhå)”}”(hŒ_will ignore all devices ranging from 0.0.0023 to 0.0.0042 and the device
0.0.4711, if detected.”h]”hŒ_will ignore all devices ranging from 0.0.0023 to 0.0.0042 and the device
0.0.4711, if detected.”…””}”(hjŒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K*hj  ubhå)”}”(hŒAs another example::”h]”hŒAs another example:”…””}”(hjš  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K-hj  ubj{  )”}”(hŒ+cio_ignore=all,!0.0.4711,!0.0.fd00-0.0.fd02”h]”hŒ+cio_ignore=all,!0.0.4711,!0.0.fd00-0.0.fd02”…””}”hj¨  sbah}”(h]”h ]”h"]”h$]”h&]”jŠ  j‹  uh1jz  hŸh¶h K/hj  ubhå)”}”(hŒCwill ignore all devices but 0.0.4711, 0.0.fd00, 0.0.fd01, 0.0.fd02.”h]”hŒCwill ignore all devices but 0.0.4711, 0.0.fd00, 0.0.fd01, 0.0.fd02.”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K1hj  ubhå)”}”(hŒ#By default, no devices are ignored.”h]”hŒ#By default, no devices are ignored.”…””}”(hjÄ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K3hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÞhhÛhžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1hÙhŸh¶h KhhÈhžhubeh}”(h]”Œcommand-line-parameters”ah ]”h"]”Œcommand line parameters”ah$]”h&]”uh1h¡hh·hžhhŸh¶h K	ubh¢)”}”(hhh]”(h§)”}”(hŒ/proc entries”h]”hŒ/proc entries”…””}”(hjë  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjè  hžhhŸh¶h K7ubhÚ)”}”(hhh]”(hß)”}”(hXÖ  /proc/cio_ignore

Lists the ranges of devices (by bus id) which are ignored by common I/O.

You can un-ignore certain or all devices by piping to /proc/cio_ignore.
"free all" will un-ignore all ignored devices,
"free <device range>, <device range>, ..." will un-ignore the specified
devices.

For example, if devices 0.0.0023 to 0.0.0042 and 0.0.4711 are ignored,

- echo free 0.0.0030-0.0.0032 > /proc/cio_ignore
  will un-ignore devices 0.0.0030 to 0.0.0032 and will leave devices 0.0.0023
  to 0.0.002f, 0.0.0033 to 0.0.0042 and 0.0.4711 ignored;
- echo free 0.0.0041 > /proc/cio_ignore will furthermore un-ignore device
  0.0.0041;
- echo free all > /proc/cio_ignore will un-ignore all remaining ignored
  devices.

When a device is un-ignored, device recognition and sensing is performed and
the device driver will be notified if possible, so the device will become
available to the system. Note that un-ignoring is performed asynchronously.

You can also add ranges of devices to be ignored by piping to
/proc/cio_ignore; "add <device range>, <device range>, ..." will ignore the
specified devices.

Note: While already known devices can be added to the list of devices to be
      ignored, there will be no effect on then. However, if such a device
      disappears and then reappears, it will then be ignored. To make
      known devices go away, you need the "purge" command (see below).

For example::

      "echo add 0.0.a000-0.0.accc, 0.0.af00-0.0.afff > /proc/cio_ignore"

will add 0.0.a000-0.0.accc and 0.0.af00-0.0.afff to the list of ignored
devices.

You can remove already known but now ignored devices via::

      "echo purge > /proc/cio_ignore"

All devices ignored but still registered and not online (= not in use)
will be deregistered and thus removed from the system.

The devices can be specified either by bus id (0.x.abcd) or, for 2.4 backward
compatibility, by the device number in hexadecimal (0xabcd or abcd). Device
numbers given as 0xabcd will be interpreted as 0.0.abcd.
”h]”(hå)”}”(hŒ/proc/cio_ignore”h]”hŒ/proc/cio_ignore”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K9hjü  ubhå)”}”(hŒHLists the ranges of devices (by bus id) which are ignored by common I/O.”h]”hŒHLists the ranges of devices (by bus id) which are ignored by common I/O.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K;hjü  ubhå)”}”(hŒÇYou can un-ignore certain or all devices by piping to /proc/cio_ignore.
"free all" will un-ignore all ignored devices,
"free <device range>, <device range>, ..." will un-ignore the specified
devices.”h]”hŒÏYou can un-ignore certain or all devices by piping to /proc/cio_ignore.
â€œfree allâ€ will un-ignore all ignored devices,
â€œfree <device range>, <device range>, ...â€ will un-ignore the specified
devices.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K=hjü  ubhå)”}”(hŒFFor example, if devices 0.0.0023 to 0.0.0042 and 0.0.4711 are ignored,”h]”hŒFFor example, if devices 0.0.0023 to 0.0.0042 and 0.0.4711 are ignored,”…””}”(hj*  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KBhjü  ubhÚ)”}”(hhh]”(hß)”}”(hŒ²echo free 0.0.0030-0.0.0032 > /proc/cio_ignore
will un-ignore devices 0.0.0030 to 0.0.0032 and will leave devices 0.0.0023
to 0.0.002f, 0.0.0033 to 0.0.0042 and 0.0.4711 ignored;”h]”hå)”}”(hŒ²echo free 0.0.0030-0.0.0032 > /proc/cio_ignore
will un-ignore devices 0.0.0030 to 0.0.0032 and will leave devices 0.0.0023
to 0.0.002f, 0.0.0033 to 0.0.0042 and 0.0.4711 ignored;”h]”hŒ²echo free 0.0.0030-0.0.0032 > /proc/cio_ignore
will un-ignore devices 0.0.0030 to 0.0.0032 and will leave devices 0.0.0023
to 0.0.002f, 0.0.0033 to 0.0.0042 and 0.0.4711 ignored;”…””}”(hj?  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KDhj;  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÞhj8  ubhß)”}”(hŒQecho free 0.0.0041 > /proc/cio_ignore will furthermore un-ignore device
0.0.0041;”h]”hå)”}”(hŒQecho free 0.0.0041 > /proc/cio_ignore will furthermore un-ignore device
0.0.0041;”h]”hŒQecho free 0.0.0041 > /proc/cio_ignore will furthermore un-ignore device
0.0.0041;”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KGhjS  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÞhj8  ubhß)”}”(hŒOecho free all > /proc/cio_ignore will un-ignore all remaining ignored
devices.
”h]”hå)”}”(hŒNecho free all > /proc/cio_ignore will un-ignore all remaining ignored
devices.”h]”hŒNecho free all > /proc/cio_ignore will un-ignore all remaining ignored
devices.”…””}”(hjo  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KIhjk  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÞhj8  ubeh}”(h]”h ]”h"]”h$]”h&]”jÞ  Œ-”uh1hÙhŸh¶h KDhjü  ubhå)”}”(hŒâWhen a device is un-ignored, device recognition and sensing is performed and
the device driver will be notified if possible, so the device will become
available to the system. Note that un-ignoring is performed asynchronously.”h]”hŒâWhen a device is un-ignored, device recognition and sensing is performed and
the device driver will be notified if possible, so the device will become
available to the system. Note that un-ignoring is performed asynchronously.”…””}”(hjŠ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KLhjü  ubhå)”}”(hŒœYou can also add ranges of devices to be ignored by piping to
/proc/cio_ignore; "add <device range>, <device range>, ..." will ignore the
specified devices.”h]”hŒ You can also add ranges of devices to be ignored by piping to
/proc/cio_ignore; â€œadd <device range>, <device range>, ...â€ will ignore the
specified devices.”…””}”(hj˜  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KPhjü  ubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hX  Note: While already known devices can be added to the list of devices to be
ignored, there will be no effect on then. However, if such a device
disappears and then reappears, it will then be ignored. To make
known devices go away, you need the "purge" command (see below).
”h]”(hŒterm”“”)”}”(hŒKNote: While already known devices can be added to the list of devices to be”h]”hŒKNote: While already known devices can be added to the list of devices to be”…””}”(hj³  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j±  hŸh¶h KWhj­  ubhŒ
definition”“”)”}”(hhh]”hå)”}”(hŒÄignored, there will be no effect on then. However, if such a device
disappears and then reappears, it will then be ignored. To make
known devices go away, you need the "purge" command (see below).”h]”hŒÈignored, there will be no effect on then. However, if such a device
disappears and then reappears, it will then be ignored. To make
known devices go away, you need the â€œpurgeâ€ command (see below).”…””}”(hjÆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KUhjÃ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÁ  hj­  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j«  hŸh¶h KWhj¨  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¦  hjü  ubhå)”}”(hŒFor example::”h]”hŒFor example:”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KYhjü  ubj{  )”}”(hŒB"echo add 0.0.a000-0.0.accc, 0.0.af00-0.0.afff > /proc/cio_ignore"”h]”hŒB"echo add 0.0.a000-0.0.accc, 0.0.af00-0.0.afff > /proc/cio_ignore"”…””}”hjô  sbah}”(h]”h ]”h"]”h$]”h&]”jŠ  j‹  uh1jz  hŸh¶h K[hjü  ubhå)”}”(hŒPwill add 0.0.a000-0.0.accc and 0.0.af00-0.0.afff to the list of ignored
devices.”h]”hŒPwill add 0.0.a000-0.0.accc and 0.0.af00-0.0.afff to the list of ignored
devices.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K]hjü  ubhå)”}”(hŒ:You can remove already known but now ignored devices via::”h]”hŒ9You can remove already known but now ignored devices via:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K`hjü  ubj{  )”}”(hŒ"echo purge > /proc/cio_ignore"”h]”hŒ"echo purge > /proc/cio_ignore"”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”jŠ  j‹  uh1jz  hŸh¶h Kbhjü  ubhå)”}”(hŒ}All devices ignored but still registered and not online (= not in use)
will be deregistered and thus removed from the system.”h]”hŒ}All devices ignored but still registered and not online (= not in use)
will be deregistered and thus removed from the system.”…””}”(hj,  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Kdhjü  ubhå)”}”(hŒÒThe devices can be specified either by bus id (0.x.abcd) or, for 2.4 backward
compatibility, by the device number in hexadecimal (0xabcd or abcd). Device
numbers given as 0xabcd will be interpreted as 0.0.abcd.”h]”hŒÒThe devices can be specified either by bus id (0.x.abcd) or, for 2.4 backward
compatibility, by the device number in hexadecimal (0xabcd or abcd). Device
numbers given as 0xabcd will be interpreted as 0.0.abcd.”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Kghjü  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÞhjù  hžhhŸh¶h Nubhß)”}”(hŒî/proc/cio_settle

A write request to this file is blocked until all queued cio actions are
handled. This will allow userspace to wait for pending work affecting
device availability after changing cio_ignore or the hardware configuration.
”h]”(hå)”}”(hŒ/proc/cio_settle”h]”hŒ/proc/cio_settle”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KkhjN  ubhå)”}”(hŒÛA write request to this file is blocked until all queued cio actions are
handled. This will allow userspace to wait for pending work affecting
device availability after changing cio_ignore or the hardware configuration.”h]”hŒÛA write request to this file is blocked until all queued cio actions are
handled. This will allow userspace to wait for pending work affecting
device availability after changing cio_ignore or the hardware configuration.”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h KmhjN  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÞhjù  hžhhŸh¶h Nubhß)”}”(hŒÌFor some of the information present in the /proc filesystem in 2.4 (namely,
/proc/subchannels and /proc/chpids), see driver-model.txt.
Information formerly in /proc/irq_count is now in /proc/interrupts.

”h]”hå)”}”(hŒÊFor some of the information present in the /proc filesystem in 2.4 (namely,
/proc/subchannels and /proc/chpids), see driver-model.txt.
Information formerly in /proc/irq_count is now in /proc/interrupts.”h]”hŒÊFor some of the information present in the /proc filesystem in 2.4 (namely,
/proc/subchannels and /proc/chpids), see driver-model.txt.
Information formerly in /proc/irq_count is now in /proc/interrupts.”…””}”(hjx  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Kqhjt  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÞhjù  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jÞ  jß  uh1hÙhŸh¶h K9hjè  hžhubeh}”(h]”Œproc-entries”ah ]”h"]”Œ/proc entries”ah$]”h&]”uh1h¡hh·hžhhŸh¶h K7ubh¢)”}”(hhh]”(h§)”}”(hŒdebugfs entries”h]”hŒdebugfs entries”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjš  hžhhŸh¶h KwubhÚ)”}”(hhh]”hß)”}”(hXH  /sys/kernel/debug/s390dbf/cio_*/ (S/390 debug feature)

Some views generated by the debug feature to hold various debug outputs.

- /sys/kernel/debug/s390dbf/cio_crw/sprintf
  Messages from the processing of pending channel report words (machine check
  handling).

- /sys/kernel/debug/s390dbf/cio_msg/sprintf
  Various debug messages from the common I/O-layer.

- /sys/kernel/debug/s390dbf/cio_trace/hex_ascii
  Logs the calling of functions in the common I/O-layer and, if applicable,
  which subchannel they were called for, as well as dumps of some data
  structures (like irb in an error case).

The level of logging can be changed to be more or less verbose by piping to
/sys/kernel/debug/s390dbf/cio_*/level a number between 0 and 6; see the
documentation on the S/390 debug feature (Documentation/arch/s390/s390dbf.rst)
for details.”h]”(hå)”}”(hŒ6/sys/kernel/debug/s390dbf/cio_*/ (S/390 debug feature)”h]”hŒ6/sys/kernel/debug/s390dbf/cio_*/ (S/390 debug feature)”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Kyhj®  ubhå)”}”(hŒHSome views generated by the debug feature to hold various debug outputs.”h]”hŒHSome views generated by the debug feature to hold various debug outputs.”…””}”(hjÀ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K{hj®  ubhÚ)”}”(hhh]”(hß)”}”(hŒ/sys/kernel/debug/s390dbf/cio_crw/sprintf
Messages from the processing of pending channel report words (machine check
handling).
”h]”hå)”}”(hŒ€/sys/kernel/debug/s390dbf/cio_crw/sprintf
Messages from the processing of pending channel report words (machine check
handling).”h]”hŒ€/sys/kernel/debug/s390dbf/cio_crw/sprintf
Messages from the processing of pending channel report words (machine check
handling).”…””}”(hjÕ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K}hjÑ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÞhjÎ  ubhß)”}”(hŒ\/sys/kernel/debug/s390dbf/cio_msg/sprintf
Various debug messages from the common I/O-layer.
”h]”hå)”}”(hŒ[/sys/kernel/debug/s390dbf/cio_msg/sprintf
Various debug messages from the common I/O-layer.”h]”hŒ[/sys/kernel/debug/s390dbf/cio_msg/sprintf
Various debug messages from the common I/O-layer.”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h Khjé  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÞhjÎ  ubhß)”}”(hŒå/sys/kernel/debug/s390dbf/cio_trace/hex_ascii
Logs the calling of functions in the common I/O-layer and, if applicable,
which subchannel they were called for, as well as dumps of some data
structures (like irb in an error case).
”h]”hå)”}”(hŒä/sys/kernel/debug/s390dbf/cio_trace/hex_ascii
Logs the calling of functions in the common I/O-layer and, if applicable,
which subchannel they were called for, as well as dumps of some data
structures (like irb in an error case).”h]”hŒä/sys/kernel/debug/s390dbf/cio_trace/hex_ascii
Logs the calling of functions in the common I/O-layer and, if applicable,
which subchannel they were called for, as well as dumps of some data
structures (like irb in an error case).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K„hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÞhjÎ  ubeh}”(h]”h ]”h"]”h$]”h&]”jÞ  j‰  uh1hÙhŸh¶h K}hj®  ubhå)”}”(hŒïThe level of logging can be changed to be more or less verbose by piping to
/sys/kernel/debug/s390dbf/cio_*/level a number between 0 and 6; see the
documentation on the S/390 debug feature (Documentation/arch/s390/s390dbf.rst)
for details.”h]”hŒïThe level of logging can be changed to be more or less verbose by piping to
/sys/kernel/debug/s390dbf/cio_*/level a number between 0 and 6; see the
documentation on the S/390 debug feature (Documentation/arch/s390/s390dbf.rst)
for details.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hähŸh¶h K‰hj®  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÞhj«  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”jÞ  jß  uh1hÙhŸh¶h Kyhjš  hžhubeh}”(h]”Œdebugfs-entries”ah ]”h"]”Œdebugfs entries”ah$]”h&]”uh1h¡hh·hžhhŸh¶h Kwubeh}”(h]”Œ2command-line-parameters-procfs-and-debugfs-entries”ah ]”h"]”Œ3command line parameters, procfs and debugfs entries”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubeh}”(h]”Œs-390-common-i-o-layer”ah ]”h"]”Œs/390 common i/o-layer”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jt  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jN  jK  jF  jC  jå  jâ  j—  j”  j>  j;  uŒ	nametypes”}”(jN  ‰jF  ‰jå  ‰j—  ‰j>  ‰uh}”(jK  h£jC  h·jâ  hÈj”  jè  j;  jš  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.