caprevoke: remove store side revocation #1743
Commits on Sep 7, 2023
-
-
cheribsdtest: remove cheri_revoke_capdirty
This test depends on store-side behavior which will be removed shortly.
-
cheri_revoke(2): remove load/store-side interface
Always revoke load-side. CHERI_REVOKE_FORCE_LOAD_SIDE and CHERI_REVOKE_FORCE_STORE_SIDE are no longer defined and currently ignored as flags. We should likely restrict flags to valids ones for the release.
-
caprevoke: remove store-side states
Delete the CHERI_REVOKE_ST_SS_* states from the enum and remove all code that referenced them.
-
caprevoke: remove VM_CHERI_REVOKE_INCREMENTAL flag
Nothing sets this any more so remove it and the code that depends on it.
-
cheri_revoke(2): remove CHERI_REVOKE_EARLY_SYNC
This was a store-side specific flag so remove it.
-
-
-
caprevoke: reclaim a bit from revoker state
We can now revoke 2^60 times more before the epoch counter wraps...
-
kern_cheri_revoke: rename close_already_inited
Drop the ls_ prefix as we're always doing load-side revocation. Add an comment on the cause of the goto since I spent quite a few minutes failing to parse the label.
-
caprevoke: remove a few mentions of load-side
We're always doing load-side revocation so there's no need to keep it.
-
caprevoke: remove VM_CHERI_REVOKE_LOAD_SIDE flag
We're always doing a load-side scan so drop the flag to indicate we're doing one.
-
caprevoke: remove VM_CHERI_REVOKE_TLB_FLUSH flag
This flag was unused so drop it.
-
vm_cheri_revoke_pass: compress flag space
More flags have been removed so renumber the remaining ones. It might make sense to remove VM_CHERI_REVOKE_BARRIERED as it's implemented, but unused. For now keep it as it's described as a debug flag.
-
caprevoke: rewrite state machine comment
The whole comment was store side focused with an aside about the possibility of load side revocation. Rewrite to be be purely load side.
-
-
Installing all kernels by their own name is useful, but not what we're merging so remove from the branch.
-
cheribsdtest: Trim verbose stats
These are useful in the development branch long with cycle counts, but probably not something we want in production.
-
FETT: remove nonsense std.CHERI-CAPREVOKE include
std.CHERI-CAPREVOKE doesn't do anyting useful without CHERI support.
-
morello: Default to enabling CAPREVOKE
Make GENERIC-MORELLO include std.CHERI-CAPREVOKE. Add -NOCAPREVOKE variants that disable CAPREVOKE entierly. To aid script transitions, retain -CAPREVOKE variants. Update them to assume they inherit CAPREVOKE from GENERIC-MORELLO.
-
morello: Remove -CAPREVOKE kernel variants
GENERIC-MORELLO now enables CAPREVOKE so we don't need these.
-
morello: Expand std.CHERI-CAPREVOKE in place
Add the contents of std.CHERI-CAPREVOKE to GENERIC-MORELLO and remove std.CHERI-CAPREVOKE.
-
riscv: Default to enabling CAPREVOKE
Make std.CHERI include std.CHERI-CAPREVOKE. Add -NOCAPREVOKE variants that disable CAPREVOKE entierly. To aid script transitions, retain -CAPREVOKE variants. Update them to assume they inherit CAPREVOKE from std.CHERI.
-
riscv: Remove -CAPREVOKE kernel variants
All non-NOCAPREVOKE kernels now enable CAPREVOKE so they are unneeded.
-
riscv: Expand std.CHERI-CAPREVOKE in place
Add the contents of std.CHERI-CAPREVOKE to std.CHERI and remove std.CHERI-CAPREVOKE.
