Re: [OS-BUILD PATCH] [redhat] New configs in kernel/trace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 6/10/20 12:38 AM, GitLab Bridge on behalf of jeremycline wrote:
> From: Fedora Kernel Team <kernel-team@xxxxxxxxxxxxxxxxx>
>

Adding jmarchan

P.

> Hi,
>
> As part of the ongoing rebase effort, the following configuration
> options need to be reviewed.
>
> As a reminder, the ARK configuration flow involves moving unreviewed
> configuration options from the pending directory to the ark directory.
> In the diff below, options are removed from the pending directory and
> added to the ark hierarchy. The final options that need to be ACKed
> are the files that are being added to the ark hierarchy.
>
> If the value for a file that is added should be changed, please reply
> with a better option.
>
>  CONFIG_HIST_TRIGGERS_DEBUG:
>
>  Add "hist_debug" file for each event, which when read will
>  dump out a bunch of internal details about the hist triggers
>  defined on that event.
>
>  The hist_debug file serves a couple of purposes:
>
>    - Helps developers verify that nothing is broken.
>
>    - Provides educational information to support the details
>      of the hist trigger internals as described by
>      Documentation/trace/histogram-design.rst.
>
>  The hist_debug output only covers the data structures
>  related to the histogram definitions themselves and doesn't
>  display the internals of map buckets or variable values of
>  running histograms.
>
>  If unsure, say N.
>
>  Symbol: HIST_TRIGGERS_DEBUG [=n]
>  Type  : bool
>  Defined at kernel/trace/Kconfig:850
>    Prompt: Hist trigger debug support
>    Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && HIST_TRIGGERS [=y]
>    Location:
>      -> Kernel hacking
>        -> Tracers (FTRACE [=y])
>
> ---
>
> Signed-off-by: Fedora Kernel Team <kernel-team@xxxxxxxxxxxxxxxxx>
> ---
>  .../common/generic/CONFIG_HIST_TRIGGERS_DEBUG |  1 +
>  .../generic/CONFIG_HIST_TRIGGERS_DEBUG        | 33 -------------------
>  2 files changed, 1 insertion(+), 33 deletions(-)
>  create mode 100644 redhat/configs/common/generic/CONFIG_HIST_TRIGGERS_DEBUG
>  delete mode 100644
redhat/configs/pending-common/generic/CONFIG_HIST_TRIGGERS_DEBUG
>
> diff --git a/redhat/configs/common/generic/CONFIG_HIST_TRIGGERS_DEBUG
b/redhat/configs/common/generic/CONFIG_HIST_TRIGGERS_DEBUG
> new file mode 100644
> index 000000000000..a6a06ed369a0
> --- /dev/null
> +++ b/redhat/configs/common/generic/CONFIG_HIST_TRIGGERS_DEBUG
> @@ -0,0 +1 @@
> +# CONFIG_HIST_TRIGGERS_DEBUG is not set
> diff --git a/redhat/configs/pending-common/generic/CONFIG_HIST_TRIGGERS_DEBUG
b/redhat/configs/pending-common/generic/CONFIG_HIST_TRIGGERS_DEBUG
> deleted file mode 100644
> index 7634345b6a98..000000000000
> --- a/redhat/configs/pending-common/generic/CONFIG_HIST_TRIGGERS_DEBUG
> +++ /dev/null
> @@ -1,33 +0,0 @@
> -# CONFIG_HIST_TRIGGERS_DEBUG:
> -#
> -# Add "hist_debug" file for each event, which when read will
> -# dump out a bunch of internal details about the hist triggers
> -# defined on that event.
> -#
> -# The hist_debug file serves a couple of purposes:
> -#
> -#   - Helps developers verify that nothing is broken.
> -#
> -#   - Provides educational information to support the details
> -#     of the hist trigger internals as described by
> -#     Documentation/trace/histogram-design.rst.
> -#
> -# The hist_debug output only covers the data structures
> -# related to the histogram definitions themselves and doesn't
> -# display the internals of map buckets or variable values of
> -# running histograms.
> -#
> -# If unsure, say N.
> -#
> -# Symbol: HIST_TRIGGERS_DEBUG [=n]
> -# Type  : bool
> -# Defined at kernel/trace/Kconfig:850
> -#   Prompt: Hist trigger debug support
> -#   Depends on: TRACING_SUPPORT [=y] && FTRACE [=y] && HIST_TRIGGERS [=y]
> -#   Location:
> -#     -> Kernel hacking
> -#       -> Tracers (FTRACE [=y])
> -#
> -#
> -#
> -# CONFIG_HIST_TRIGGERS_DEBUG is not set
>
_______________________________________________
kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux