Searched hist:"26 a04d84bc5311d7785b229b353f327e866ab61a" (Results 1 – 6 of 6) sorted by relevance
| /openbmc/linux/arch/arm64/include/asm/ |
| H A D | brk-imm.h | diff 26a04d84bc5311d7785b229b353f327e866ab61a Tue Feb 26 06:52:47 CST 2019 Will Deacon <will.deacon@arm.com> arm64: debug: Separate debug hooks based on target exception level
Mixing kernel and user debug hooks together is highly error-prone as it
relies on all of the hooks to figure out whether the exception came from
kernel or user, and then to act accordingly.
Make our debug hook code a little more robust by maintaining separate
hook lists for user and kernel, with separate registration functions
to force callers to be explicit about the exception levels that they
care about.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
|
| H A D | debug-monitors.h | diff 26a04d84bc5311d7785b229b353f327e866ab61a Tue Feb 26 06:52:47 CST 2019 Will Deacon <will.deacon@arm.com> arm64: debug: Separate debug hooks based on target exception level
Mixing kernel and user debug hooks together is highly error-prone as it
relies on all of the hooks to figure out whether the exception came from
kernel or user, and then to act accordingly.
Make our debug hook code a little more robust by maintaining separate
hook lists for user and kernel, with separate registration functions
to force callers to be explicit about the exception levels that they
care about.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
|
| /openbmc/linux/arch/arm64/kernel/probes/ |
| H A D | uprobes.c | diff 26a04d84bc5311d7785b229b353f327e866ab61a Tue Feb 26 06:52:47 CST 2019 Will Deacon <will.deacon@arm.com> arm64: debug: Separate debug hooks based on target exception level
Mixing kernel and user debug hooks together is highly error-prone as it
relies on all of the hooks to figure out whether the exception came from
kernel or user, and then to act accordingly.
Make our debug hook code a little more robust by maintaining separate
hook lists for user and kernel, with separate registration functions
to force callers to be explicit about the exception levels that they
care about.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
|
| /openbmc/linux/arch/arm64/kernel/ |
| H A D | kgdb.c | diff 26a04d84bc5311d7785b229b353f327e866ab61a Tue Feb 26 06:52:47 CST 2019 Will Deacon <will.deacon@arm.com> arm64: debug: Separate debug hooks based on target exception level
Mixing kernel and user debug hooks together is highly error-prone as it
relies on all of the hooks to figure out whether the exception came from
kernel or user, and then to act accordingly.
Make our debug hook code a little more robust by maintaining separate
hook lists for user and kernel, with separate registration functions
to force callers to be explicit about the exception levels that they
care about.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
|
| H A D | debug-monitors.c | diff 26a04d84bc5311d7785b229b353f327e866ab61a Tue Feb 26 06:52:47 CST 2019 Will Deacon <will.deacon@arm.com> arm64: debug: Separate debug hooks based on target exception level
Mixing kernel and user debug hooks together is highly error-prone as it
relies on all of the hooks to figure out whether the exception came from
kernel or user, and then to act accordingly.
Make our debug hook code a little more robust by maintaining separate
hook lists for user and kernel, with separate registration functions
to force callers to be explicit about the exception levels that they
care about.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
|
| H A D | traps.c | diff 26a04d84bc5311d7785b229b353f327e866ab61a Tue Feb 26 06:52:47 CST 2019 Will Deacon <will.deacon@arm.com> arm64: debug: Separate debug hooks based on target exception level
Mixing kernel and user debug hooks together is highly error-prone as it
relies on all of the hooks to figure out whether the exception came from
kernel or user, and then to act accordingly.
Make our debug hook code a little more robust by maintaining separate
hook lists for user and kernel, with separate registration functions
to force callers to be explicit about the exception levels that they
care about.
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
|