I suggest this for the shortlog KVM: selftests: Make sparsebit structs const where appropriate Three deep scopes are a net negative IMO. Too much of the shortlog is consumed by the scope, and very few patches are actually capable of such precision, i.e. touch more than a single area. On Tue, Jan 10, 2023, Peter Gonda wrote: > From: Michael Roth <michael.roth@xxxxxxx> > > Subsequent patches will introduce an encryption bitmap in kvm_util that protected memory, not encryption > would be useful to allow tests to access in read-only fashion. This > will be done via a const sparsebit*. To avoid warnings or the need to > add casts everywhere, add const to the various sparsebit functions that > are applicable for read-only usage of sparsebit.
