Closed
Bug 904881
Opened 11 years ago
Closed 11 years ago
Add stack unwinding through JS JIT code to SPS and perf_events on B2G
Categories
(Firefox OS Graveyard :: Performance, defect, P4)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 914561
2.0 S2 (23may)
People
(Reporter: huseby, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [c=profiling p= s=2014.05.23 u=])
Add support for this to the stack unwinding code on B2G: We push a pseudoframe entry called js::RunScript before entering JS. We can modify that pseudoframe to contain all the data to unwind from that point. We can use these frames to resume the unwinding. Thus the stack would look like this: XRE_Main --- done ... | event loop | run event | ... | JS::RunScript (Saved Context) Resume unwind from context JITFrame (Can't unwind) Recover all JITFrame (Can't unwind) JIT frames via JITFrame (Can't unwind) Pseudoframes JITFrame (Can't unwind) --- VMCall | JS_GetData | PR_Now Unwind
Updated•11 years ago
|
Keywords: perf
Whiteboard: [c=profiling s=2013.09.20 p=4] → [c=profiling p=4 s= u=]
Reporter | ||
Updated•11 years ago
|
Assignee: dhuseby → nobody
Do we still need to take action on this one?
Component: General → Performance
Flags: needinfo?(dhuseby)
Priority: -- → P4
Reporter | ||
Comment 3•11 years ago
|
||
closing then.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dhuseby)
Resolution: --- → DUPLICATE
Updated•11 years ago
|
Whiteboard: [c=profiling p=4 s= u=] → [c=profiling p= s=2014.05.23 u=]
Updated•10 years ago
|
Target Milestone: --- → 2.0 S2 (23may)
You need to log in
before you can comment on or make changes to this bug.
Description
•