-
Notifications
You must be signed in to change notification settings - Fork 9
want USDT support for probes #56
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
Comments
rzezeski
added a commit
that referenced
this issue
Mar 14, 2022
The main thrust of this commit is to add DHCPv4 support. However some other work came along for the ride. Some of these are complete, others are ongoing. * use smoltcp for parsing (#57) This commit introduces smoltcp for the purpose of using its wire module to parse protocol data -- to wit the DHCP/ICMP data. Over time more of the homegrown header parsing will be usurped by smoltcp. * ping (ICMPv4) the gateway (#58) * show data predicates when dumping a layer (#59) * Use cfg_if crate (#47) Added cfg_if crate and made use of it in some places. The next step is to update the rest of the modules to use it. * want USDT support for probes (#56) Started adding USDT support for the various DTrace probes allowing one to trace the SDT probes while running unit tests! Other work done in this commit includes: * Refactored some of the common DTrace script code into a common library and common header file. * Removed some obsolete code + tests that date back to when OPTE was designed to take part in a home/lab IPv4 network, before the times of IPv6+Geneve and the glory of the Falcon topology simulator. * Added some incomplete code around generating packet captures for tests.
Fixed in 1cada72. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the SDT probes are only available when
opte-core
is running in kernel context on a live system. Thestd
environment side of things are just stubs that do nothing. It would be useful to turn those no-ops into USDT probes: allowing one to trace the SDT probes during unit testing just as they would when running on a live system!The text was updated successfully, but these errors were encountered: