From: Dave Hansen <dave@sr71.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Raghavendra KT <raghavendra.kt.linux@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org,
Raghavendra KT <raghavendra.kt@linux.vnet.ibm.com>
Subject: Re: [RESEND][PATCH] mm: vmstats: tlb flush counters
Date: Mon, 22 Jul 2013 09:59:40 -0700 [thread overview]
Message-ID: <51ED64FC.8090104@sr71.net> (raw)
In-Reply-To: <20130722100605.GA1148@gmail.com>
On 07/22/2013 03:06 AM, Ingo Molnar wrote:
> Btw., would be nice to also integrate these VM counters into perf as well,
> as an instrumentation variant/option.
>
> It could be done in an almost zero overhead fashion using jump-labels I
> think.
>
> [ Just in case someone is bored to death and is looking for an interesting
> side project ;-) ]
I'd actually been thinking about making them in to tracepoints, but the
tracepoint macros seem to create #include messes if you try to use them
in very common headers.
Agree it would be an interesting side project, though. :)
--
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: Ingo Molnar <mingo@kernel.org>
Cc: Raghavendra KT <raghavendra.kt.linux@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org,
Raghavendra KT <raghavendra.kt@linux.vnet.ibm.com>
Subject: Re: [RESEND][PATCH] mm: vmstats: tlb flush counters
Date: Mon, 22 Jul 2013 09:59:40 -0700 [thread overview]
Message-ID: <51ED64FC.8090104@sr71.net> (raw)
In-Reply-To: <20130722100605.GA1148@gmail.com>
On 07/22/2013 03:06 AM, Ingo Molnar wrote:
> Btw., would be nice to also integrate these VM counters into perf as well,
> as an instrumentation variant/option.
>
> It could be done in an almost zero overhead fashion using jump-labels I
> think.
>
> [ Just in case someone is bored to death and is looking for an interesting
> side project ;-) ]
I'd actually been thinking about making them in to tracepoints, but the
tracepoint macros seem to create #include messes if you try to use them
in very common headers.
Agree it would be an interesting side project, though. :)
next prev parent reply other threads:[~2013-07-22 16:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 23:44 [RESEND][PATCH] mm: vmstats: tlb flush counters Dave Hansen
2013-07-16 23:44 ` Dave Hansen
2013-07-17 7:21 ` Ingo Molnar
2013-07-17 7:21 ` Ingo Molnar
2013-07-18 20:51 ` Andrew Morton
2013-07-18 20:51 ` Andrew Morton
2013-07-19 8:28 ` Ingo Molnar
2013-07-19 8:28 ` Ingo Molnar
2013-07-19 15:51 ` Dave Hansen
2013-07-19 15:51 ` Dave Hansen
2013-07-19 11:38 ` Raghavendra KT
2013-07-19 11:38 ` Raghavendra KT
2013-07-19 15:20 ` Dave Hansen
2013-07-19 15:20 ` Dave Hansen
2013-07-20 13:09 ` Raghavendra K T
2013-07-20 13:09 ` Raghavendra K T
2013-07-22 10:06 ` Ingo Molnar
2013-07-22 10:06 ` Ingo Molnar
2013-07-22 16:59 ` Dave Hansen [this message]
2013-07-22 16:59 ` Dave Hansen
2013-07-23 8:17 ` Ingo Molnar
2013-07-23 8:17 ` Ingo Molnar
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=51ED64FC.8090104@sr71.net \
--to=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=raghavendra.kt.linux@gmail.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=x86@kernel.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.