> On Jun 4, 2019, at 1:44 AM, Baodong Chen <chenbaod...@mxnavi.com> wrote: > > Xen internal running status(trace event) will be saved to > trace memory when enabled. trace event data and config params can be > read/changed by system control hypercall at run time. > > Can be disabled for smaller code footprint. > > Signed-off-by: Baodong Chen <chenbaod...@mxnavi.com> > --- > xen/common/Kconfig | 12 ++++++++++++ > xen/common/Makefile | 2 +- > xen/include/xen/trace.h | 17 +++++++++++++++++ > 3 files changed, 30 insertions(+), 1 deletion(-) > > diff --git a/xen/common/Kconfig b/xen/common/Kconfig > index c838506..3459f56 100644 > --- a/xen/common/Kconfig > +++ b/xen/common/Kconfig > @@ -368,4 +368,16 @@ config DOM0_MEM > > Leave empty if you are not sure what to specify. > > +config TRACEBUFFER > + bool "Enable trace event logs" if EXPERT = "y" > + ---help--- > + Xen internal running status(trace event) will be saved to trace memory > + when enabled. trace event data and config params can be read/changed > + by system control hypercall at run time. > + > + This is used to record xen internal running status. > + with a litte performance overhead. > + Can be set to 'N' if you dont want this function. > + When not configured, 'XEN_STSCTL_tbuf_op' command will result > 'ENOSYS’.
I think this would look better something like this: “Enable tracing infrastructure” “Enable in tracing infrastructure and pre-defined tracepoints within Xen. This will allow live information about Xen’s execution and performance to be collected at run time for debugging or performance analysis. Memory and execution overhead when not active is minimal." Also, I’m not 100% familiar with the kconfig syntax — I think we want tracing enabled by default unless actively disabled; is that what will happen here? Or will it only be enabled if EXPERT == ‘y’? -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
