| commit | 372dbdb90c2cbe391d98649ca1f91a57b268b613 | |
| author | Nicholas Piggin <npiggin@gmail.com> | |
| Mon, 13 Nov 2023 13:02:45 +0000 (13 23:02 +1000) | ||
| committer | Nicholas Piggin <npiggin@gmail.com> | |
| Fri, 23 Feb 2024 13:24:43 +0000 (23 23:24 +1000) | ||
| tree | 0e632df8ea0aefbfe1be829646f8002f837c8172 | treesnapshot (tar.gz zip) |
| parent | c191ad779372cc3b355ef10a355de8bb9b92efdc | commitdiff |
target/ppc: 4xx don't flush TLB for a newly written software TLB entry
BookE software TLB is implemented by flushing old translations from the
relevant TCG TLB whenever software TLB entries change. This means a new
software TLB entry should not have any corresponding cached TCG TLB
translations, so there is nothing to flush. The exception is multiple
software TLBs that cover the same address and address space, but that is
a programming error and results in undefined behaviour, and flushing
does not give an obviously better outcome in that case either.
Remove the unnecessary flush of a newly written software TLB entry.
Tested-by: BALATON Zoltan <balaton@eik.bme.hu>
Acked-by: Cédric Le Goater <clg@kaod.org>
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
BookE software TLB is implemented by flushing old translations from the
relevant TCG TLB whenever software TLB entries change. This means a new
software TLB entry should not have any corresponding cached TCG TLB
translations, so there is nothing to flush. The exception is multiple
software TLBs that cover the same address and address space, but that is
a programming error and results in undefined behaviour, and flushing
does not give an obviously better outcome in that case either.
Remove the unnecessary flush of a newly written software TLB entry.
Tested-by: BALATON Zoltan <balaton@eik.bme.hu>
Acked-by: Cédric Le Goater <clg@kaod.org>
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
| target/ppc/mmu_helper.c | diffblobblamehistory |