From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: Frantisek Hrbata <fhrbata@redhat.com>
Cc: linux-kernel@vger.kernel.org, jstancek@redhat.com,
keescook@chromium.org, rusty@rustcorp.com.au,
linux-arch@vger.kernel.org, arnd@arndb.de, mgahagan@redhat.com,
agospoda@redhat.com
Subject: Re: [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version
Date: Fri, 23 Aug 2013 17:21:12 +0200 [thread overview]
Message-ID: <52177DE8.6090704@linux.vnet.ibm.com> (raw)
In-Reply-To: <52177C87.4090003@linux.vnet.ibm.com>
On 23.08.2013 17:15, Peter Oberparleiter wrote:
> On 23.08.2013 10:39, Frantisek Hrbata wrote:
>> Compile the correct gcov implementation file for a specific gcc version. In
>> the future, if another file is added, the conditions will need to be somehow
>> adjusted to if-elif-else case, but at this point the simple cc-ifversion should
>> be enough.
As promised, I'm also adding the patch that makes the format-specific part
of gcov-kernel a loadable kernel module:
---
kernel: gcov: make format-specific code loadable
Turn the format-specific part of gcov-kernel into a loadable kernel
module. This enables the use of gcov-kernel with kernel modules
that were compiled with a version of GCC that produces a different
gcov format when compared to the version of GCC that was used to
compile the kernel.
Signed-off-by: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
---
kernel/gcov/Kconfig | 19 +++++++++++++++++--
kernel/gcov/Makefile | 7 ++++---
2 files changed, 21 insertions(+), 5 deletions(-)
--- a/kernel/gcov/Kconfig
+++ b/kernel/gcov/Kconfig
@@ -29,8 +29,23 @@ config GCOV_KERNEL
and:
GCOV_PROFILE := n
- Note that the debugfs filesystem has to be mounted to access
- profiling data.
+ Note that GCOV_KERNEL_FS has to specified as well and the debugfs
+ filesystem has to be mounted to access profiling data.
+
+config GCOV_KERNEL_FS
+ tristate "Provide gcov data files in debugfs"
+ depends on GCOV_KERNEL
+ default y
+ ---help---
+ Make profiling data available in debugfs at /sys/kernel/debug/gcov.
+
+ Say M if you want to enable collecting coverage data for kernel modules
+ which are compiled using a gcc version different from the one that
+ was used to compile the kernel. In that case, re-compile the gcov
+ kernel module with corresponding format support and load that module
+ instead.
+
+ If unsure, say Y.
config GCOV_PROFILE_ALL
bool "Profile entire Kernel"
--- a/kernel/gcov/Makefile
+++ b/kernel/gcov/Makefile
@@ -13,10 +13,11 @@ else
cc-ver := $(call cc-version)
endif
-obj-$(CONFIG_GCOV_KERNEL) := base.o fs.o
+obj-$(CONFIG_GCOV_KERNEL) += base.o
+obj-$(CONFIG_GCOV_KERNEL_FS) += gcov.o
ifeq ($(call if-lt, $(cc-ver), 0407),1)
- obj-$(CONFIG_GCOV_KERNEL) += gcc_3_4.o
+ gcov-objs += fs.o gcc_3_4.o
else
- obj-$(CONFIG_GCOV_KERNEL) += gcc_4_7.o
+ gcov-objs += fs.o gcc_4_7.o
endif
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
next prev parent reply other threads:[~2013-08-23 15:21 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 8:39 [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7 Frantisek Hrbata
2013-08-23 8:39 ` [RFC PATCH 1/4] gcov: move gcov structs definitions to a gcc version specific file Frantisek Hrbata
2013-08-23 8:39 ` Frantisek Hrbata
2013-08-23 15:09 ` Peter Oberparleiter
2013-08-23 15:09 ` Peter Oberparleiter
2013-08-23 16:50 ` Frantisek Hrbata
2013-08-23 16:50 ` Frantisek Hrbata
2013-08-26 12:17 ` Peter Oberparleiter
2013-08-23 8:39 ` [RFC PATCH 2/4] gcov: add support for gcc 4.7 gcov format Frantisek Hrbata
2013-08-23 8:39 ` Frantisek Hrbata
2013-08-23 15:12 ` Peter Oberparleiter
2013-08-23 21:00 ` Frantisek Hrbata
2013-08-26 12:45 ` Peter Oberparleiter
2013-08-27 13:41 ` Frantisek Hrbata
2013-08-27 13:41 ` Frantisek Hrbata
2013-08-23 8:39 ` [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version Frantisek Hrbata
2013-08-23 8:39 ` Frantisek Hrbata
2013-08-23 15:15 ` Peter Oberparleiter
2013-08-23 15:21 ` Peter Oberparleiter [this message]
2013-08-24 19:44 ` Frantisek Hrbata
2013-08-25 18:29 ` Arnd Bergmann
2013-08-26 14:14 ` Peter Oberparleiter
2013-08-27 13:34 ` Frantisek Hrbata
2013-08-28 13:46 ` Peter Oberparleiter
2013-08-28 13:54 ` Frantisek Hrbata
2013-08-28 13:54 ` Frantisek Hrbata
2013-08-24 19:12 ` Frantisek Hrbata
2013-08-24 19:12 ` Frantisek Hrbata
2013-08-26 12:56 ` Peter Oberparleiter
2013-08-26 12:56 ` Peter Oberparleiter
2013-08-27 13:23 ` Frantisek Hrbata
2013-08-27 13:23 ` Frantisek Hrbata
2013-08-23 8:39 ` [RFC PATCH 4/4] kernel: add support for init_array constructors Frantisek Hrbata
2013-08-23 8:39 ` Frantisek Hrbata
2013-08-23 15:13 ` Peter Oberparleiter
2013-08-23 16:55 ` Frantisek Hrbata
2013-08-23 15:08 ` [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7 Peter Oberparleiter
2013-08-23 16:15 ` Frantisek Hrbata
2013-08-23 16:15 ` Frantisek Hrbata
2013-08-26 11:39 ` LF.Tan
2013-08-26 11:39 ` LF.Tan
2013-08-26 14:19 ` Peter Oberparleiter
2013-08-27 2:38 ` LF.Tan
2013-08-26 11:57 ` Peter Oberparleiter
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=52177DE8.6090704@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=agospoda@redhat.com \
--cc=arnd@arndb.de \
--cc=fhrbata@redhat.com \
--cc=jstancek@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgahagan@redhat.com \
--cc=rusty@rustcorp.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).