Currently the kdump_core_collector accepts values such as makedumpfile -l --message-level 2 -d 30 that we demo in presentations. Since the system roles are also about abstractions, it would make sense to expose the command-line options for makedumpfile as individual variables, especially the bitmap specified after -d could be exposed as the following booleans:
kdump_dump_zero_pageskdump_dump_non_private_cachekdump_dump_private_cachekdump_dump_user_datakdump_dump_free_pages
And a sensible default could be used.
Currently the kdump_core_collector accepts values such as
makedumpfile -l --message-level 2 -d 30that we demo in presentations. Since the system roles are also about abstractions, it would make sense to expose the command-line options for makedumpfile as individual variables, especially the bitmap specified after-dcould be exposed as the following booleans:kdump_dump_zero_pageskdump_dump_non_private_cachekdump_dump_private_cachekdump_dump_user_datakdump_dump_free_pagesAnd a sensible default could be used.