Uh oh!
There was an error while loading. Please reload this page.
Make firing of ETW events in nativeaot opt-in via the enabled/disabled lib - #88800
Conversation
ghost
commented
Jul 12, 2023
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue Details
The actual implementation still:
This will enable us to actually reconcile the ETW and EventPipe tracking/contexts/callbacks in nativeaot, which we will need to address #88162 and to switch to the generation scripts based on the event manifest instead of checking in modified parts of the output and manually updating.
|
abfefdc to
02e28c9CompareUh oh!
There was an error while loading. Please reload this page.
LakshanF
left a comment
There was a problem hiding this comment.
Thanks for making this change! The clean separation is going to make it much easier, both to add new events and for the change to auto-generated python scripts.
elinor-fung
commented
Jul 14, 2023
Failure is #88870. |
FireEtw*instead ofEventPipeWriteEvent*The actual implementation still:
This will enable us to actually reconcile the ETW and EventPipe tracking/contexts/callbacks in nativeaot, which we will need to address #88162 and to switch to the generation scripts based on the event manifest instead of checking in modified parts of the output and manually updating.
I'd also like to move some of the files that are no longer part of the core runtime into a subdirectory (of nativeaot/Runtime) - but in a separate change.