Skip to main content

wasmtime_environ/component/translate/
adapt.rs

1//! Identification and creation of fused adapter modules in Wasmtime.
2//!
3//! A major piece of the component model is the ability for core wasm modules to
4//! talk to each other through the use of lifted and lowered functions. For
5//! example one core wasm module can export a function which is lifted. Another
6//! component could import that lifted function, lower it, and pass it as the
7//! import to another core wasm module. This is what Wasmtime calls "adapter
8//! fusion" where two core wasm functions are coming together through the
9//! component model.
10//!
11//! There are a few ingredients during adapter fusion:
12//!
13//! * A core wasm function which is "lifted".
14//! * A "lift type" which is the type that the component model function had in
15//!   the original component
16//! * A "lower type" which is the type that the component model function has
17//!   in the destination component (the one the uses `canon lower`)
18//! * Configuration options for both the lift and the lower operations such as
19//!   memories, reallocs, etc.
20//!
21//! With these ingredients combined Wasmtime must produce a function which
22//! connects the two components through the options specified. The fused adapter
23//! performs tasks such as validation of passed values, copying data between
24//! linear memories, etc.
25//!
26//! Wasmtime's current implementation of fused adapters is designed to reduce
27//! complexity elsewhere as much as possible while also being suitable for being
28//! used as a polyfill for the component model in JS environments as well. To
29//! that end Wasmtime implements a fused adapter with another wasm module that
30//! it itself generates on the fly. The usage of WebAssembly for fused adapters
31//! has a number of advantages:
32//!
33//! * There is no need to create a raw Cranelift-based compiler. This is where
34//!   majority of "unsafety" lives in Wasmtime so reducing the need to lean on
35//!   this or audit another compiler is predicted to weed out a whole class of
36//!   bugs in the fused adapter compiler.
37//!
38//! * As mentioned above generation of WebAssembly modules means that this is
39//!   suitable for use in JS environments. For example a hypothetical tool which
40//!   polyfills a component onto the web today would need to do something for
41//!   adapter modules, and ideally the adapters themselves are speedy. While
42//!   this could all be written in JS the adapting process is quite nontrivial
43//!   so sharing code with Wasmtime would be ideal.
44//!
45//! * Using WebAssembly insulates the implementation to bugs to a certain
46//!   degree. While logic bugs are still possible it should be much more
47//!   difficult to have segfaults or things like that. With adapters exclusively
48//!   executing inside a WebAssembly sandbox like everything else the failure
49//!   modes to the host at least should be minimized.
50//!
51//! * Integration into the runtime is relatively simple, the adapter modules are
52//!   just another kind of wasm module to instantiate and wire up at runtime.
53//!   The goal is that the `GlobalInitializer` list that is processed at runtime
54//!   will have all of its `Adapter`-using variants erased by the time it makes
55//!   its way all the way up to Wasmtime. This means that the support in
56//!   Wasmtime prior to adapter modules is actually the same as the support
57//!   after adapter modules are added, keeping the runtime fiddly bits quite
58//!   minimal.
59//!
60//! This isn't to say that this approach isn't without its disadvantages of
61//! course. For now though this seems to be a reasonable set of tradeoffs for
62//! the development stage of the component model proposal.
63//!
64//! ## Creating adapter modules
65//!
66//! With WebAssembly itself being used to implement fused adapters, Wasmtime
67//! still has the question of how to organize the adapter functions into actual
68//! wasm modules.
69//!
70//! The first thing you might reach for is to put all the adapters into the same
71//! wasm module. This cannot be done, however, because some adapters may depend
72//! on other adapters (transitively) to be created. This means that if
73//! everything were in the same module there would be no way to instantiate the
74//! module. An example of this dependency is an adapter (A) used to create a
75//! core wasm instance (M) whose exported memory is then referenced by another
76//! adapter (B). In this situation the adapter B cannot be in the same module
77//! as adapter A because B needs the memory of M but M is created with A which
78//! would otherwise create a circular dependency.
79//!
80//! The second possibility of organizing adapter modules would be to place each
81//! fused adapter into its own module. Each `canon lower` would effectively
82//! become a core wasm module instantiation at that point. While this works it's
83//! currently believed to be a bit too fine-grained. For example it would mean
84//! that importing a dozen lowered functions into a module could possibly result
85//! in up to a dozen different adapter modules. While this possibility could
86//! work it has been ruled out as "probably too expensive at runtime".
87//!
88//! Thus the purpose and existence of this module is now evident -- this module
89//! exists to identify what exactly goes into which adapter module. This will
90//! evaluate the `GlobalInitializer` lists coming out of the `inline` pass and
91//! insert `InstantiateModule` entries for where adapter modules should be
92//! created.
93//!
94//! ## Partitioning adapter modules
95//!
96//! Currently this module does not attempt to be really all that fancy about
97//! grouping adapters into adapter modules. The main idea is that most items
98//! within an adapter module are likely to be close together since they're
99//! theoretically going to be used for an instantiation of a core wasm module
100//! just after the fused adapter was declared. With that in mind the current
101//! algorithm is a one-pass approach to partitioning everything into adapter
102//! modules.
103//!
104//! Adapters were identified in-order as part of the inlining phase of
105//! translation where we're guaranteed that once an adapter is identified
106//! it can't depend on anything identified later. The pass implemented here is
107//! to visit all transitive dependencies of an adapter. If one of the
108//! dependencies of an adapter is an adapter in the current adapter module
109//! being built then the current module is finished and a new adapter module is
110//! started. This should quickly partition adapters into contiugous chunks of
111//! their index space which can be in adapter modules together.
112//!
113//! There's probably more general algorithms for this but for now this should be
114//! fast enough as it's "just" a linear pass. As we get more components over
115//! time this may want to be revisited if too many adapter modules are being
116//! created.
117
118use crate::component::translate::*;
119use crate::fact;
120use crate::{EntityType, Memory};
121use std::collections::HashSet;
122
123/// Metadata information about a fused adapter.
124#[derive(Debug, Clone, Hash, Eq, PartialEq)]
125pub struct Adapter {
126    /// The type used when the original core wasm function was lifted.
127    ///
128    /// Note that this could be different than `lower_ty` (but still matches
129    /// according to subtyping rules).
130    pub lift_ty: TypeFuncIndex,
131    /// Canonical ABI options used when the function was lifted.
132    pub lift_options: AdapterOptions,
133    /// The type used when the function was lowered back into a core wasm
134    /// function.
135    ///
136    /// Note that this could be different than `lift_ty` (but still matches
137    /// according to subtyping rules).
138    pub lower_ty: TypeFuncIndex,
139    /// Canonical ABI options used when the function was lowered.
140    pub lower_options: AdapterOptions,
141    /// The original core wasm function which was lifted.
142    pub func: dfg::CoreDef,
143}
144
145/// The data model for objects that are not unboxed in locals.
146#[derive(Debug, Clone, Hash, Eq, PartialEq)]
147pub enum DataModel {
148    /// Data is stored in GC objects.
149    Gc {},
150
151    /// Data is stored in a linear memory.
152    LinearMemory {
153        /// An optional memory definition supplied, and its type.
154        memory: Option<(dfg::CoreExport<MemoryIndex>, Memory)>,
155        /// An optional definition of `realloc` to used.
156        realloc: Option<dfg::CoreDef>,
157    },
158}
159
160/// Configuration options which can be specified as part of the canonical ABI
161/// in the component model.
162#[derive(Debug, Clone, Hash, Eq, PartialEq)]
163pub struct AdapterOptions {
164    /// The Wasmtime-assigned component instance index where the options were
165    /// originally specified.
166    pub instance: RuntimeComponentInstanceIndex,
167    /// The ancestors (i.e. chain of instantiating instances) of the instance
168    /// specified in the `instance` field.
169    pub ancestors: Vec<RuntimeComponentInstanceIndex>,
170    /// How strings are encoded.
171    pub string_encoding: StringEncoding,
172    /// The async callback function used by these options, if specified.
173    pub callback: Option<dfg::CoreDef>,
174    /// An optional definition of a `post-return` to use.
175    pub post_return: Option<dfg::CoreDef>,
176    /// Whether to use the async ABI for lifting or lowering.
177    pub async_: bool,
178    /// Whether or not this intrinsic can consume a task cancellation
179    /// notification.
180    pub cancellable: bool,
181    /// The core function type that is being lifted from / lowered to.
182    pub core_type: ModuleInternedTypeIndex,
183    /// The data model used by this adapter: linear memory or GC objects.
184    pub data_model: DataModel,
185}
186
187impl<'data> Translator<'_, 'data> {
188    /// This is the entrypoint of functionality within this module which
189    /// performs all the work of identifying adapter usages and organizing
190    /// everything into adapter modules.
191    ///
192    /// This will mutate the provided `component` in-place and fill out the dfg
193    /// metadata for adapter modules.
194    pub(super) fn partition_adapter_modules(&mut self, component: &mut dfg::ComponentDfg) {
195        // Visit each adapter, in order of its original definition, during the
196        // partitioning. This allows for the guarantee that dependencies are
197        // visited in a topological fashion ideally.
198        let mut state = PartitionAdapterModules::default();
199        for (id, adapter) in component.adapters.iter() {
200            state.adapter(component, id, adapter);
201        }
202        state.finish_adapter_module();
203
204        // Now that all adapters have been partitioned into modules this loop
205        // generates a core wasm module for each adapter module, translates
206        // the module using standard core wasm translation, and then fills out
207        // the dfg metadata for each adapter.
208        for (module_id, adapter_module) in state.adapter_modules.iter() {
209            let mut module = fact::Module::new(self.types.types(), self.tunables);
210            let mut names = Vec::with_capacity(adapter_module.adapters.len());
211            for adapter in adapter_module.adapters.iter() {
212                let name = format!("adapter{}", adapter.as_u32());
213                module.adapt(&name, &component.adapters[*adapter]);
214                names.push(name);
215            }
216            let wasm = module.encode();
217            let imports = module.imports().to_vec();
218
219            // Extend the lifetime of the owned `wasm: Vec<u8>` on the stack to
220            // a higher scope defined by our original caller. That allows to
221            // transform `wasm` into `&'data [u8]` which is much easier to work
222            // with here.
223            let wasm = &*self.scope_vec.push(wasm);
224            if log::log_enabled!(log::Level::Trace) {
225                match wasmprinter::print_bytes(wasm) {
226                    Ok(s) => log::trace!("generated adapter module:\n{s}"),
227                    Err(e) => log::trace!("failed to print adapter module: {e}"),
228                }
229            }
230
231            // With the wasm binary this is then pushed through general
232            // translation, validation, etc. Note that multi-memory is
233            // specifically enabled here since the adapter module is highly
234            // likely to use that if anything is actually indirected through
235            // memory.
236            self.validator.reset();
237            let static_module_index = self.static_modules.next_key();
238            let translation = ModuleEnvironment::new(
239                self.tunables,
240                &mut self.validator,
241                self.types.module_types_builder(),
242                static_module_index,
243            )
244            .translate(Parser::new(0), wasm)
245            .expect("invalid adapter module generated");
246
247            // Record, for each adapter in this adapter module, the module that
248            // the adapter was placed within as well as the function index of
249            // the adapter in the wasm module generated. Note that adapters are
250            // partitioned in-order so we're guaranteed to push the adapters
251            // in-order here as well. (with an assert to double-check)
252            for (adapter, name) in adapter_module.adapters.iter().zip(&names) {
253                let name = translation.module.strings.get_atom(name).unwrap();
254                let export = translation.module.exports[&name];
255                let i = component.adapter_partitionings.push((module_id, export));
256                assert_eq!(i, *adapter);
257            }
258
259            // Finally the metadata necessary to instantiate this adapter
260            // module is also recorded in the dfg. This metadata will be used
261            // to generate `GlobalInitializer` entries during the linearization
262            // final phase.
263            assert_eq!(imports.len(), translation.module.imports().len());
264            let args = imports
265                .iter()
266                .zip(translation.module.imports())
267                .map(|(arg, (_, _, ty))| fact_import_to_core_def(component, arg, ty))
268                .collect::<Vec<_>>();
269            let static_module_index2 = self.static_modules.push(translation);
270            assert_eq!(static_module_index, static_module_index2);
271            let id = component.adapter_modules.push((static_module_index, args));
272            assert_eq!(id, module_id);
273        }
274    }
275}
276
277fn fact_import_to_core_def(
278    dfg: &mut dfg::ComponentDfg,
279    import: &fact::Import,
280    ty: EntityType,
281) -> dfg::CoreDef {
282    fn unwrap_memory(def: &dfg::CoreDef) -> dfg::CoreExport<MemoryIndex> {
283        match def {
284            dfg::CoreDef::Export(e) => e.clone().map_index(|i| match i {
285                EntityIndex::Memory(i) => i,
286                _ => unreachable!(),
287            }),
288            _ => unreachable!(),
289        }
290    }
291
292    let mut simple_intrinsic = |trampoline: dfg::Trampoline| {
293        let signature = ty.unwrap_func();
294        let index = dfg
295            .trampolines
296            .push((signature.unwrap_module_type_index(), trampoline));
297        dfg::CoreDef::Trampoline(index)
298    };
299    match import {
300        fact::Import::CoreDef(def) => def.clone(),
301        fact::Import::Transcode {
302            op,
303            from,
304            from64,
305            to,
306            to64,
307        } => {
308            let from = dfg.memories.push(unwrap_memory(from));
309            let to = dfg.memories.push(unwrap_memory(to));
310            let signature = ty.unwrap_func();
311            let index = dfg.trampolines.push((
312                signature.unwrap_module_type_index(),
313                dfg::Trampoline::Transcoder {
314                    op: *op,
315                    from,
316                    from64: *from64,
317                    to,
318                    to64: *to64,
319                },
320            ));
321            dfg::CoreDef::Trampoline(index)
322        }
323        fact::Import::ResourceTransferOwn => simple_intrinsic(dfg::Trampoline::ResourceTransferOwn),
324        fact::Import::ResourceTransferBorrow => {
325            simple_intrinsic(dfg::Trampoline::ResourceTransferBorrow)
326        }
327        fact::Import::PrepareCall { memory } => simple_intrinsic(dfg::Trampoline::PrepareCall {
328            memory: memory.as_ref().map(|v| dfg.memories.push(unwrap_memory(v))),
329        }),
330        fact::Import::SyncStartCall { callback } => {
331            simple_intrinsic(dfg::Trampoline::SyncStartCall {
332                callback: callback.clone().map(|v| dfg.callbacks.push(v)),
333            })
334        }
335        fact::Import::AsyncStartCall {
336            callback,
337            post_return,
338        } => simple_intrinsic(dfg::Trampoline::AsyncStartCall {
339            callback: callback.clone().map(|v| dfg.callbacks.push(v)),
340            post_return: post_return.clone().map(|v| dfg.post_returns.push(v)),
341        }),
342        fact::Import::FutureTransfer => simple_intrinsic(dfg::Trampoline::FutureTransfer),
343        fact::Import::StreamTransfer => simple_intrinsic(dfg::Trampoline::StreamTransfer),
344        fact::Import::ErrorContextTransfer => {
345            simple_intrinsic(dfg::Trampoline::ErrorContextTransfer)
346        }
347        fact::Import::Trap => simple_intrinsic(dfg::Trampoline::Trap),
348        fact::Import::EnterSyncCall => simple_intrinsic(dfg::Trampoline::EnterSyncCall),
349        fact::Import::ExitSyncCall => simple_intrinsic(dfg::Trampoline::ExitSyncCall),
350    }
351}
352
353#[derive(Default)]
354struct PartitionAdapterModules {
355    /// The next adapter module that's being created. This may be empty.
356    next_module: AdapterModuleInProgress,
357
358    /// The set of items which are known to be defined which the adapter module
359    /// in progress is allowed to depend on.
360    defined_items: HashSet<Def>,
361
362    /// Finished adapter modules that won't be added to.
363    ///
364    /// In theory items could be added to preexisting modules here but to keep
365    /// this pass linear this is never modified after insertion.
366    adapter_modules: PrimaryMap<dfg::AdapterModuleId, AdapterModuleInProgress>,
367}
368
369#[derive(Default)]
370struct AdapterModuleInProgress {
371    /// The adapters which have been placed into this module.
372    adapters: Vec<dfg::AdapterId>,
373}
374
375/// Items that adapters can depend on.
376///
377/// Note that this is somewhat of a flat list and is intended to mostly model
378/// core wasm instances which are side-effectful unlike other host items like
379/// lowerings or always-trapping functions.
380#[derive(Copy, Clone, Hash, Eq, PartialEq)]
381enum Def {
382    Adapter(dfg::AdapterId),
383    Instance(dfg::InstanceId),
384}
385
386impl PartitionAdapterModules {
387    fn adapter(&mut self, dfg: &dfg::ComponentDfg, id: dfg::AdapterId, adapter: &Adapter) {
388        // Visit all dependencies of this adapter and if anything depends on
389        // the current adapter module in progress then a new adapter module is
390        // started.
391        self.adapter_options(dfg, &adapter.lift_options);
392        self.adapter_options(dfg, &adapter.lower_options);
393        self.core_def(dfg, &adapter.func);
394
395        // With all dependencies visited this adapter is added to the next
396        // module.
397        //
398        // This will either get added the preexisting module if this adapter
399        // didn't depend on anything in that module itself or it will be added
400        // to a fresh module if this adapter depended on something that the
401        // current adapter module created.
402        log::debug!("adding {id:?} to adapter module");
403        self.next_module.adapters.push(id);
404    }
405
406    fn adapter_options(&mut self, dfg: &dfg::ComponentDfg, options: &AdapterOptions) {
407        if let Some(def) = &options.callback {
408            self.core_def(dfg, def);
409        }
410        if let Some(def) = &options.post_return {
411            self.core_def(dfg, def);
412        }
413        match &options.data_model {
414            DataModel::Gc {} => {
415                // Nothing to do here yet.
416            }
417            DataModel::LinearMemory { memory, realloc } => {
418                if let Some((memory, _ty)) = memory {
419                    self.core_export(dfg, memory);
420                }
421                if let Some(def) = realloc {
422                    self.core_def(dfg, def);
423                }
424            }
425        }
426    }
427
428    fn core_def(&mut self, dfg: &dfg::ComponentDfg, def: &dfg::CoreDef) {
429        match def {
430            dfg::CoreDef::Export(e) => self.core_export(dfg, e),
431            dfg::CoreDef::Adapter(id) => {
432                // If this adapter is already defined then we can safely depend
433                // on it with no consequences.
434                if self.defined_items.contains(&Def::Adapter(*id)) {
435                    log::debug!("using existing adapter {id:?} ");
436                    return;
437                }
438
439                log::debug!("splitting module needing {id:?} ");
440
441                // .. otherwise we found a case of an adapter depending on an
442                // adapter-module-in-progress meaning that the current adapter
443                // module must be completed and then a new one is started.
444                self.finish_adapter_module();
445                assert!(self.defined_items.contains(&Def::Adapter(*id)));
446            }
447
448            // These items can't transitively depend on an adapter
449            dfg::CoreDef::Trampoline(_)
450            | dfg::CoreDef::InstanceFlags(_)
451            | dfg::CoreDef::UnsafeIntrinsic(..)
452            | dfg::CoreDef::TaskMayBlock => {}
453        }
454    }
455
456    fn core_export<T>(&mut self, dfg: &dfg::ComponentDfg, export: &dfg::CoreExport<T>) {
457        // When an adapter depends on an exported item it actually depends on
458        // the instance of that exported item. The caveat here is that the
459        // adapter not only depends on that particular instance, but also all
460        // prior instances to that instance as well because instance
461        // instantiation order is fixed and cannot change.
462        //
463        // To model this the instance index space is looped over here and while
464        // an instance hasn't been visited it's visited. Note that if an
465        // instance has already been visited then all prior instances have
466        // already been visited so there's no need to continue.
467        let mut instance = export.instance;
468        while self.defined_items.insert(Def::Instance(instance)) {
469            self.instance(dfg, instance);
470            if instance.as_u32() == 0 {
471                break;
472            }
473            instance = dfg::InstanceId::from_u32(instance.as_u32() - 1);
474        }
475    }
476
477    fn instance(&mut self, dfg: &dfg::ComponentDfg, instance: dfg::InstanceId) {
478        log::debug!("visiting instance {instance:?}");
479
480        // ... otherwise if this is the first timet he instance has been seen
481        // then the instances own arguments are recursively visited to find
482        // transitive dependencies on adapters.
483        match &dfg.instances[instance] {
484            dfg::Instance::Static(_, args) => {
485                for arg in args.iter() {
486                    self.core_def(dfg, arg);
487                }
488            }
489            dfg::Instance::Import(_, args) => {
490                for (_, values) in args {
491                    for (_, def) in values {
492                        self.core_def(dfg, def);
493                    }
494                }
495            }
496        }
497    }
498
499    fn finish_adapter_module(&mut self) {
500        if self.next_module.adapters.is_empty() {
501            return;
502        }
503
504        // Reset the state of the current module-in-progress and then flag all
505        // pending adapters as now defined since the current module is being
506        // committed.
507        let module = mem::take(&mut self.next_module);
508        for adapter in module.adapters.iter() {
509            let inserted = self.defined_items.insert(Def::Adapter(*adapter));
510            assert!(inserted);
511        }
512        let idx = self.adapter_modules.push(module);
513        log::debug!("finishing adapter module {idx:?}");
514    }
515}