All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
	jolsa@redhat.com, tglx@linutronix.de,
	torvalds@linux-foundation.org, vincent.weaver@maine.edu,
	bp@alien8.de, hpa@zytor.com, eranian@google.com,
	markus.t.metzger@intel.com, acme@redhat.com,
	linux-kernel@vger.kernel.org, acme@infradead.org,
	peterz@infradead.org
Subject: Re: [tip:perf/urgent] perf/x86/intel/pt: Generate PMI in the STOP region as well
Date: Tue, 17 May 2016 10:40:34 +0200	[thread overview]
Message-ID: <20160517084034.GA12163@gmail.com> (raw)
In-Reply-To: <87a8jpta29.fsf@ashishki-desk.ger.corp.intel.com>


* Alexander Shishkin <alexander.shishkin@linux.intel.com> wrote:

> tip-bot for Alexander Shishkin <tipbot@zytor.com> writes:
> 
> > Commit-ID:  ab92b232ae05c382c3df0e3d6a5c6d16b639ac8c
> > Gitweb:     http://git.kernel.org/tip/ab92b232ae05c382c3df0e3d6a5c6d16b639ac8c
> > Author:     Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > AuthorDate: Tue, 10 May 2016 16:18:32 +0300
> > Committer:  Ingo Molnar <mingo@kernel.org>
> > CommitDate: Thu, 12 May 2016 14:45:59 +0200
> >
> > perf/x86/intel/pt: Generate PMI in the STOP region as well
> >
> > Currently, the PT driver always sets the PMI bit one region (page) before
> > the STOP region so that we can wake up the consumer before we run out of
> > room in the buffer and have to disable the event. However, we also need
> > an interrupt in the last output region, so that we actually get to disable
> > the event (if no more room from new data is available at that point),
> > otherwise hardware just quietly refuses to start, but the event is
> > scheduled in and we end up losing trace data till the event gets removed.
> >
> > For a cpu-wide event it is even worse since there may not be any
> > re-scheduling at all and no chance for the ring buffer code to notice
> > that its buffer is filled up and the event needs to be disabled (so that
> > the consumer can re-enable it when it finishes reading the data out). In
> > other words, all the trace data will be lost after the buffer gets filled
> > up.
> >
> > This patch makes PT also generate a PMI when the last output region is
> > full.
> >
> > Reported-by: Markus Metzger <markus.t.metzger@intel.com>
> > Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > Cc: <stable@vger.kernel.org>
> 
> Can we also have this one queued up for stable 4.4 and 4.5?

Agreed.

Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

  reply	other threads:[~2016-05-17  8:40 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 [this message]
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
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=20160517084034.GA12163@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@infradead.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=eranian@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.t.metzger@intel.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.weaver@maine.edu \
    /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.