Lines Matching full:guest
58 After execution of the new BB, all guest state and guest memory is
62 In addition, parts of the guest state will be identical to that
66 * In a dirty helper call, any parts of the guest state that the
68 Also, guest memory will be up to date. Parts of the guest state
73 The guest state is only up to date only as explained above
80 Immediately prior to any load or store, those parts of the guest
82 Also, guest memory will be up to date. Parts of the guest state
87 Same as minimal, but all the guest state is up to date at memory
91 Guest state is up to date at each instruction.
94 guest memory done by dirty helpers annotated as such) is not
148 assumed not to write parts of the guest state that we need to have
149 up-to-date at loads/stores. So far on x86 guest that has not
163 is important for getting good performance for x86 guest code.
552 /* Extract the min/max offsets from a guest state array descriptor. */
679 /* Deal with dirty helpers which write or modify guest state.
759 environment. The helper might read guest state, in which
761 access guest memory, in which case all parts of the guest
824 of the environment corresponding to guest state that may not
830 Flush all guest state. */
863 offset) pairs, indicating those parts of the guest state
874 which implicitly read parts of the guest state: dirty helper calls
909 doesn't overlap with the guest state written by this exit.
977 of the guest state is no longer a write, but a read. Also
978 deals with implicit reads of guest state needed to maintain
1024 keep track of changes in the guest state and memory. Thusly, two
1027 at different times and the guest state / memory can have changed in
1070 /* Guest state / memory could have changed in the meantime. */
3150 /*--- Determination of guest state aliasing relationships ---*/
3156 guest state accesses. The possible outcomes are:
3159 piece of the guest state.
3162 overlap any part of the guest state.
3173 /* Produces the alias relation between an indexed guest
3195 /* Produces the alias relation between two indexed guest state
4083 exactly the same piece of guest state, and so return the expression
4113 overlapping any part of the indexed guest state. */
4127 an area of guest state which is read by a GetI. Which
4130 /* This Put potentially writes guest state that the GetI
4153 /* We don't know if this PutI writes to the same guest
4165 /* Be conservative. If the dirty call has any guest effects at
4167 are any guest writes/modifies. */
4181 that it writes exactly the same piece of guest state) ? Safe
4239 /* If the dirty call has any guest effects at all, give up.
4376 * If a dirty helper call which might write guest state, give up.
4573 X and Y must be literal (guest) addresses.
4636 /* Extract the next-guest address. If it isn't a literal, we
4802 /* An interval. Used to record the bytes in the guest state accessed
4848 /* Record the bytes of the guest state BINDEE reads from. */
5489 /* Passing the guest state pointer opens the door to modifying the
5490 guest state under the covers. It's not allowed, but let's be
5495 /* Assume all guest state is written. */
5503 /* Check the side effects on the guest state */
5527 /* Return an interval if st modifies the guest state. Via requiresPreciseMemExns
5595 opportunity to also find the maximum guest address in the block,
5749 updates the IP in the guest state. If the load generates
