Page MenuHomeFreeBSD

Add missing pmap dsb instructions
ClosedPublic

Authored by andrew on Feb 7 2019, 9:53 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Mar 30, 6:13 AM
Unknown Object (File)
Feb 24 2024, 7:35 PM
Unknown Object (File)
Jan 28 2024, 2:39 PM
Unknown Object (File)
Dec 21 2023, 12:30 PM
Unknown Object (File)
Dec 18 2023, 8:19 AM
Unknown Object (File)
Nov 21 2023, 7:11 AM
Unknown Object (File)
Nov 5 2023, 5:32 PM
Unknown Object (File)
Nov 4 2023, 11:57 PM
Subscribers

Details

Summary

We need them in arm64_tlb_flushID when clearing the TLB and after pagetable
stores when moving from an invalid to valid entry. The latter don't call
any of the pmap_invalidate_* functions.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This fixes the failure on ThunderX2 when INVARIANTS are turned off. The failure was:

panic: vm_fault_hold: fault on nofault entry, addr: 0xffff000040c11000
cpuid = 0
time = 1

Tested with overnight 'make -j 224 buildworld' without failures.
This is more of a 'Tested by' - I don't have enough background here to do a full review. My understanding of ARM spec is you need a dsb after a update of valid pte/pde, before access to the page. ThunderX2 has full out of order execution with weakly ordered loads and stores - so the failure above points to a missing barrier.

This revision is now accepted and ready to land.Feb 7 2019, 6:52 PM

Tested with overnight 'make -j 224 buildworld' without failures.

How long does that take?

This is more of a 'Tested by' - I don't have enough background here to do a full review. My understanding of ARM spec is you need a dsb after a update of valid pte/pde, before access to the page. ThunderX2 has full out of order execution with weakly ordered loads and stores - so the failure above points to a missing barrier.

We need one whenever we create a valid page. In many cases there was one because of the call to pmap_invalidate_* functions, however a few were missed.

This revision was automatically updated to reflect the committed changes.
This revision was not accepted when it landed; it landed in state Needs Review.Feb 7 2019, 8:59 PM
This revision was automatically updated to reflect the committed changes.

Tested with overnight 'make -j 224 buildworld' without failures.

How long does that take?

buildworld takes around 30 minutes now, but I don't see the CPUs getting fully loaded. I think this can be improved quite a bit with some profiling.