From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, vince@deater.net,
eranian@google.com, Arnaldo Carvalho de Melo <acme@infradead.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH 2/4] perf: Keep AUX flags in the output handle
Date: Tue, 21 Feb 2017 12:54:26 +0200 [thread overview]
Message-ID: <87a89fizkt.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20170221104242.GB300@arm.com>
Will Deacon <will.deacon@arm.com> writes:
> Hi Alexander,
Hi Will,
>> + handle->aux_flags &= ~PERF_AUX_FLAG_OVERWRITE;
>> +
>
> ... I don't think you need this addition anymore. It's harmless, though.
Right, assuming the PMU driver isn't doing anything fishy to
handle->aux_flags directly.
Regards,
--
Alex
next prev parent reply other threads:[~2017-02-21 10:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 13:33 [PATCH 0/4] perf, pt, coresight: AUX flags and VMX update Alexander Shishkin
2017-02-20 13:33 ` [PATCH 1/4] perf: Export AUX buffer helpers to modules Alexander Shishkin
2017-02-20 13:33 ` [PATCH 2/4] perf: Keep AUX flags in the output handle Alexander Shishkin
2017-02-20 17:01 ` kbuild test robot
2017-02-20 17:17 ` Alexander Shishkin
2017-02-20 20:42 ` Mathieu Poirier
2017-02-21 10:42 ` Will Deacon
2017-02-21 10:54 ` Alexander Shishkin [this message]
2017-03-16 11:22 ` [tip:perf/core] perf/core: " tip-bot for Will Deacon
2017-02-20 13:33 ` [PATCH 3/4] perf: Add a flag for partial AUX records Alexander Shishkin
2017-03-16 11:23 ` [tip:perf/core] perf/core: " tip-bot for Alexander Shishkin
2017-03-16 14:24 ` Vince Weaver
2017-02-20 13:33 ` [PATCH 4/4] perf/x86/intel/pt: Handle VMX better Alexander Shishkin
2017-03-16 11:24 ` [tip:perf/core] " tip-bot for Alexander Shishkin
2017-02-20 15:18 ` [PATCH 0/4] perf, pt, coresight: AUX flags and VMX update Alexander Shishkin
2017-02-20 15:39 ` Adrian Hunter
2017-02-20 16:09 ` Arnaldo Carvalho de Melo
2017-02-20 16:31 ` Alexander Shishkin
2017-03-16 16:41 ` Alexander Shishkin
2017-03-21 6:50 ` [tip:perf/core] tools lib api fs: Introduce sysfs__read_bool tip-bot for Alexander Shishkin
2017-03-21 6:51 ` [tip:perf/core] tools include: Sync {,tools/}include/uapi/linux/perf_event.h tip-bot for Alexander Shishkin
2017-03-21 6:51 ` [tip:perf/core] perf tools: Handle partial AUX records and print a warning tip-bot for 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=87a89fizkt.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=vince@deater.net \
--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
Powered by JetHome