From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Borislav Petkov <bp@alien8.de>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, vince@deater.net,
eranian@google.com, Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [PATCH 2/2] perf: Disable the event on a truncated AUX record
Date: Wed, 11 May 2016 11:49:31 +0200 [thread overview]
Message-ID: <20160511094931.GD3190@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <874ma5ue2g.fsf@ashishki-desk.ger.corp.intel.com>
On Wed, May 11, 2016 at 12:41:27PM +0300, Alexander Shishkin wrote:
> Peter Zijlstra <peterz@infradead.org> writes:
> >
> > Does the userspace tool know how to deal with this and re-enable it?
>
> Yes, it knows to ioctl(EVENT_ENABLE). Also, we're already doing the
> disabling for the no-room-in-buffer condition in
> perf_aux_output_begin().
Awesome; gots them queued.
next prev parent reply other threads:[~2016-05-11 9:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 13:18 [PATCH 0/2] perf, pt: Fix massive data losses Alexander Shishkin
2016-05-10 13:18 ` [PATCH 1/2] perf/x86/intel/pt: Generate PMI in the STOP region as well Alexander Shishkin
2016-05-12 10:34 ` [tip:perf/core] " tip-bot for Alexander Shishkin
2016-05-12 12:28 ` Alexander Shishkin
2016-05-12 12:47 ` Ingo Molnar
2016-05-12 13:03 ` Alexander Shishkin
2016-05-12 12:48 ` [tip:perf/urgent] " tip-bot for Alexander Shishkin
2016-05-17 7:31 ` Alexander Shishkin
2016-05-17 8:40 ` Ingo Molnar
2016-05-21 5:25 ` Greg KH
2016-05-10 13:18 ` [PATCH 2/2] perf: Disable the event on a truncated AUX record Alexander Shishkin
2016-05-11 9:13 ` Peter Zijlstra
2016-05-11 9:41 ` Alexander Shishkin
2016-05-11 9:49 ` Peter Zijlstra [this message]
2016-05-11 10:05 ` Alexander Shishkin
2016-05-12 10:35 ` [tip:perf/core] perf/core: " tip-bot for Alexander Shishkin
2016-05-12 12:49 ` [tip:perf/urgent] " 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=20160511094931.GD3190@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vince@deater.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome