From: Vince Weaver <vince@deater.net>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, eranian@google.com,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks
Date: Fri, 26 Aug 2016 16:49:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1608261648370.21116@pianoman.cluster.toy> (raw)
In-Reply-To: <87fupul0bp.fsf@ashishki-desk.ger.corp.intel.com>
On Wed, 24 Aug 2016, Alexander Shishkin wrote:
> Alexander Shishkin <alexander.shishkin@linux.intel.com> writes:
>
> > Alexander Shishkin <alexander.shishkin@linux.intel.com> writes:
> >
> >> Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> >
> > Ok, this one is broken, please disregard.
>
> Vince, can you try the following (with the other two in this series)?
>
Sorry for the delay. Not sure if testing was still needed (or if it was
superceded by Will Deacon's patch) but I ran the fuzzer for a few hours
with this patch and the other two applied and didn't see any of the NMI
errors that I saw with the original patch.
Vince
next prev parent reply other threads:[~2016-08-26 20:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 8:54 [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Alexander Shishkin
2016-08-23 8:54 ` [PATCH 1/3] perf/x86/intel/bts: Fix confused ordering of PMU callbacks Alexander Shishkin
2016-08-24 12:28 ` Alexander Shishkin
2016-08-24 14:15 ` Alexander Shishkin
2016-08-26 20:49 ` Vince Weaver [this message]
2016-08-27 6:35 ` Alexander Shishkin
2016-08-29 14:14 ` Peter Zijlstra
2016-08-29 14:43 ` Alexander Shishkin
2016-08-23 8:54 ` [PATCH 2/3] perf/x86/intel/bts: Kill a silly warning Alexander Shishkin
2016-08-23 8:54 ` [PATCH 3/3] perf: Fix a race between mmap_close and set_output of AUX events Alexander Shishkin
2016-08-23 16:24 ` [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Vince Weaver
2016-08-23 17:10 ` Alexander Shishkin
2016-08-23 20:55 ` Vince Weaver
2016-08-24 3:44 ` 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=alpine.DEB.2.11.1608261648370.21116@pianoman.cluster.toy \
--to=vince@deater.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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;
as well as URLs for NNTP newsgroup(s).