diff options
author | Michael Cree <mcree@orcon.net.nz> | 2009-11-30 22:44:40 -0500 |
---|---|---|
committer | Matt Turner <mattst88@gmail.com> | 2009-11-30 22:44:40 -0500 |
commit | 745dd2405e281d96c0a449103bdf6a895048f28c (patch) | |
tree | 3cbcd71049b42e0f2933d7682886527beed4a4c3 /Makefile | |
parent | cc9a2c8301683f73b7e0d1fc2cb5159110f3469f (diff) | |
download | talos-op-linux-745dd2405e281d96c0a449103bdf6a895048f28c.tar.gz talos-op-linux-745dd2405e281d96c0a449103bdf6a895048f28c.zip |
Alpha: Rearrange thread info flags fixing two regressions
The removal of the TIF_NOTIFY_RESUME flag, commit a583f1b54249b
"remove unused TIF_NOTIFY_RESUME flag," resulted in incorrect
setting of the unaligned access control flags by the prctl syscall.
The re-addition of the TIF_NOTIFY_RESUME flag, commit d0420c83f39f
"KEYS: Extend TIF_NOTIFY_RESUME to (almost) all architectures [try #6]"
further caused problems, namely incorrect operands to assembler code
as evidenced by:
AS arch/alpha/kernel/entry.o
arch/alpha/kernel/entry.S: Assembler messages:
arch/alpha/kernel/entry.S:326: Warning: operand out of range
(0x0000000000000406 is not between 0x0000000000000000 and
0x00000000000000ff)
Both regressions fixed by (1) rearranging TIF_NOTIFY_RESUME flag to be
in lower 8 bits of the thread info flags, and (2) making sure that
ALPHA_UAC_SHIFT matches the rearrangement of the thread info flags.
Signed-off-by: Michael Cree <mcree@orcon.net.nz>
Cc: Richard Henderson <rth@twiddle.net>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: David Howells <dhowells@redhat.com>,
Signed-off-by: Matt Turner <mattst88@gmail.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions