Lines Matching refs:guest

40 Inputs from the guest or external sources (e.g. network, files) cannot be
42 that could crash the program, expose host memory to the guest, or otherwise be
46 accesses and data read from guest memory must be validated.  A typical example
47 is a device that contains multiple units that are selectable by the guest via
73 The guest may access device registers in unusual orders or at unexpected
74 moments.  Device emulation code must not assume that the guest follows the
75 typical "theory of operation" presented in driver writer manuals.  The guest
81 well-behaved guest might wait for a completion interrupt before accessing
83 guest overwrites registers or submits further requests before an ongoing
101 Guests with multiple vCPUs may modify guest RAM while device emulation code is
102 running.  Device emulation code must copy in descriptors and other guest RAM
105 crash when a vCPU thread modifies guest RAM while device emulation is