From: Greg KH <gregkh@linuxfoundation.org>
To: gengcixi@gmail.com
Cc: oberpar@linux.ibm.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, jslaby@suse.com,
orsonzhai@gmail.com, zhang.lyra@gmail.com,
Cixi Geng <cixi.geng1@unisoc.com>
Subject: Re: [RFC][PATCH V2] GCOV: profile by modules
Date: Wed, 20 May 2020 10:51:11 +0200 [thread overview]
Message-ID: <20200520085111.GE2837844@kroah.com> (raw)
In-Reply-To: <20200520083821.9602-1-gengcixi@gmail.com>
On Wed, May 20, 2020 at 04:38:21PM +0800, gengcixi@gmail.com wrote:
> From: Cixi Geng <cixi.geng1@unisoc.com>
>
> ---
> Replace symbol GCOV_PROFILE_MODULES with GCOV_PROFILE_PREREQS
> ---
> The CONFIG_GCOV_PROFILE_ALL will compile kernel by profiling entire
> kernel which will lead to kernel run slower.Use GCOV_PROFILE_PREREQS
> to control part of the kernel modules to open gcov.
>
> Only add SERIAL_GCOV for an example.
>
> Signed-off-by: Cixi Geng <cixi.geng1@unisoc.com>
> ---
> drivers/tty/serial/Kconfig | 6 ++++++
> drivers/tty/serial/Makefile | 1 +
> kernel/gcov/Kconfig | 14 ++++++++++++++
> 3 files changed, 21 insertions(+)
>
> diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
> index adf9e80e7dc9..964df1a2989c 100644
> --- a/drivers/tty/serial/Kconfig
> +++ b/drivers/tty/serial/Kconfig
> @@ -1566,3 +1566,9 @@ endmenu
>
> config SERIAL_MCTRL_GPIO
> tristate
> +
> +config SERIAL_GCOV
> + bool "open gcov for serial"
What do you mean by "open"? And Kconfig entries are usually Upper Case" :)
> + depends on GCOV_PROFILE_PREREQS
> + help
> + Say Y here to enable gcov in serial.
I think we need more text here.
> diff --git a/drivers/tty/serial/Makefile b/drivers/tty/serial/Makefile
> index d056ee6cca33..7be1202286d2 100644
> --- a/drivers/tty/serial/Makefile
> +++ b/drivers/tty/serial/Makefile
> @@ -2,6 +2,7 @@
> #
> # Makefile for the kernel serial device drivers.
> #
> +GCOV_PROFILE := $(CONFIG_SERIAL_GCOV)
>
> obj-$(CONFIG_SERIAL_CORE) += serial_core.o
>
> diff --git a/kernel/gcov/Kconfig b/kernel/gcov/Kconfig
> index 3941a9c48f83..91cc8f3c7c43 100644
> --- a/kernel/gcov/Kconfig
> +++ b/kernel/gcov/Kconfig
> @@ -51,6 +51,20 @@ config GCOV_PROFILE_ALL
> larger and run slower. Also be sure to exclude files from profiling
> which are not linked to the kernel image to prevent linker errors.
>
> +config GCOV_PROFILE_PREREQS
> + bool "Profile Kernel subsytem"
> + depends on !COMPILE_TEST
> + depends on GCOV_KERNEL
> + default n
default is always 'n', no need to list that
> + help
> + This options activates profiling for the specified kernel modules.
> +
> + If unsure, say N.
> +
> + When some modules need Gcov data, enable this config, then configure
> + with gcov on the corresponding modules configs.The directories or files
'. '?
> + of these modules will be added profiling flags after kernel compile.
The lines under "help" need to be indented more, right?
thanks,
greg k-h
next prev parent reply other threads:[~2020-05-20 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 8:38 [RFC][PATCH V2] GCOV: profile by modules gengcixi
2020-05-20 8:49 ` Greg KH
2020-05-20 8:51 ` Greg KH [this message]
2020-05-20 9:04 ` Cixi Geng
2020-05-20 9:20 ` Cixi Geng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200520085111.GE2837844@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cixi.geng1@unisoc.com \
--cc=gengcixi@gmail.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.