From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: gcov: enable GCOV_PROFILE_ALL for x86_64
Date: Mon, 22 Jun 2009 13:28:21 +0200 [thread overview]
Message-ID: <4A3F6AD5.1030703@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090620101424.GA21928@elte.hu>
Ingo Molnar wrote:
> * Linux Kernel Mailing List <linux-kernel@vger.kernel.org> wrote:
>
>> Gitweb: http://git.kernel.org/linus/7bf99fb673f18408be1ebc958321ef4c3f6da9e2
>> Commit: 7bf99fb673f18408be1ebc958321ef4c3f6da9e2
>> Parent: 2521f2c228ad750701ba4702484e31d876dbc386
>> Author: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
>> AuthorDate: Wed Jun 17 16:28:09 2009 -0700
>> Committer: Linus Torvalds <torvalds@linux-foundation.org>
>> CommitDate: Thu Jun 18 13:03:58 2009 -0700
>>
>> gcov: enable GCOV_PROFILE_ALL for x86_64
>>
>> Enable gcov profiling of the entire kernel on x86_64. Required changes
>> include disabling profiling for:
>>
>> * arch/kernel/acpi/realmode and arch/kernel/boot/compressed:
>> not linked to main kernel
>> * arch/vdso, arch/kernel/vsyscall_64 and arch/kernel/hpet:
>> profiling causes segfaults during boot (incompatible context)
>
> This feature crashes on bootup:
I can recreate the crash using your config. It looks like another object file in arch/x86 is incompatible with gcov profiling (most likely due to special stack usage) and needs to be excluded from profiling. I'm working on identifying this file but it will take a bit more time.
next prev parent reply other threads:[~2009-06-22 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200906182200.n5IM0jFq007278@hera.kernel.org>
2009-06-20 10:14 ` gcov: enable GCOV_PROFILE_ALL for x86_64 Ingo Molnar
2009-06-22 11:28 ` Peter Oberparleiter [this message]
2009-06-22 10:56 ` Ingo Molnar
2009-06-23 7:42 ` 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=4A3F6AD5.1030703@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
/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.