Searched refs:VMState (Results 1 – 8 of 8) sorted by relevance
145 pub unsafe trait VMState { interface168 pub const fn vmstate_scalar_type<T: VMState>(_: PhantomData<T>) -> VMStateFieldType { in vmstate_scalar_type()174 pub const fn vmstate_base<T: VMState>(_: PhantomData<T>) -> VMStateField { in vmstate_base()181 pub const fn vmstate_varray_flag<T: VMState>(_: PhantomData<T>) -> VMStateFlags { in vmstate_varray_flag()317 unsafe impl $crate::vmstate::VMState for $tuple {329 ($type:ty where $base:tt: VMState $($where:tt)*) => {330 unsafe impl<$base> VMState for $type where $base: VMState $($where)* { impl331 const SCALAR_TYPE: VMStateFieldType = <$base as VMState>::SCALAR_TYPE;334 ..<$base as VMState>::BASE336 const VARRAY_FLAG: VMStateFlags = <$base as VMState>::VARRAY_FLAG;[all …]
29 pub use crate::vmstate::VMState;
38 via VMState wrapper on75 via VMState wrapper on
147 VMState section in Saving the state of one device189 The VMState macros take care of ensuring that the device data section193 VMState macros can include other VMStateDescriptions to store substructures224 Note that because the VMState macros still save the data in a raw226 with a carefully constructed VMState description that matches the357 Sometimes members of the VMState are no longer needed:400 - ``version_id``: the maximum version_id supported by VMState for that device.401 - ``minimum_version_id``: the minimum version_id that VMState is able to understand404 VMState is able to read versions from minimum_version_id to version_id.484 The iterative devices generally don't use VMState macros
2 D-Bus VMState
182 the value of VGIA is persisted via the VMState mechanism.
96 architecture (VMState). Right now, VMState lacks type safety because
349 mandatory for VMState fields.