| commit | 3a56a55ccb2e31e3a52d74db2ddd8ea603ea667b | |
| author | David Gibson <david@gibson.dropbear.id.au> | |
| Mon, 6 Jan 2020 06:26:24 +0000 (6 17:26 +1100) | ||
| committer | David Gibson <david@gibson.dropbear.id.au> | |
| Mon, 16 Mar 2020 22:41:15 +0000 (17 09:41 +1100) | ||
| tree | 3be220e10e3b668ce3939eef60727592db192e96 | treesnapshot (tar.gz zip) |
| parent | d37b40daf647aaf2f5e4c4dfcd62c9412ff05009 | commitdiff |
target/ppc: Only calculate RMLS derived RMA limit on demand
When the LPCR is written, we update the env->rmls field with the RMA limit
it implies. Simplify things by just calculating the value directly from
the LPCR value when we need it.
It's possible this is a little slower, but it's unlikely to be significant,
since this is only for real mode accesses in a translation configuration
that's not used very often, and the whole thing is behind the qemu TLB
anyway. Therefore, keeping the number of state variables down and not
having to worry about making sure it's always in sync seems the better
option.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
When the LPCR is written, we update the env->rmls field with the RMA limit
it implies. Simplify things by just calculating the value directly from
the LPCR value when we need it.
It's possible this is a little slower, but it's unlikely to be significant,
since this is only for real mode accesses in a translation configuration
that's not used very often, and the whole thing is behind the qemu TLB
anyway. Therefore, keeping the number of state variables down and not
having to worry about making sure it's always in sync seems the better
option.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
| target/ppc/cpu.h | diffblobblamehistory | |
| target/ppc/mmu-hash64.c | diffblobblamehistory |