diff options
| author | Christian Borntraeger <borntraeger@de.ibm.com> | 2009-11-13 15:43:54 +0100 |
|---|---|---|
| committer | Martin Schwidefsky <sky@mschwide.boeblingen.de.ibm.com> | 2009-11-13 15:45:03 +0100 |
| commit | bcc6525fb23d2cec7ffdf908d98826a66823bcb2 (patch) | |
| tree | bf5bc71446c3ad861db386ca68e9221309f6ca8b /mm | |
| parent | 8b94c1ed4d8232a452aa9db0f5ac9141d942590f (diff) | |
| download | lwn-bcc6525fb23d2cec7ffdf908d98826a66823bcb2.tar.gz lwn-bcc6525fb23d2cec7ffdf908d98826a66823bcb2.zip | |
[S390] s390: fix single stepping on svc0
On s390 there are two ways of specifying the system call number for
the svc instruction. The standard way is to use the immediate field
in the instruction (or to use EXecute for values unknown during
assemble time). This can encode 256 system calls.
The kernel ABI also allows to put the system call number in r1 and
then execute svc 0 to enable system call numbers > 255.
It turns out that single stepping svc 0 is broken, since the PER
program check handler uses r1. We have to use a different register.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions