From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, ak@linux.intel.com,
jolsa@redhat.com, acme@redhat.com, cebbert.lkml@gmail.com
Subject: Re: [PATCH v6 0/6] perf: add ability to sample interrupted machine state
Date: Wed, 24 Sep 2014 09:49:27 +0200 [thread overview]
Message-ID: <20140924074927.GS16043@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1411484269-32311-1-git-send-email-eranian@google.com>
On Tue, Sep 23, 2014 at 04:57:43PM +0200, Stephane Eranian wrote:
> In V6, we added the missing copy of the eflags from the PEBS
> mahcine state (reported by Andi). We fixed some formatting
> issues. We rebased to 3.17-rc6.
../arch/x86/kernel/cpu/perf_event_intel_ds.c: In function ‘__intel_pmu_pebs_event’:
../arch/x86/kernel/cpu/perf_event_intel_ds.c:899:7: error: ‘struct pt_regs’ has no member named ‘eflags’
You mean that?
next prev parent reply other threads:[~2014-09-24 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:57 Stephane Eranian
2014-09-23 14:57 ` [PATCH v6 1/6] perf: add ability to sample machine state on interrupt Stephane Eranian
2014-09-23 14:57 ` [PATCH v6 2/6] perf/x86: add support for sampling PEBS machine state registers Stephane Eranian
2014-09-24 7:49 ` Peter Zijlstra
2014-09-23 14:57 ` [PATCH v6 3/6] perf tools: add core support for sampling intr machine state regs Stephane Eranian
2014-09-23 14:57 ` [PATCH v6 4/6] perf/tests: add interrupted state sample parsing test Stephane Eranian
2014-09-23 14:57 ` [PATCH v6 5/6] perf record: add new -I option to sample interrupted machine state Stephane Eranian
2014-09-23 14:57 ` [PATCH v6 6/6] perf: improve perf_sample_data struct layout Stephane Eranian
2014-09-24 7:49 ` Peter Zijlstra [this message]
2014-09-24 8:31 ` [PATCH v6 0/6] perf: add ability to sample interrupted machine state Stephane Eranian
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=20140924074927.GS16043@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=cebbert.lkml@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome