linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Frantisek Hrbata <fhrbata@redhat.com>
Cc: linux-kernel@vger.kernel.org, jstancek@redhat.com,
	keescook@chromium.org, peter.oberparleiter@de.ibm.com,
	rusty@rustcorp.com.au, linux-arch@vger.kernel.org, arnd@arndb.de,
	mgahagan@redhat.com, agospoda@redhat.com
Subject: Re: [PATCH v2 2/4] gcov: add support for gcc 4.7 gcov format
Date: Wed, 18 Sep 2013 14:22:59 -0700	[thread overview]
Message-ID: <20130918142259.8c504e7cfbc8318a0550a891@linux-foundation.org> (raw)
In-Reply-To: <1378305776-3644-3-git-send-email-fhrbata@redhat.com>

On Wed,  4 Sep 2013 16:42:54 +0200 Frantisek Hrbata <fhrbata@redhat.com> wrote:

> The gcov in-memory format changed in gcc 4.7. The biggest change, which
> requires this special implementation, is that gcov_info no longer contains
> array of counters for each counter type for all functions and gcov_fn_info is
> not used for mapping of function's counters to these arrays(offset). Now each
> gcov_fn_info contans it's counters, which makes things a little bit easier.
> 
> This is heavily based on the previous gcc_3_4.c implementation and patches
> provided by Peter Oberparleiter. Specially the buffer gcda implementation for
> iterator.

A couple of little tweaks:

--- a/kernel/gcov/gcc_4_7.c~gcov-add-support-for-gcc-47-gcov-format-fix
+++ a/kernel/gcov/gcc_4_7.c
@@ -254,11 +254,10 @@ struct gcov_info *gcov_info_dup(struct g
 	size_t fi_size; /* function info size */
 	size_t cv_size; /* counter values size */
 
-	dup = kmalloc(sizeof(struct gcov_info), GFP_KERNEL);
+	dup = kmemdup(info, sizeof(*dup), GFP_KERNEL);
 	if (!dup)
 		return NULL;
 
-	*dup = *info;
 	dup->next = NULL;
 	dup->filename = NULL;
 	dup->functions = NULL;
@@ -267,8 +266,8 @@ struct gcov_info *gcov_info_dup(struct g
 	if (!dup->filename)
 		goto err_free;
 
-	dup->functions = kzalloc(sizeof(struct gcov_fn_info *) *
-			info->n_functions, GFP_KERNEL);
+	dup->functions = kcalloc(sizeof(struct gcov_fn_info *),
+				 info->n_functions, GFP_KERNEL);
 	if (!dup->functions)
 		goto err_free;
 
_

  parent reply	other threads:[~2013-09-18 21:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 14:42 [PATCH v2 0/4] add support for gcov format introduced in gcc 4.7 Frantisek Hrbata
2013-09-04 14:42 ` [PATCH v2 1/4] gcov: move gcov structs definitions to a gcc version specific file Frantisek Hrbata
2013-09-04 14:42   ` Frantisek Hrbata
2013-09-04 14:42 ` [PATCH v2 2/4] gcov: add support for gcc 4.7 gcov format Frantisek Hrbata
2013-09-04 14:42   ` Frantisek Hrbata
2013-09-18 21:22   ` Andrew Morton [this message]
2013-09-18 21:27     ` Joe Perches
2013-09-18 21:27       ` Joe Perches
2013-09-18 21:31       ` Andrew Morton
2013-09-19 10:12         ` Frantisek Hrbata
2013-09-19  9:04   ` Peter Oberparleiter
2013-09-19 10:21     ` Frantisek Hrbata
2013-09-19 10:31       ` Peter Oberparleiter
2013-09-04 14:42 ` [PATCH v2 3/4] gcov: compile specific gcov implementation based on gcc version Frantisek Hrbata
2013-09-04 14:42   ` Frantisek Hrbata
2013-09-04 14:42 ` [PATCH v2 4/4] kernel: add support for init_array constructors Frantisek Hrbata
2013-09-04 14:42   ` Frantisek Hrbata
2013-09-06  2:13   ` Rusty Russell
2013-09-06 17:51     ` Frantisek Hrbata
2013-09-06 18:07       ` Kyle McMartin
2013-09-09  1:14         ` Rusty Russell
2013-09-09  1:14           ` Rusty Russell
2013-09-09 16:28           ` Frantisek Hrbata
2013-09-10  0:15             ` Kyle McMartin
2013-09-10  5:35             ` Rusty Russell
2013-09-10 13:28               ` Frantisek Hrbata
2013-09-10 13:28                 ` Frantisek Hrbata
2013-09-11  1:52                 ` Rusty Russell
2013-09-26 23:11 ` [PATCH v2 0/4] add support for gcov format introduced in gcc 4.7 Christophe Guillon

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=20130918142259.8c504e7cfbc8318a0550a891@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --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=peter.oberparleiter@de.ibm.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).