Closed julianbraha closed 2 years ago
Thanks @julianbraha, yeah I guess I was aware that that wasn't the best way to do it but I didn't want CONFIG_HORIZON to be disabled implicitly due to this dependency. I agree this is probably more correct though, I will just make it clear in the wiki page that CONFIG_TRANSPARENT_HUGEPAGE
needs to be disabled.
I didn't want CONFIG_HORIZON to be disabled implicitly due to this dependency
This is a good point. I've created #2 to add a default horizon configuration.
When
CONFIG_HORIZON
is enabled in the kernel configuration, it force-enablesCONFIG_MEM_SOFT_DIRTY
without ensuring that its dependencies (CONFIG_TRANSPARENT_HUGEPAGE=n
andCONFIG_CHECKPOINT_RESTORE=y
) are satisfied.The solution: we can safely force-enable
CONFIG_CHECKPOINT_RESTORE
too, but since we cannot force-disableCONFIG_TRANSPARENT_HUGEPAGE
, we candepend on
disabling it.The other option would be to make
CONFIG_HORIZON
usedepends on MEM_SOFT_DIRTY
instead ofselect MEM_SOFT_DIRTY
, but this would require more effort on the user's part.