Chromium Code Reviews| Index: base/trace_event/trace_event_impl.h |
| diff --git a/base/trace_event/trace_event_impl.h b/base/trace_event/trace_event_impl.h |
| index efa20c4ff85ff57b3b6c52b22247cfb136392fe6..b02b3a2ba246944f899f8bc1470ca5ce023e5e6d 100644 |
| --- a/base/trace_event/trace_event_impl.h |
| +++ b/base/trace_event/trace_event_impl.h |
| @@ -26,6 +26,7 @@ |
| // Older style trace macros with explicit id and extra data |
| // Only these macros result in publishing data to ETW as currently implemented. |
|
dsinclair
2015/03/26 18:18:17
This is no longer correct.
Georges Khalil
2015/03/26 23:09:19
Acknowledged.
|
| +// TODO(georgesak): Update/replace these with new ETW macros. |
|
dsinclair
2015/03/26 18:18:17
In theory, we won't need ETW custom macros anymore
Georges Khalil
2015/03/26 23:09:20
Correct. Right now, we have old ETW tracing as wel
|
| #define TRACE_EVENT_BEGIN_ETW(name, id, extra) \ |
| base::trace_event::TraceLog::AddTraceEventEtw( \ |
| TRACE_EVENT_PHASE_BEGIN, \ |
| @@ -446,6 +447,8 @@ class BASE_EXPORT TraceLog { |
| ENABLED_FOR_MONITORING = 1 << 1, |
| // Category group enabled by SetEventCallbackEnabled(). |
| ENABLED_FOR_EVENT_CALLBACK = 1 << 2, |
| + // Category group enabled to export events to ETW. |
| + ENABLED_FOR_ETW_EXPORT = 1 << 3 |
| }; |
| static TraceLog* GetInstance(); |