Struct devices::virtio::pvclock::PvClockWorker

struct PvClockWorker {
    tsc_frequency: u64,
    suspend_time: Option<PvclockInstant>,
    total_injected_ns: Arc<AtomicU64>,
    total_suspend_tsc_delta: u64,
    pvclock_shared_data: Option<PvclockSharedData>,
    mem: GuestMemory,
}

Worker struct for the virtio-pvclock device.

Handles virtio requests, storing information about suspend/resume, adjusting the pvclock data in shared memory, and injecting suspend durations via config changes.

Fields

tsc_frequency: u64

suspend_time: Option<PvclockInstant>

total_injected_ns: Arc<AtomicU64>

total_suspend_tsc_delta: u64

pvclock_shared_data: Option<PvclockSharedData>

mem: GuestMemory

Implementations

impl PvClockWorker

pub fn new( tsc_frequency: u64, total_injected_ns: Arc<AtomicU64>, mem: GuestMemory ) -> Self

fn from_snapshot( tsc_frequency: u64, total_injected_ns: Arc<AtomicU64>, snap: PvClockWorkerSnapshot, mem: GuestMemory ) -> Self

fn set_pvclock_page(&mut self, addr: u64) -> Result<()>

Initialize the pvclock for initial boot. We assume that the systemtime of 0 corresponds to the tsc time of 0, so we do not set these. We set the tsc frequency based on the vcpu tsc frequency and we set PVCLOCK_TSC_STABLE_BIT in flags to tell the guest that it’s safe to use vcpu0’s pvclock page for use by the vdso. The order of writing the different fields doesn’t matter at this point, but does matter when updating.

pub fn suspend(&mut self)

pub fn resume(&mut self) -> Result<u64>

fn get_suspended_duration(suspend_time: &PvclockInstant) -> Duration

fn set_suspended_time(&mut self) -> Result<u64>

fn increment_pvclock_seqlock(&mut self) -> Result<()>

fn set_guest_stopped_bit(&mut self) -> Result<()>

Trait Implementations

impl From<PvClockWorker> for PvClockWorkerSnapshot

fn from(worker: PvClockWorker) -> Self

Converts to this type from the input type.