diff options
author | Jani Nikula <jani.nikula@intel.com> | 2024-09-30 11:49:10 +0300 |
---|---|---|
committer | Jani Nikula <jani.nikula@intel.com> | 2024-09-30 11:49:10 +0300 |
commit | e0568571258d096f0277c74185bcbfc9cf21bccb (patch) | |
tree | a380953643dbb86bffaa862d11e58eba22697988 /Documentation/dev-tools/kfence.rst | |
parent | 9d5a05f86d2f4f81abcac6abc856c0d511a8607b (diff) | |
parent | 9852d85ec9d492ebef56dc5f229416c925758edc (diff) |
Merge drm/drm-next into drm-intel-next
Sync to v6.12-rc1.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'Documentation/dev-tools/kfence.rst')
-rw-r--r-- | Documentation/dev-tools/kfence.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/dev-tools/kfence.rst b/Documentation/dev-tools/kfence.rst index 936f6aaa75c8..541899353865 100644 --- a/Documentation/dev-tools/kfence.rst +++ b/Documentation/dev-tools/kfence.rst @@ -53,6 +53,13 @@ configurable via the Kconfig option ``CONFIG_KFENCE_DEFERRABLE``. The KUnit test suite is very likely to fail when using a deferrable timer since it currently causes very unpredictable sample intervals. +By default KFENCE will only sample 1 heap allocation within each sample +interval. *Burst mode* allows to sample successive heap allocations, where the +kernel boot parameter ``kfence.burst`` can be set to a non-zero value which +denotes the *additional* successive allocations within a sample interval; +setting ``kfence.burst=N`` means that ``1 + N`` successive allocations are +attempted through KFENCE for each sample interval. + The KFENCE memory pool is of fixed size, and if the pool is exhausted, no further KFENCE allocations occur. With ``CONFIG_KFENCE_NUM_OBJECTS`` (default 255), the number of available guarded objects can be controlled. Each object |