Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Obsolete/MultiCoreDebugWorkingGroup/calls/minutes"
< CDT | Obsolete | MultiCoreDebugWorkingGroup
(→Next call) |
(→November 16, 2010) |
||
| Line 15: | Line 15: | ||
=== November 16, 2010 === | === November 16, 2010 === | ||
| − | + | Attendees: | |
| + | * Patrick Chuong (TI) | ||
| + | * Dobrin Alexiev (TI) | ||
| + | * Pawel Piech (WindRiver) | ||
| + | * Doug Schaefer (WindRiver) | ||
| + | * Pete (Tensilica) | ||
| + | * Amen (Tensilica) | ||
| + | * Norman Yi (Analog Devices) | ||
| + | * Bill Swanson (Tilera) | ||
| + | * John Cortell (Freescale) | ||
| + | * Marc Khouzam (Ericsson) | ||
| + | |||
| + | Minutes: | ||
| + | |||
| + | * Level of expected contributions from interested parties | ||
| + | ** Patrick and Dobrin have time allocated to this | ||
| + | ** Marc has time allocated for this | ||
| + | ** Pete can have someone help on UI work | ||
| + | ** Other commitments will clarify as the effort takes shape | ||
| − | |||
| − | |||
* Conference calls - is the proposed schedule satisfactory? | * Conference calls - is the proposed schedule satisfactory? | ||
| + | ** Seems as good as any other | ||
| + | |||
* High-level preliminary goals | * High-level preliminary goals | ||
* Current state of affairs (including Patrick and Dobrin's nice work) | * Current state of affairs (including Patrick and Dobrin's nice work) | ||
| Line 25: | Line 43: | ||
* Task definition and assignment | * Task definition and assignment | ||
* Pin and Clone status | * Pin and Clone status | ||
| + | |||
| + | |||
| + | == | ||
| + | |||
| + | TI's uses cases all focus on 10 to 50 contexts in the debug view. They currently feel that dealing with more than 100 contexts requires a new approach. | ||
| + | TI's approach is to use the Debug View with a recursive set of containers, where the backend debugger remains the top-level entity. | ||
| + | |||
| + | From a user-perspective, we want to be able to actively focus on a small amount of contexts, while making the others available in case they become of interest. | ||
| + | |||
| + | Filtering of information is essential to this effort. Grouping and hiding are trying to address this. | ||
| + | |||
| + | Clean up wiki page to help people add their use-cases of interest, to help keep focus on the problems we face. [Marc] | ||
| + | |||
| + | Discussions on Tilera's Grid view: | ||
| + | ** The view has proven useful, but mostly when knowledge about the underlying hardware was relevant to the problem being debugged. | ||
| + | ** Software designers still saw their software as a generic grouping of processes and threads, as shown in the Debug View. | ||
Revision as of 06:42, 17 November 2010
Contents
Multi-Core Debugging Work Group Conference Calls
Conference call dates
Next call
Previous calls
Agenda for next call
Minutes of previous calls
November 16, 2010
Attendees:
- Patrick Chuong (TI)
- Dobrin Alexiev (TI)
- Pawel Piech (WindRiver)
- Doug Schaefer (WindRiver)
- Pete (Tensilica)
- Amen (Tensilica)
- Norman Yi (Analog Devices)
- Bill Swanson (Tilera)
- John Cortell (Freescale)
- Marc Khouzam (Ericsson)
Minutes:
- Level of expected contributions from interested parties
- Patrick and Dobrin have time allocated to this
- Marc has time allocated for this
- Pete can have someone help on UI work
- Other commitments will clarify as the effort takes shape
- Conference calls - is the proposed schedule satisfactory?
- Seems as good as any other
- High-level preliminary goals
- Current state of affairs (including Patrick and Dobrin's nice work)
- Way forward
- Task definition and assignment
- Pin and Clone status
==
TI's uses cases all focus on 10 to 50 contexts in the debug view. They currently feel that dealing with more than 100 contexts requires a new approach. TI's approach is to use the Debug View with a recursive set of containers, where the backend debugger remains the top-level entity.
From a user-perspective, we want to be able to actively focus on a small amount of contexts, while making the others available in case they become of interest.
Filtering of information is essential to this effort. Grouping and hiding are trying to address this.
Clean up wiki page to help people add their use-cases of interest, to help keep focus on the problems we face. [Marc]
Discussions on Tilera's Grid view:
- The view has proven useful, but mostly when knowledge about the underlying hardware was relevant to the problem being debugged.
- Software designers still saw their software as a generic grouping of processes and threads, as shown in the Debug View.