Lines Matching full:shadow
119 /* All reads and writes are checked against a memory map (a.k.a. shadow
153 writing shadow memory. Only a couple are strictly necessary (eg.
197 // compression scheme to reduce the size of shadow memory. Each byte of
231 // need to be explicit to made the shadow operations possible. Therefore
826 // (PDBs) that are represented by VA_BITS2_PARTDEFINED in the main shadow
1989 Origin tags and ECUs -- about the shadow values
2057 that shows which of the 4 bytes have that shadow value and which
2058 have a shadow value of zero (indicating no origin). Hence a lot of
2075 Shadowing registers is a bit tricky, because the shadow values are
2079 shadow guest state fragments smaller than 32 bits. For example, on
2081 shadow are allocated for the register's otag, then there are still
2082 12 bytes left over which could be used to shadow 3 other values.
2085 (start,length) pairs to the relevant shadow offset (for the origin
2102 schemeS merely arranges to move shadow values around the guest
2217 1. It becomes hard to shadow any element of guest state which is
2220 shadow, and use that instead to hold the otag. On ppc64, the
2234 2. (More compelling) it doubles the size of the origin shadow
2235 memory. Given that the shadow memory is organised as a fixed
4152 shadow area as valid. This is used to initialise arbitrarily large
4174 /* Look at the definedness of the guest's shadow state for
5311 // Cleverness 1: sometimes we don't have to write the shadow memory at
7578 " memcheck: max shadow mem size: %luk, %luM\n",
