From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH 2/4] tools, perf_event.h: Synchronize
Date: Thu, 9 Nov 2017 19:05:46 +0200 [thread overview]
Message-ID: <20171109170548.32133-3-alexander.shishkin@linux.intel.com> (raw)
In-Reply-To: <20171109170548.32133-1-alexander.shishkin@linux.intel.com>
I've just added attr::suppress_aux bit to the kernel header, adding
it to the tools' header too.
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
---
tools/include/uapi/linux/perf_event.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/include/uapi/linux/perf_event.h b/tools/include/uapi/linux/perf_event.h
index 362493a2f950..fa3821d9dc52 100644
--- a/tools/include/uapi/linux/perf_event.h
+++ b/tools/include/uapi/linux/perf_event.h
@@ -370,7 +370,8 @@ struct perf_event_attr {
context_switch : 1, /* context switch data */
write_backward : 1, /* Write ring buffer from end to beginning */
namespaces : 1, /* include namespaces data */
- __reserved_1 : 35;
+ suppress_aux : 1, /* don't generate PERF_RECORD_AUX */
+ __reserved_1 : 34;
union {
__u32 wakeup_events; /* wakeup every n events */
--
2.14.2
next prev parent reply other threads:[~2017-11-09 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 17:05 [PATCH 0/4] perf: Allow suppressing useless AUX records Alexander Shishkin
2017-11-09 17:05 ` [PATCH 1/4] perf: Allow suppressing " Alexander Shishkin
2017-11-10 8:22 ` Adrian Hunter
2017-11-09 17:05 ` Alexander Shishkin [this message]
2017-11-09 17:05 ` [PATCH 3/4] perf tools: Add 'suppress_aux' attribute bit definition and fallback Alexander Shishkin
2017-11-09 17:05 ` [PATCH 4/4] perf intel-pt, intel-bts: Suppress useless AUX records by default Alexander Shishkin
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=20171109170548.32133-3-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®