[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130918142259.8c504e7cfbc8318a0550a891@linux-foundation.org>
Date: Wed, 18 Sep 2013 14:22:59 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Frantisek Hrbata <fhrbata@...hat.com>
Cc: linux-kernel@...r.kernel.org, jstancek@...hat.com,
keescook@...omium.org, peter.oberparleiter@...ibm.com,
rusty@...tcorp.com.au, linux-arch@...r.kernel.org, arnd@...db.de,
mgahagan@...hat.com, agospoda@...hat.com
Subject: Re: [PATCH v2 2/4] gcov: add support for gcc 4.7 gcov format
On Wed, 4 Sep 2013 16:42:54 +0200 Frantisek Hrbata <fhrbata@...hat.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;
_
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists