All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH] perf/core: fix a possible deadlock scenario
Date: Thu, 19 Jul 2018 15:28:34 +0200	[thread overview]
Message-ID: <20180719132834.GF18667@krava> (raw)
In-Reply-To: <CAM_iQpVX_9C42Wh+ydti=droRz_Xs_Cv4ovVcg4nqu+n1OScKg@mail.gmail.com>

On Wed, Jul 18, 2018 at 01:21:11PM -0700, Cong Wang wrote:

SNIP

> > hum, the swevent pmu does not triger NMI, so that timer
> > will never be touched in NMI context
> 
> Good to know! So I worry too much here.
> 
> But still, given hrtimer interrupt is called with IRQ disabled, getting
> stuck in a hrtimer callback could also block IPI handler, therefore
> causing soft lockups.
> 
> Let me know if you want me to adjust the changelog for this.

yep, it's confusing, I think it should be removed from changelog

jirka

  reply	other threads:[~2018-07-19 13:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 21:51 [PATCH] perf/core: fix a possible deadlock scenario Cong Wang
2018-07-18  8:19 ` Jiri Olsa
2018-07-18 20:21   ` Cong Wang
2018-07-19 13:28     ` Jiri Olsa [this message]
2018-07-19 19:12       ` [PATCH v2] " Cong Wang
2018-07-20 11:52         ` Peter Zijlstra
2018-07-23 23:16           ` Cong Wang
2018-07-24  1:35             ` Cong Wang
2018-07-24  1:44               ` Cong Wang
2018-07-24  9:18                 ` Peter Zijlstra
2018-07-25 18:44                   ` Cong Wang
2018-07-24  9:12             ` Peter Zijlstra

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=20180719132834.GF18667@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.