All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	Christophe Guillon <christophe.guillon@st.com>,
	rusty@rustcorp.com.au, linux-arch@vger.kernel.org, arnd@arndb.de,
	mgahagan@redhat.com, agospoda@redhat.com
Subject: Re: [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7
Date: Fri, 23 Aug 2013 17:08:07 +0200	[thread overview]
Message-ID: <52177AD7.1030709@linux.vnet.ibm.com> (raw)
In-Reply-To: <1377247176-13537-1-git-send-email-fhrbata@redhat.com>

On 23.08.2013 10:39, Frantisek Hrbata wrote:
> This is an attempt to bring support for modified gcov format in gcc 4.7 to
> the kernel. It tries to leverage the existing layout/abstraction, which was
> designed keeping in mind that the gcov format could change, but some changes had
> to be make. Mostly because the current model does not take into account that
> even the core gcov structures, like gcov_info, could change. One part that could
> be problematic is the addition of the .init_array section for constructors.

It appears that gcc 4.7 support for gcov-kernel is quite important to a
number of people, at least that is what I derive from the fact that I
now know of 3 people who've been working on this support separately from
each other: you, myself (I've been close to posting my own version to
LKML) and Christophe Guillon.

It's apparent now that I made a mistake delaying the discussion of the
effort for too long, but I think your posting the patches opens up a
good opportunity to combine the best of all previous efforts.

Most of your code looks very familiar. There's one feature missing though
that Christophe brought up as a requirement: the ability for gcov-kernel
to cope with kernel modules being compiled with GCC versions implementing
a different gcov format (apparently this can happen in some embedded
setups).

Christophe proposed run-time version checking and a file-ops type function
table which is chosen based on info->version. I found this approach
somewhat intrusive and this would also not have covered the case where a
new GCC versions was used to compile kernel modules for which the base
kernel has no support. I tried to solve this requirement by combining
two changes:

1) make the gcov-format generated by gcov-kernel compile-time configurable
2) separate the gcov-format specific code into a loadable kernel module

This way, the gcov-format specific part of gcov-kernel could be replaced
when working with a different version GCC. I'll post the corresponding
patches as reply in another mail.

Back to your patches: I tested them and they work fine on s390x when
compiled with GCC 4.3.4 and 4.7.2. I'll provide some more specific
comments as replies to your patch-mails.


Regards,
  Peter Oberparleiter

-- 
Peter Oberparleiter
Linux on System z Development - IBM Germany

  parent reply	other threads:[~2013-08-23 15:08 UTC|newest]

Thread overview: 31+ 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 15:09   ` Peter Oberparleiter
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 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-23  8:39 ` [RFC PATCH 3/4] gcov: compile specific gcov implementation based on gcc version Frantisek Hrbata
2013-08-23 15:15   ` Peter Oberparleiter
2013-08-23 15:21     ` Peter Oberparleiter
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-24 19:12     ` Frantisek Hrbata
2013-08-26 12:56       ` Peter Oberparleiter
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 15:13   ` Peter Oberparleiter
2013-08-23 16:55     ` Frantisek Hrbata
2013-08-23 15:08 ` Peter Oberparleiter [this message]
2013-08-23 16:15   ` [RFC PATCH 0/4] add support for gcov format introduced in gcc 4.7 Frantisek Hrbata
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=52177AD7.1030709@linux.vnet.ibm.com \
    --to=oberpar@linux.vnet.ibm.com \
    --cc=agospoda@redhat.com \
    --cc=arnd@arndb.de \
    --cc=christophe.guillon@st.com \
    --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 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.