diff options
author | Alex Bennée <alex.bennee@linaro.org> | 2016-11-14 14:19:17 +0000 |
---|---|---|
committer | Alex Bennée <alex.bennee@linaro.org> | 2017-01-13 14:24:31 +0000 |
commit | 1f5c00cfdb8114c1e3a13426588ceb64f82c9ddb (patch) | |
tree | a2cdd1a75d613b7509e7968cd973c30d383c1186 /bootdevice.c | |
parent | b6c08970bc989bfddcf830684ea7a96b7a4d62a7 (diff) | |
download | qemu-1f5c00cfdb8114c1e3a13426588ceb64f82c9ddb.zip qemu-1f5c00cfdb8114c1e3a13426588ceb64f82c9ddb.tar.gz qemu-1f5c00cfdb8114c1e3a13426588ceb64f82c9ddb.tar.bz2 |
qom/cpu: move tlb_flush to cpu_common_reset
It is a common thing amongst the various cpu reset functions want to
flush the SoftMMU's TLB entries. This is done either by calling
tlb_flush directly or by way of a general memset of the CPU
structure (sometimes both).
This moves the tlb_flush call to the common reset function and
additionally ensures it is only done for the CONFIG_SOFTMMU case and
when tcg is enabled.
In some target cases we add an empty end_of_reset_fields structure to the
target vCPU structure so have a clear end point for any memset which
is resetting value in the structure before CPU_COMMON (where the TLB
structures are).
While this is a nice clean-up in general it is also a precursor for
changes coming to cputlb for MTTCG where the clearing of entries
can't be done arbitrarily across vCPUs. Currently the cpu_reset
function is usually called from the context of another vCPU as the
architectural power up sequence is run. By using the cputlb API
functions we can ensure the right behaviour in the future.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Richard Henderson <rth@twiddle.net>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'bootdevice.c')
0 files changed, 0 insertions, 0 deletions