-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ETDumpGen_Done state and reset when in that state #3667
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/3667
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 5a4a5bd with merge base 47a29a1 (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D57517927 |
Summary: Currently when we call `get_etdump_data()` we finalize the flatbuffer and close it. In order to add entries to etdump once again after we've closed it we need to reset the etdump buffer. In order to support this, adding a `ETDumpGen_Done` state to which we move after calling `get_etdump_data()`. When this state is detected in `create_event_block` we implicitly call `reset()` and thus enabling writing to the flatbuffer again without any user intervention. Reviewed By: swolchok Differential Revision: D57517927
690c63b
to
a527abc
Compare
This pull request was exported from Phabricator. Differential Revision: D57517927 |
Summary: Currently when we call `get_etdump_data()` we finalize the flatbuffer and close it. In order to add entries to etdump once again after we've closed it we need to reset the etdump buffer. In order to support this, adding a `ETDumpGen_Done` state to which we move after calling `get_etdump_data()`. When this state is detected in `create_event_block` we implicitly call `reset()` and thus enabling writing to the flatbuffer again without any user intervention. Reviewed By: swolchok Differential Revision: D57517927
a527abc
to
93e2466
Compare
This pull request was exported from Phabricator. Differential Revision: D57517927 |
Summary: Currently when we call `get_etdump_data()` we finalize the flatbuffer and close it. In order to add entries to etdump once again after we've closed it we need to reset the etdump buffer. In order to support this, adding a `ETDumpGen_Done` state to which we move after calling `get_etdump_data()`. When this state is detected in `create_event_block` we implicitly call `reset()` and thus enabling writing to the flatbuffer again without any user intervention. Reviewed By: swolchok Differential Revision: D57517927
93e2466
to
7ddfd28
Compare
This pull request was exported from Phabricator. Differential Revision: D57517927 |
Summary: Currently when we call `get_etdump_data()` we finalize the flatbuffer and close it. In order to add entries to etdump once again after we've closed it we need to reset the etdump buffer. In order to support this, adding a `ETDumpGen_Done` state to which we move after calling `get_etdump_data()`. When this state is detected in `create_event_block` we implicitly call `reset()` and thus enabling writing to the flatbuffer again without any user intervention. Reviewed By: swolchok Differential Revision: D57517927
7ddfd28
to
5a4a5bd
Compare
This pull request was exported from Phabricator. Differential Revision: D57517927 |
This pull request has been merged in 07dcf35. |
Summary:
Currently when we call
get_etdump_data()
we finalize the flatbuffer and close it. In order to add entries to etdump once again after we've closed it we need to reset the etdump buffer.In order to support this, adding a
ETDumpGen_Done
state to which we move after callingget_etdump_data()
. When this state is detected increate_event_block
we implicitly callreset()
and thus enabling writing to the flatbuffer again without any user intervention.Differential Revision: D57517927