summaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2012-03-21 10:17:03 -0500
committerJason Wessel <jason.wessel@windriver.com>2012-03-29 17:41:25 -0500
commit98b54aa1a2241b59372468bd1e9c2d207bdba54b (patch)
tree0a6cc3bc8426434a176e0fcb3c2da23d383a5a3b /firmware
parent23bbd8e346f1ef3fc1219c79cea53d8d52b207d8 (diff)
downloadblackbird-op-linux-98b54aa1a2241b59372468bd1e9c2d207bdba54b.tar.gz
blackbird-op-linux-98b54aa1a2241b59372468bd1e9c2d207bdba54b.zip
kgdb,debug_core: pass the breakpoint struct instead of address and memory
There is extra state information that needs to be exposed in the kgdb_bpt structure for tracking how a breakpoint was installed. The debug_core only uses the the probe_kernel_write() to install breakpoints, but this is not enough for all the archs. Some arch such as x86 need to use text_poke() in order to install a breakpoint into a read only page. Passing the kgdb_bpt structure to kgdb_arch_set_breakpoint() and kgdb_arch_remove_breakpoint() allows other archs to set the type variable which indicates how the breakpoint was installed. Cc: stable@vger.kernel.org # >= 2.6.36 Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud