-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mm/validate: fully migrate and clear bitmap & other cleanups #134
Conversation
@joergroedel I think this is ready to be merged |
@00xc This breaks |
Bisection points at
|
Only happens in debug builds, so I suspect some debug assertion is being triggered. |
I'm working on a bigger rework of the bitmap to increase safety. |
Remove useless pub identifiers on methods on the private ValidBitmap struct. Signed-off-by: Carlos López <carlos.lopez@suse.com>
If the number of pages in the bitmap was not a multiple of 64, the remainder would not be copied over to the new bitmap during migration, which could lead to tracking validated pages as invalid. Signed-off-by: Carlos López <carlos.lopez@suse.com>
The offsets are always positive from the start of the bitmap, so use an unsigned type. Signed-off-by: Carlos López <carlos.lopez@suse.com>
Turns out my assumption on 498b599 was wrong, things should work now. I'll push my rework of the bitmap to a separate PR. |
pub
onValidBitmap
methods.usize
to index into the bitmap, as offsets are always positive.