From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Paul Mackerras <paulus@samba.org>, Michal Marek <mmarek@suse.cz>,
Andrew Randrianasulu <randrik_a@yahoo.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
"K.Prasad" <prasad@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] hw-breakpoint: Fix hardware breakpoints -> perf events dependency
Date: Thu, 17 Dec 2009 18:11:02 +0300 [thread overview]
Message-ID: <20091217151102.GA5414@lenovo> (raw)
In-Reply-To: <1261010034-7786-1-git-send-regression-fweisbec@gmail.com>
On Thu, Dec 17, 2009 at 01:33:54AM +0100, Frederic Weisbecker wrote:
...
>
> This fixes the following kind of build errors:
>
> In file included from arch/x86/kernel/hw_breakpoint.c:31:
> include/linux/hw_breakpoint.h: In function 'hw_breakpoint_addr':
> include/linux/hw_breakpoint.h:39: error: 'struct perf_event' has no member named 'attr'
> include/linux/hw_breakpoint.h: In function 'hw_breakpoint_type':
> include/linux/hw_breakpoint.h:44: error: 'struct perf_event' has no member named 'attr'
> include/linux/hw_breakpoint.h: In function 'hw_breakpoint_len':
> include/linux/hw_breakpoint.h:49: error: 'struct perf_event' has no member named 'attr'
> include/linux/hw_breakpoint.h: In function 'counter_arch_bp':
> include/linux/hw_breakpoint.h:85: error: 'struct perf_event' has no member named 'hw'
>
> v2: Select also ANON_INODES from x86, required for perf
>
...
Thanks Frederic! It did trick for me.
-- Cyrill
next prev parent reply other threads:[~2009-12-17 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 0:26 [PATCH] hw-breakpoint: Fix hardware breakpoints -> perf events dependency Frederic Weisbecker
2009-12-17 0:33 ` [PATCH v2] " Frederic Weisbecker
2009-12-17 15:11 ` Cyrill Gorcunov [this message]
2009-12-18 13:03 ` [tip:perf/urgent] hw-breakpoints: " tip-bot for Frederic Weisbecker
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=20091217151102.GA5414@lenovo \
--to=gorcunov@gmail.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mmarek@suse.cz \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=randrik_a@yahoo.com \
--cc=randy.dunlap@oracle.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