4 Commits (53c59aed5e0bc4b9ee5563ec8751f727c7e5371e)

Author	SHA1	Message	Date
Thomas Eizinger	53c59aed5e	workspace: include eBPF crates in default-members ... Being able to compile the eBPF crates for the host architecture is useful because it allows `cargo build` and `cargo test` to "just work". To achieve that, we feature-gate `no_std` and `no_main` on the bpf target architecture.	3 weeks ago
Thomas Eizinger	ef181058b0	fix: only include panic-handler on bpf target	3 weeks ago
Dave Tucker	3078e5aba0	chore: Fix clippy panic_handler warnings ... Working with aya in vscode will currently show a number of warnings along the lines of: ``` found duplicate lang item `panic_impl` the lang item is first defined in crate `std` (which `aya` depends on) ... second definition in the local crate (`bpf_probe_read`) ``` This comes from feature unification. integration-test requires the integration-common user feature, which requires aya, which in turn brings in std. For this same reason we avoid running clippy across the whole workspace. We can avoid this issue by using the panic handler from the another crate, which implements the same loop {} panic handler we use today. It seems rustc is happy to conditionally link the panic handler from an external crate without issuing warnings. Therefore, we add our own crate - ebpf-panic - for this purpose. Signed-off-by: Dave Tucker <dave@dtucker.co.uk>	4 weeks ago
Mike Rostecki	f34d355d7d	bpf: Handle raw tracepoint arguments ... Provide an `arg()` method in `RawTracepointArgs` wrapper of `bpf_raw_tracepoint_args` and also in `RawTracepointContext`, so it's directly available in raw tracepoint programs. The methods and traits implemented here are unsafe. There is no way to reliably check the number of available arguments, so requesting a non-existing one leads to undefined behavior.	3 months ago