From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: a.p.zijlstra@chello.nl, mingo@elte.hu, paulus@samba.org,
cjashfor@linux.vnet.ibm.com, fweisbec@gmail.com,
eranian@google.com, gorcunov@openvz.org, tzanussi@gmail.com,
mhiramat@redhat.com, robert.richter@amd.com, fche@redhat.com,
linux-kernel@vger.kernel.org, masami.hiramatsu.pt@hitachi.com,
drepper@gmail.com, asharma@fb.com,
benjamin.redelings@nescent.org
Subject: Re: [PATCH 1/7] perf: Unified API to record selective sets of arch registers
Date: Mon, 30 Jul 2012 14:23:59 -0300 [thread overview]
Message-ID: <20120730172358.GA1004@infradead.org> (raw)
In-Reply-To: <1343391834-10851-2-git-send-email-jolsa@redhat.com>
Em Fri, Jul 27, 2012 at 02:23:42PM +0200, Jiri Olsa escreveu:
> This brings a new API to help the selective dump of registers on
> event sampling, and its implementation for x86 arch.
CC arch/x86/kernel/perf_regs.o
/home/git/linux/arch/x86/kernel/perf_regs.c: In function
‘perf_reg_validate’:
/home/git/linux/arch/x86/kernel/perf_regs.c:83: error: ‘EINVAL’
undeclared (first use in this function)
/home/git/linux/arch/x86/kernel/perf_regs.c:83: error: (Each undeclared
identifier is reported only once
/home/git/linux/arch/x86/kernel/perf_regs.c:83: error: for each function
it appears in.)
- Arnaldo
next prev parent reply other threads:[~2012-07-30 17:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 12:23 [PATCHv8 00/13] perf: Add backtrace post dwarf unwind Jiri Olsa
2012-07-27 12:23 ` [PATCH 1/7] perf: Unified API to record selective sets of arch registers Jiri Olsa
2012-07-30 17:23 ` Arnaldo Carvalho de Melo [this message]
2012-07-27 12:23 ` [PATCH 2/7] perf: Add ability to attach user level registers dump to sample Jiri Olsa
2012-07-27 12:23 ` [PATCH 3/7] perf, x86: Add copy_from_user_nmi_nochk for best effort copy Jiri Olsa
2012-07-27 12:23 ` [PATCH 4/7] perf: Factor __output_copy to be usable with specific copy function Jiri Olsa
2012-07-27 12:23 ` [PATCH 5/7] perf: Add perf_output_skip function to skip bytes in sample Jiri Olsa
2012-07-27 12:23 ` [PATCH 6/7] perf: Add ability to attach user stack dump to sample Jiri Olsa
2012-07-27 12:23 ` [PATCH 7/7] perf: Add attribute to filter out callchains Jiri Olsa
2012-07-27 12:23 ` [PATCH 08/13] perf, tool: Adding PERF_ATTR_SIZE_VER2 to the header swap check Jiri Olsa
2012-07-27 12:23 ` [PATCH 09/13] perf, tool: Add interface to arch registers sets Jiri Olsa
2012-07-27 12:23 ` [PATCH 10/13] perf, tool: Add libunwind dependency for dwarf cfi unwinding Jiri Olsa
2012-07-27 12:23 ` [PATCH 11/13] perf, tool: Support user regs and stack in sample parsing Jiri Olsa
2012-07-27 12:23 ` [PATCH 12/13] perf, tool: Support for dwarf cfi unwinding on post processing Jiri Olsa
2012-07-27 12:23 ` [PATCH 13/13] perf, tool: Support for dwarf mode callchain on perf record Jiri Olsa
2012-08-01 4:04 ` [PATCHv8 00/13] perf: Add backtrace post dwarf unwind Stephane Eranian
2012-08-01 8:57 ` 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=20120730172358.GA1004@infradead.org \
--to=acme@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=asharma@fb.com \
--cc=benjamin.redelings@nescent.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=drepper@gmail.com \
--cc=eranian@google.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@openvz.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=robert.richter@amd.com \
--cc=tzanussi@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).