The <ebp> and </ebp> tags mark the beginning and end of an event-based profile data collection configuration. This element has the following attributes:
name |
Configuration name (string) |
The sampling events are specified using <event> element. One are more events can be specified. The tag <event> </event> mark the beginning and end of an event element. It describes how an individual event counter is configured for data collection.
An event has the following attributes:
select |
Event select value (integer) |
mask |
Unit mask value (integer) |
os |
Enables OS sampling (Boolean) |
user |
Enables user level sampling (Boolean) |
count |
Sampling period (integer) |
edge_detect |
Enables edge detect when counting events (Boolean). This is optional. |
host |
Enables host mode event counting (Boolean). This is optional. |
guest |
Enables guest mode event counting (Boolean). This is optional. |
The values must be validated against the events and specific capabilities supported by the measurement platform. The maximum number of events depends upon the number of counters supported by the platform on which the measurements are taken.
Sample EBP configuration:
<dc_configuration>
<ebp name=”event based profile”>
<event select=”C0” mask=”00” os=”T” user=”T” count=”250000> </event>
<event select=”76” mask=”00” os=”T” user=”T” count=”250000> </event>
<tool_tip> HW PMC events based profiling </tool_tip>
<description> Configuration to find potential issues for investigation
</description>
</ebp>
</dc_configuration>