use crate::instantiate::CompiledModule; use crate::prelude::*; use crate::runtime::vm::Backtrace; use crate::{AsContext, CallHook, Module}; use fxprof_processed_profile::debugid::DebugId; use fxprof_processed_profile::{ CategoryHandle, Frame, FrameFlags, FrameInfo, LibraryInfo, MarkerLocation, MarkerSchema, MarkerTiming, Profile, ProfilerMarker, ReferenceTimestamp, Symbol, SymbolTable, Timestamp, }; use std::ops::Range; use std::sync::Arc; use std::time::{Duration, Instant}; use wasmtime_environ::demangle_function_name_or_index; // TODO: collect more data // - On non-Windows, measure thread-local CPU usage between events with // rustix::time::clock_gettime(ClockId::ThreadCPUTime) // - Report which wasm module, and maybe instance, each frame came from /// Collects basic profiling data for a single WebAssembly guest. /// /// This profiler can't provide measurements that are as accurate or detailed /// as a platform-specific profiler, such as `perf` on Linux. On the other /// hand, this profiler works on every platform that Wasmtime supports. Also, /// as an embedder you can use this profiler selectively on individual guest /// instances rather than profiling the entire process. /// /// To use this, you'll need to arrange to call [`GuestProfiler::sample`] at /// regular intervals while the guest is on the stack. The most straightforward /// way to do that is to call it from a callback registered with /// [`Store::epoch_deadline_callback()`](crate::Store::epoch_deadline_callback). /// /// # Accuracy /// /// The data collection granularity is limited by the mechanism you use to /// interrupt guest execution and collect a profiling sample. /// /// If you use epoch interruption, then samples will only be collected at /// function entry points and loop headers. This introduces some bias to the /// results. In addition, samples will only be taken at times when WebAssembly /// functions are running, not during host-calls. /// /// It is technically possible to use fuel interruption instead. That /// introduces worse bias since samples occur after a certain number of /// WebAssembly instructions, which can take different amounts of time. /// /// You may instead be able to use platform-specific methods, such as /// `setitimer(ITIMER_VIRTUAL, ...)` on POSIX-compliant systems, to sample on /// a more accurate interval. The only current requirement is that the guest /// you wish to profile must be on the same stack where you call `sample`, /// and executing within the same thread. However, the `GuestProfiler::sample` /// method is not currently async-signal-safe, so doing this correctly is not /// easy. /// /// # Security /// /// Profiles produced using this profiler do not include any configuration /// details from the host, such as virtual memory addresses, or from any /// WebAssembly modules that you haven't specifically allowed. So for /// example, these profiles should be safe to share with untrusted users /// who have provided untrusted code that you are running in a multi-tenancy /// environment. /// /// However, the profile does include byte offsets into the text section of /// the compiled module, revealing some information about the size of the code /// generated for each module. For user-provided modules, the user could get /// the same information by compiling the module for themself using a similar /// version of Wasmtime on the same target architecture, but for any module /// where they don't already have the WebAssembly module binary available this /// could theoretically lead to an undesirable information disclosure. So you /// should only include user-provided modules in profiles. #[derive(Debug)] pub struct GuestProfiler { profile: Profile, modules: Modules, process: fxprof_processed_profile::ProcessHandle, thread: fxprof_processed_profile::ThreadHandle, start: Instant, } type Modules = Vec<(Range, fxprof_processed_profile::LibraryHandle)>; impl GuestProfiler { /// Begin profiling a new guest. When this function is called, the current /// wall-clock time is recorded as the start time for the guest. /// /// The `module_name` parameter is recorded in the profile to help identify /// where the profile came from. /// /// The `interval` parameter should match the rate at which you intend /// to call `sample`. However, this is used as a hint and not required to /// exactly match the real sample rate. /// /// Only modules which are present in the `modules` vector will appear in /// stack traces in this profile. Any stack frames which were executing /// host code or functions from other modules will be omitted. See the /// "Security" section of the [`GuestProfiler`] documentation for guidance /// on what modules should not be included in this list. pub fn new(module_name: &str, interval: Duration, modules: Vec<(String, Module)>) -> Self { let zero = ReferenceTimestamp::from_millis_since_unix_epoch(0.0); let mut profile = Profile::new(module_name, zero, interval.into()); let mut modules: Vec<_> = modules .into_iter() .filter_map(|(name, module)| { let compiled = module.compiled_module(); let text = compiled.text().as_ptr_range(); let address_range = text.start as usize..text.end as usize; module_symbols(name, compiled).map(|lib| (address_range, profile.add_lib(lib))) }) .collect(); modules.sort_unstable_by_key(|(range, _)| range.start); profile.set_reference_timestamp(std::time::SystemTime::now().into()); let process = profile.add_process(module_name, 0, Timestamp::from_nanos_since_reference(0)); let thread = profile.add_thread(process, 0, Timestamp::from_nanos_since_reference(0), true); let start = Instant::now(); Self { profile, modules, process, thread, start, } } /// Add a sample to the profile. This function collects a backtrace from /// any stack frames for allowed modules on the current stack. It should /// typically be called from a callback registered using /// [`Store::epoch_deadline_callback()`](crate::Store::epoch_deadline_callback). /// /// The `delta` parameter is the amount of CPU time that was used by this /// guest since the previous sample. It is allowed to pass `Duration::ZERO` /// here if recording CPU usage information is not needed. pub fn sample(&mut self, store: impl AsContext, delta: Duration) { let now = Timestamp::from_nanos_since_reference( self.start.elapsed().as_nanos().try_into().unwrap(), ); let backtrace = Backtrace::new(store.as_context().0); let frames = lookup_frames(&self.modules, &backtrace); self.profile .add_sample(self.thread, now, frames, delta.into(), 1); } /// Add a marker for transitions between guest and host to the profile. /// This function should typically be called from a callback registered /// using [`Store::call_hook()`](crate::Store::call_hook), and the `kind` /// parameter should be the value of the same type passed into that hook. pub fn call_hook(&mut self, store: impl AsContext, kind: CallHook) { let now = Timestamp::from_nanos_since_reference( self.start.elapsed().as_nanos().try_into().unwrap(), ); match kind { CallHook::CallingWasm | CallHook::ReturningFromWasm => {} CallHook::CallingHost => { let backtrace = Backtrace::new(store.as_context().0); let frames = lookup_frames(&self.modules, &backtrace); self.profile.add_marker_with_stack( self.thread, "hostcall", CallMarker, MarkerTiming::IntervalStart(now), frames, ); } CallHook::ReturningFromHost => { self.profile.add_marker( self.thread, "hostcall", CallMarker, MarkerTiming::IntervalEnd(now), ); } } } /// When the guest finishes running, call this function to write the /// profile to the given `output`. The output is a JSON-formatted object in /// the [Firefox "processed profile format"][fmt]. Files in this format may /// be visualized at . /// /// [fmt]: https://github.com/firefox-devtools/profiler/blob/main/docs-developer/processed-profile-format.md pub fn finish(mut self, output: impl std::io::Write) -> Result<()> { let now = Timestamp::from_nanos_since_reference( self.start.elapsed().as_nanos().try_into().unwrap(), ); self.profile.set_thread_end_time(self.thread, now); self.profile.set_process_end_time(self.process, now); serde_json::to_writer(output, &self.profile)?; Ok(()) } } fn module_symbols(name: String, compiled: &CompiledModule) -> Option { let symbols = Vec::from_iter(compiled.finished_functions().map(|(defined_idx, _)| { let loc = compiled.func_loc(defined_idx); let func_idx = compiled.module().func_index(defined_idx); let mut name = String::new(); demangle_function_name_or_index( &mut name, compiled.func_name(func_idx), defined_idx.as_u32() as usize, ) .unwrap(); Symbol { address: loc.start, size: Some(loc.length), name, } })); if symbols.is_empty() { return None; } Some(LibraryInfo { name, debug_name: String::new(), path: String::new(), debug_path: String::new(), debug_id: DebugId::nil(), code_id: None, arch: None, symbol_table: Some(Arc::new(SymbolTable::new(symbols))), }) } fn lookup_frames<'a>( modules: &'a Modules, backtrace: &'a Backtrace, ) -> impl Iterator + 'a { backtrace .frames() // Samply needs to see the oldest frame first, but we list the newest // first, so iterate in reverse. .rev() .filter_map(|frame| { // Find the first module whose start address includes this PC. let module_idx = modules.partition_point(|(range, _)| range.start > frame.pc()); if let Some((range, lib)) = modules.get(module_idx) { if range.contains(&frame.pc()) { return Some(FrameInfo { frame: Frame::RelativeAddressFromReturnAddress( *lib, u32::try_from(frame.pc() - range.start).unwrap(), ), category_pair: CategoryHandle::OTHER.into(), flags: FrameFlags::empty(), }); } } None }) } struct CallMarker; impl ProfilerMarker for CallMarker { const MARKER_TYPE_NAME: &'static str = "hostcall"; fn schema() -> MarkerSchema { MarkerSchema { type_name: Self::MARKER_TYPE_NAME, locations: vec![ MarkerLocation::MarkerChart, MarkerLocation::MarkerTable, MarkerLocation::TimelineOverview, ], chart_label: None, tooltip_label: None, table_label: None, fields: vec![], } } fn json_marker_data(&self) -> serde_json::Value { serde_json::json!({ "type": Self::MARKER_TYPE_NAME }) } }