From: Dave Hansen <dave@sr71.net>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
peterz@infradead.org, mingo@redhat.com, ak@linux.intel.com,
akpm@linux-foundation.org, cl@linux.com, penberg@kernel.org,
linux-mm@kvack.org, kirill@shutemov.name, lauraa@codeaurora.org
Subject: Re: [PATCH] [v3] warn on performance-impacting configs aka. TAINT_PERFORMANCE
Date: Fri, 22 Aug 2014 09:45:22 -0700 [thread overview]
Message-ID: <53F773A2.7040904@sr71.net> (raw)
In-Reply-To: <1408725157.4347.14.camel@schen9-DESK>
On 08/22/2014 09:32 AM, Tim Chen wrote:
>> > +#ifdef CONFIG_DEBUG_OBJECTS_FREE
>> > + "DEBUG_OBJECTS_FREE",
>> > +#endif
>> > +#ifdef CONFIG_DEBUG_KMEMLEAK
>> > + "DEBUG_KMEMLEAK",
>> > +#endif
>> > +#ifdef CONFIG_DEBUG_PAGEALLOC
>> > + "DEBUG_PAGEALLOC",
> I think coverage profiling also impact performance.
> So I sould also put CONFIG_GCOV_KERNEL in the list.
Would CONFIG_GCOV_PROFILE_ALL be the better one to check? With plain
GCOV_KERNEL, I don't think we will, by default, put the coverage
information in any files and slow them down.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@sr71.net>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
peterz@infradead.org, mingo@redhat.com, ak@linux.intel.com,
akpm@linux-foundation.org, cl@linux.com, penberg@kernel.org,
linux-mm@kvack.org, kirill@shutemov.name, lauraa@codeaurora.org
Subject: Re: [PATCH] [v3] warn on performance-impacting configs aka. TAINT_PERFORMANCE
Date: Fri, 22 Aug 2014 09:45:22 -0700 [thread overview]
Message-ID: <53F773A2.7040904@sr71.net> (raw)
In-Reply-To: <1408725157.4347.14.camel@schen9-DESK>
On 08/22/2014 09:32 AM, Tim Chen wrote:
>> > +#ifdef CONFIG_DEBUG_OBJECTS_FREE
>> > + "DEBUG_OBJECTS_FREE",
>> > +#endif
>> > +#ifdef CONFIG_DEBUG_KMEMLEAK
>> > + "DEBUG_KMEMLEAK",
>> > +#endif
>> > +#ifdef CONFIG_DEBUG_PAGEALLOC
>> > + "DEBUG_PAGEALLOC",
> I think coverage profiling also impact performance.
> So I sould also put CONFIG_GCOV_KERNEL in the list.
Would CONFIG_GCOV_PROFILE_ALL be the better one to check? With plain
GCOV_KERNEL, I don't think we will, by default, put the coverage
information in any files and slow them down.
next prev parent reply other threads:[~2014-08-22 16:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 20:24 [PATCH] [v3] warn on performance-impacting configs aka. TAINT_PERFORMANCE Dave Hansen
2014-08-21 20:24 ` Dave Hansen
2014-08-21 20:57 ` Dave Jones
2014-08-21 20:57 ` Dave Jones
2014-08-21 21:03 ` Dave Hansen
2014-08-21 21:03 ` Dave Hansen
2014-08-22 7:20 ` Ingo Molnar
2014-08-22 7:20 ` Ingo Molnar
2014-08-22 15:02 ` Dave Hansen
2014-08-22 15:02 ` Dave Hansen
2014-08-24 14:49 ` Ingo Molnar
2014-08-24 14:49 ` Ingo Molnar
2014-08-24 20:40 ` Dave Hansen
2014-08-24 20:40 ` Dave Hansen
2014-08-24 22:13 ` Linus Torvalds
2014-08-22 16:32 ` Tim Chen
2014-08-22 16:45 ` Dave Hansen [this message]
2014-08-22 16:45 ` Dave Hansen
2014-08-22 18:12 ` Tim Chen
2014-08-22 18:12 ` Tim Chen
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=53F773A2.7040904@sr71.net \
--to=dave@sr71.net \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dave.hansen@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=tim.c.chen@linux.intel.com \
/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.