Commit 43c9d459 authored by Martin Schwidefsky's avatar Martin Schwidefsky Committed by Linus Torvalds

[PATCH] s/390 patches for 2.5.20 (4 of 4).

Fourth and last part of the s/390 update. Docu stuff.
parent 10e294df
...@@ -21,7 +21,8 @@ Command line parameters ...@@ -21,7 +21,8 @@ Command line parameters
Default is on. Default is on.
* cio_ignore = <range of device numbers>, <range of device numbers>, ... * cio_ignore = <device number> | <range of device numbers>,
<device number> | <range of device numbers>, ...
The given device numbers will be ignored by the common I/O-layer; no detection The given device numbers 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 and device sensing will be done on any of those devices. The subchannel to
...@@ -41,45 +42,27 @@ Command line parameters ...@@ -41,45 +42,27 @@ Command line parameters
By default, no devices are ignored. By default, no devices are ignored.
* cio_proc_devinfo = yes | no
Determines whether the entries under /proc/deviceinfo/ (see below) should be
created. Since there are problems with systems with many devices attached, I
made it configurable.
Until the problems are dealt with, default is off.
/proc entries /proc entries
------------- -------------
* /proc/subchannels * /proc/subchannels
Shows for each subchannel This entry shows information on a per-subchannel basis.
- device number
- device type/model and if applicable control unit type/model
- whether the device is in use
- path installed mask, path available mask, path operational mask and last
path used mask
- the channel path IDs (chpids)
* /proc/deviceinfo/ The data is ordered in the following way:
Shows in subdirectories for each device some characteristics: - device number
- /proc/deviceinfo/<devno>/chpids: - subchannel number
the channel path IDs - device type/model (if applicable; if not, this is empty) and control unit
- /proc/deviceinfo/<devno>/in_use: type/model
whether the device is in use - whether the device is in use (i. e. a device driver has requested ownership
- /proc/deviceinfo/<devno>/sensedata: and registered an interrupt handler)
the device type/model and if applicable control unit type/model of the - path installed mask (PIM), as reflected by last store subchannel
device - path available mask (PAM), as reflected by last store subchannel
- path operational mask (POM), as reflected by last store subchannel
- the channel path IDs (CHPIDs)
NOTE: Since the number of inodes which can be dynamically allocated by procfs All fields are separated by spaces, the chpids are in blocks of four chpids.
is limited, device entries will only be created up to a magic number of
devices. The kernel will utter a warning that not all entries can be
created. In this case, you shouldn't use "cio_proc_devinfo=yes" (see
above).
* /proc/cio_ignore * /proc/cio_ignore
...@@ -137,3 +120,26 @@ Command line parameters ...@@ -137,3 +120,26 @@ Command line parameters
This entry counts how many times s390_process_IRQ has been called for each This entry counts how many times s390_process_IRQ has been called for each
CPU. This info is in /proc/interrupts on other architectures. CPU. This info is in /proc/interrupts on other architectures.
* /proc/chpids
This entry will only show up if you specified CONFIG_CHSC=y during kernel
config.
This entry serves a dual purpose:
- show which chpids are currently known to Linux and their status (online,
logically offline),
- toggling known chpids logically online/offline.
To toggle a known chpid logically offline, do an
echo off <chpid> > /proc/chpids
<chpid> is interpreted as hex, even if you omit the '0x'.
The chpid will be treated by Linux as if it were not online, which can mean
some devices will become unavailable.
You can toggle a logically offline chpid online again by
echo on <chpid> > /proc/chpids
If devices became unavailable by toggling the chpid logically offline, they
will become available again after you toggle the chpid online again.
...@@ -237,9 +237,10 @@ they go to 64 Bit. ...@@ -237,9 +237,10 @@ they go to 64 Bit.
On 390 our limitations & strengths make us slightly different. On 390 our limitations & strengths make us slightly different.
For backward compatibility we are only allowed use 31 bits (2GB) For backward compatibility ( because of the psw address hi bit which
of our 32 bit addresses,however, we use entirely separate address indicates whether we are in 31 or 24 bit mode ) we are only allowed
spaces for the user & kernel. use 31 bits (2GB) of our 32 bit addresses. However,
we use entirely separate address spaces for the user & kernel.
This means we can support 2GB of non Extended RAM on s/390, & more This means we can support 2GB of non Extended RAM on s/390, & more
with the Extended memory managment swap device & with the Extended memory managment swap device &
...@@ -1474,6 +1475,12 @@ Now display what gpr2 is pointing to ...@@ -1474,6 +1475,12 @@ Now display what gpr2 is pointing to
D 00014CB4.20 D 00014CB4.20
V00014CB4 2F646576 2F636F6E 736F6C65 00001BF5 V00014CB4 2F646576 2F636F6E 736F6C65 00001BF5
V00014CC4 FC00014C B4001001 E0001000 B8070707 V00014CC4 FC00014C B4001001 E0001000 B8070707
Alternatively you can do the more elegant
D 0.20;BASE2
BASE2 telling VM to use GPR2 as the base register.
Now copy the text till the first 00 hex ( which is the end of the string Now copy the text till the first 00 hex ( which is the end of the string
to an xterm & do hex2ascii on it. to an xterm & do hex2ascii on it.
hex2ascii 2F646576 2F636F6E 736F6C65 00 hex2ascii 2F646576 2F636F6E 736F6C65 00
...@@ -2124,6 +2131,12 @@ now do ...@@ -2124,6 +2131,12 @@ now do
p/x (*(**$sp+56))&0x7fffffff p/x (*(**$sp+56))&0x7fffffff
& so on. & so on.
Another good trick to look at addresses on the stack if you've somehow lost
the backchain is.
x/500xa $sp
This displays anything the name of any known functions above the stack pointer
for 500 bytes.
Disassembling instructions without debug info Disassembling instructions without debug info
--------------------------------------------- ---------------------------------------------
gdb typically compains if there is a lack of debugging gdb typically compains if there is a lack of debugging
......
This diff is collapsed.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment