From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] perf tools: Fix seg fault with Intel PT
Date: Tue, 26 Jan 2016 11:30:14 -0300 [thread overview]
Message-ID: <20160126143014.GD4361@kernel.org> (raw)
In-Reply-To: <56A77C18.60407@intel.com>
Em Tue, Jan 26, 2016 at 04:00:56PM +0200, Adrian Hunter escreveu:
> On 26/01/16 15:54, Arnaldo Carvalho de Melo wrote:
> > [acme@ssdandy linux]$
> > So, this needs:
> > 1) A machine that supports Intel PT
> > 2) A kernel that supports Intel PT
> > 3) A kernel that doesn't have perf_event_attr.context_switch, so that it tries
> > to use sched:sched_switch
> > 4) an unreadable tracefs
> > What was the kernel where you stumbled on this problem? What machine?
> Kernel was v4.2, machine was Broadwell.
> context_switch was added in v4.3 I think, and PT was v4.1
> so I guess v4.1 and v4.2 are affected.
Thanks for the info, my new main machine is a t450s, so Broadwell, will
boot with 4.1/4.2.
- Arnaldo
next prev parent reply other threads:[~2016-01-26 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 12:05 [PATCH 0/2] perf tools: Fix seg fault with Intel PT Adrian Hunter
2016-01-26 12:05 ` [PATCH 1/2] " Adrian Hunter
2016-01-26 13:23 ` Arnaldo Carvalho de Melo
2016-01-26 13:34 ` Adrian Hunter
2016-01-26 13:54 ` Arnaldo Carvalho de Melo
2016-01-26 14:00 ` Adrian Hunter
2016-01-26 14:30 ` Arnaldo Carvalho de Melo [this message]
2016-02-04 7:57 ` [tip:perf/urgent] perf tools: tracepoint_error() can receive e= NULL, robustify it tip-bot for Adrian Hunter
2016-01-26 12:05 ` [PATCH 2/2] perf tools: Fix another seg fault using Intel PT Adrian Hunter
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=20160126143014.GD4361@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).