Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
d6f0f22c
Commit
d6f0f22c
authored
Oct 14, 2010
by
Chris Metcalf
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
arch/tile: update some comments to clarify register usage.
Signed-off-by:
Chris Metcalf
<
cmetcalf@tilera.com
>
parent
5592840b
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
3 deletions
+6
-3
arch/tile/kernel/intvec_32.S
arch/tile/kernel/intvec_32.S
+2
-0
arch/tile/kernel/process.c
arch/tile/kernel/process.c
+4
-3
No files found.
arch/tile/kernel/intvec_32.S
View file @
d6f0f22c
...
...
@@ -1553,6 +1553,8 @@ STD_ENTRY(_sys_clone)
*
to
be
available
to
it
on
entry
.
It
does
not
modify
any
callee
-
save
*
registers
(
including
"lr"
)
.
It
does
not
check
what
PL
it
is
being
*
called
at
,
so
you
'd better not call it other than at PL0.
*
The
<
atomic
.
h
>
wrapper
assumes
it
only
clobbers
r20
-
r29
,
so
if
*
it
ever
is
necessary
to
use
more
registers
,
be
aware
.
*
*
It
does
not
use
the
stack
,
but
since
it
might
be
re
-
interrupted
by
*
a
page
fault
which
would
assume
the
stack
was
valid
,
it
does
...
...
arch/tile/kernel/process.c
View file @
d6f0f22c
...
...
@@ -214,9 +214,10 @@ int copy_thread(unsigned long clone_flags, unsigned long sp,
/*
* Copy the callee-saved registers from the passed pt_regs struct
* into the context-switch callee-saved registers area.
* We have to restore the callee-saved registers since we may
* be cloning a userspace task with userspace register state,
* and we won't be unwinding the same kernel frames to restore them.
* This way when we start the interrupt-return sequence, the
* callee-save registers will be correctly in registers, which
* is how we assume the compiler leaves them as we start doing
* the normal return-from-interrupt path after calling C code.
* Zero out the C ABI save area to mark the top of the stack.
*/
ksp
=
(
unsigned
long
)
childregs
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment