Re: [Xen-devel] [PATCH 05/15] xen: make it possible to disable tracing in Kconfig.

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 01.06.17 at 19:34, <dario.faggioli@xxxxxxxxxx> wrote:
> --- a/xen/Kconfig.debug
> +++ b/xen/Kconfig.debug
> @@ -98,6 +98,14 @@ config PERF_ARRAYS
>       ---help---
>         Enables software performance counter array histograms.
>  
> +config TRACING
> +     bool "Tracing"
> +     default y

default DEBUG (you don't want to suggest turning it on for a
release build)

> --- a/xen/common/trace.c
> +++ b/xen/common/trace.c
> @@ -48,6 +48,11 @@ static unsigned int opt_tevt_mask;
>  integer_param("tbuf_size", opt_tbuf_size);
>  integer_param("tevt_mask", opt_tevt_mask);
>  
> +#ifdef CONFIG_TRACING
> +/* a flag recording whether initialization has been done */
> +/* or more properly, if the tbuf subsystem is enabled right now */
> +int tb_init_done __read_mostly;

Switch to bool at once? And in any event correct the comment
style please.

> --- a/xen/drivers/cpufreq/utility.c
> +++ b/xen/drivers/cpufreq/utility.c
> @@ -362,11 +362,14 @@ int __cpufreq_driver_target(struct cpufreq_policy 
> *policy,
>  
>      if (cpu_online(policy->cpu) && cpufreq_driver->target)
>      {
> -        unsigned int prev_freq = policy->cur;
> +        uint32_t d[2] = { policy->cur, 0 };

Notwithstanding Andrew's question about the placement of this
hunk the ", 0" seems pointless to me.

> @@ -33,6 +37,7 @@ void init_trace_bufs(void);
>  /* used to retrieve the physical address of the trace buffers */
>  int tb_control(struct xen_sysctl_tbuf_op *tbc);
>  
> +#ifdef CONFIG_TRACING
>  int trace_will_trace_event(u32 event);

Please have a blank line between these, two of them around the
matching #else, and one ahead of the #endif.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel