Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Menu
Open sidebar
adam.huang
Arm Trusted Firmware
Commits
ac864694
Commit
ac864694
authored
6 years ago
by
Soby Mathew
Committed by
TrustedFirmware Code Review
6 years ago
Browse files
Options
Download
Plain Diff
Merge "Fix RST rendering and other typos" into integration
parents
0cdbd023
6d0512f5
master
v2.5
v2.5-rc1
v2.5-rc0
v2.4
v2.4-rc2
v2.4-rc1
v2.4-rc0
v2.3
v2.3-rc2
v2.3-rc1
v2.3-rc0
v2.2
v2.2-rc2
v2.2-rc1
v2.2-rc0
arm_cca_v0.2
arm_cca_v0.1
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/user-guide.rst
+17
-12
docs/user-guide.rst
with
17 additions
and
12 deletions
+17
-12
docs/user-guide.rst
View file @
ac864694
...
...
@@ -359,12 +359,17 @@ Common build options
registers
to
be
included
when
saving
and
restoring
the
CPU
context
.
Default
is
0.
-
``
CTX_INCLUDE_PAUTH_REGS
``:
Boolean
option
that
,
when
set
to
1
,
enables
Pointer
Authentication
for
Secure
world
.
This
will
cause
the
ARMv8
.3
-
PAuth
registers
to
be
included
when
saving
and
restoring
the
CPU
context
as
part
of
world
switch
.
Default
value
is
0
and
this
is
an
experimental
feature
.
Note
that
Pointer
Authentication
is
enabled
for
Non
-
secure
world
irrespective
of
the
value
of
this
flag
if
the
CPU
supports
it
.
-
``
CTX_INCLUDE_PAUTH_REGS
``:
Boolean
option
that
,
when
set
to
1
,
allows
Pointer
Authentication
for
**
Secure
world
**.
This
will
cause
the
Armv8
.3
-
PAuth
registers
to
be
included
when
saving
and
restoring
the
CPU
context
as
part
of
a
world
switch
.
Default
value
is
0.
Pointer
Authentication
is
an
experimental
feature
.
Note
that
,
if
the
CPU
supports
it
,
Pointer
Authentication
is
allowed
for
Non
-
secure
world
irrespectively
of
the
value
of
this
flag
.
"Allowed"
means
that
accesses
to
PAuth
-
related
registers
or
execution
of
PAuth
-
related
instructions
will
not
be
trapped
to
EL3
.
As
such
,
usage
or
not
of
PAuth
in
Non
-
secure
world
images
,
depends
on
those
images
themselves
.
-
``
DEBUG
``:
Chooses
between
a
debug
and
release
build
.
It
can
take
either
0
(
release
)
or
1
(
debug
)
as
values
.
0
is
the
default
.
...
...
@@ -417,12 +422,12 @@ Common build options
partitioning
in
EL3
,
however
.
Platform
initialisation
code
should
configure
and
use
partitions
in
EL3
as
required
.
This
option
defaults
to
``
0
``.
-
``
ENABLE_PAUTH
``:
Boolean
option
to
enable
A
RM
v8
.3
Pointer
Authentication
support
for
TF
-
A
BL
images
itself
.
If
enabled
,
it
is
needed
to
use
a
compiler
that
supports
the
option
``-
msign
-
return
-
address
``.
This
flag
defaults
to
0
and
this
is
an
experimental
feature
.
Note
that
Pointer
Authentication
is
enabled
for
Non
-
secure
world
irrespective
of
the
value
of
this
flag
if
the
CPU
supports
it
.
-
``
ENABLE_PAUTH
``:
Boolean
option
to
enable
A
rm
v8
.3
Pointer
Authentication
for
**
TF
-
A
BL
images
themselves
**
.
If
enabled
,
the
compiler
must
support
the
``-
msign
-
return
-
address
``
option
.
This
flag
defaults
to
0
.
Pointer
Authentication
is
an
experimental
feature
.
If
this
flag
is
enabled
,
``
CTX_INCLUDE_PAUTH_REGS
``
must
also
be
enabled
.
-
``
ENABLE_PIE
``:
Boolean
option
to
enable
Position
Independent
Executable
(
PIE
)
support
within
generic
code
in
TF
-
A
.
This
option
is
currently
only
supported
...
...
This diff is collapsed.
Click to expand it.
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
Menu
Projects
Groups
Snippets
Help