From: Andi Kleen <ak@linux.intel.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
lkml <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
eranian@google.com, vincent.weaver@maine.edu,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3)
Date: Thu, 31 Jan 2019 12:39:27 -0800 [thread overview]
Message-ID: <20190131203927.GY6118@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAM_iQpVtyCR=BTBkpDtbEFJ8REczpvYRTGPQnBsV=8rznXn6fg@mail.gmail.com>
> Yeah, a loop stuck looks really scary inside an NMI handler.
> Should I just go ahead to send a patch to remove this warning?
> Or probably turn it into a pr_info()?
Not at this point. Would need to fix the PMU reset first to be
more selective.
-Andi
next prev parent reply other threads:[~2019-01-31 20:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 6:46 System crash with perf_fuzzer (kernel: 5.0.0-rc3) Ravi Bangoria
2019-01-25 15:11 ` Vince Weaver
2019-01-25 16:00 ` Andi Kleen
2019-01-31 7:58 ` Ravi Bangoria
2019-01-31 13:00 ` Andi Kleen
2019-01-31 20:27 ` Cong Wang
2019-01-31 20:39 ` Andi Kleen [this message]
2019-03-06 23:09 ` Pavel Machek
2019-01-30 18:36 ` Jiri Olsa
2019-01-30 20:39 ` Andi Kleen
2019-01-30 22:33 ` Jiri Olsa
2019-01-31 7:36 ` Jiri Olsa
2019-01-31 8:27 ` Jiri Olsa
2019-02-01 7:43 ` Jiri Olsa
2019-02-01 7:54 ` Ravi Bangoria
2019-02-02 3:24 ` Ravi Bangoria
2019-02-02 10:34 ` Jiri Olsa
2019-02-01 16:27 ` Vince Weaver
2019-02-01 17:38 ` Jiri Olsa
2019-02-02 17:58 ` Vince Weaver
2019-02-04 12:35 ` [PATCH] perf: Add check_period pmu callback Jiri Olsa
2019-02-11 10:11 ` Peter Zijlstra
2019-02-11 13:22 ` [tip:perf/urgent] perf/x86: Add check_period PMU callback tip-bot for Jiri Olsa
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=20190131203927.GY6118@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=vincent.weaver@maine.edu \
--cc=xiyou.wangcong@gmail.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).