All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cixi Geng <gengcixi@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jslaby@suse.com, oberpar@linux.ibm.com,
	linux-serial@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Orson Zhai <orsonzhai@gmail.com>,
	zhang.lyra@gmail.com, Cixi Geng <cixi.geng1@unisoc.com>
Subject: Re: [RFC][PATCH V3] GCOV: profile by modules
Date: Fri, 22 May 2020 18:46:34 +0800	[thread overview]
Message-ID: <CAF12kFsDHFNdY5ssiMpq0f3eH4ZOjXqStB=HRhuh0Nr08SqFPA@mail.gmail.com> (raw)
In-Reply-To: <20200522083715.GD1078778@kroah.com>

Hi Greg:
DId you mean that the GCOV_PROFILE_PREREQS should add depends
on !GCOV_PROFILE_ALL ,then when GCOV_PROFILE_ALL is enabled,
the config GCOV_PROFILE_PREREQS will no longer works.

Greg KH <gregkh@linuxfoundation.org> 于2020年5月22日周五 下午4:37写道:
>
> On Fri, May 22, 2020 at 03:19:17PM +0800, gengcixi@gmail.com wrote:
> > From: Cixi Geng <cixi.geng1@unisoc.com>
> >
> > 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  |  7 +++++++
> >  drivers/tty/serial/Makefile |  1 +
> >  kernel/gcov/Kconfig         | 13 +++++++++++++
> >  3 files changed, 21 insertions(+)
> >
> > diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
> > index adf9e80e7dc9..6df002370f18 100644
> > --- a/drivers/tty/serial/Kconfig
> > +++ b/drivers/tty/serial/Kconfig
> > @@ -1566,3 +1566,10 @@ endmenu
> >
> >  config SERIAL_MCTRL_GPIO
> >       tristate
> > +
> > +config SERIAL_GCOV
> > +     bool "Enable profile gcov for serial directory"
> > +     depends on GCOV_PROFILE_PREREQS
> > +     help
> > +       The SERIAL_GCOV will add Gcov profiling flags when kernel compiles.
> > +       Say 'Y' here if you want the gcov data for the serial directory,
> > diff --git a/drivers/tty/serial/Makefile b/drivers/tty/serial/Makefile
> > index d056ee6cca33..17272733db95 100644
> > --- a/drivers/tty/serial/Makefile
> > +++ b/drivers/tty/serial/Makefile
> > @@ -3,6 +3,7 @@
> >  # Makefile for the kernel serial device drivers.
> >  #
> >
> > +GCOV_PROFILE := $(CONFIG_SERIAL_GCOV)
> >  obj-$(CONFIG_SERIAL_CORE) += serial_core.o
> >
> >  obj-$(CONFIG_SERIAL_EARLYCON) += earlycon.o
> > diff --git a/kernel/gcov/Kconfig b/kernel/gcov/Kconfig
> > index 3941a9c48f83..4d75fa158726 100644
> > --- a/kernel/gcov/Kconfig
> > +++ b/kernel/gcov/Kconfig
> > @@ -51,6 +51,19 @@ 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
> > +     help
> > +       This options activates profiling for the specified kernel modules.
> > +
> > +       When some modules need Gcov data, enable this config, then configure
> > +       with gcov on the corresponding modules,The directories or files of
> > +       these modules will be added profiling flags after kernel compile.
> > +
> > +       If unsure, say N.
> > +
> >  choice
> >       prompt "Specify GCOV format"
> >       depends on GCOV_KERNEL
>
>
> I understand the goal here, but don't you need to have the main GCov
> option depend on your new Kconfig option here?  You have it switched
> around here, so what keeps all code from being built with gcov support
> at the moment?
>
> thanks,
>
> greg k-h

      reply	other threads:[~2020-05-22 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  7:19 [RFC][PATCH V3] GCOV: profile by modules gengcixi
2020-05-22  8:37 ` Greg KH
2020-05-22 10:46   ` Cixi Geng [this message]

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='CAF12kFsDHFNdY5ssiMpq0f3eH4ZOjXqStB=HRhuh0Nr08SqFPA@mail.gmail.com' \
    --to=gengcixi@gmail.com \
    --cc=cixi.geng1@unisoc.com \
    --cc=gregkh@linuxfoundation.org \
    --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.