From: Chris Metcalf <cmetcalf@tilera.com>
To: David Miller <davem@davemloft.net>
Cc: <willy@linux.intel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: perf build broke by list_head changes...
Date: Tue, 10 Aug 2010 08:36:46 -0400 [thread overview]
Message-ID: <4C6147DE.9050608@tilera.com> (raw)
In-Reply-To: <20100809.235746.115919762.davem@davemloft.net>
On 8/10/2010 2:57 AM, David Miller wrote:
> Commit:
>
> commit de5d9bf6541736dc7ad264d2b5cc99bc1b2ad958
> Author: Chris Metcalf <cmetcalf@tilera.com>
> Date: Fri Jul 2 13:41:14 2010 -0400
>
> Move list types from <linux/list.h> to <linux/types.h>.
>
> broke the build of 'perf'.
>
> If you move "struct list_head" into types.h, this means perf stops
> building because it depends upon being able to include linux/list.h
> from a userland application and at the same time be able to get the
> basic data types without defining __KERNEL__ or similar.
>
If necessary, it certainly would be easy to move the list.h types to
follow struct ustat, then bump the #endif up above them with a comment
about the perf system's use of them.
I'm confused, though, since <linux/list.h> isn't installed by
headers_install, so how was perf finding that definition before anyway?
I assume the requirement is something fairly stringent, like parsing
binary data structures out of a memory-mapped region or some such;
normally you wouldn't even want to expose the list_head declaration to
user space. I haven't looked at the perf subsystem myself yet so I
don't really know.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2010-08-10 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 6:57 perf build broke by list_head changes David Miller
2010-08-10 12:36 ` Chris Metcalf [this message]
2010-08-10 12:44 ` Sam Ravnborg
2010-08-10 13:46 ` Arnaldo Carvalho de Melo
2010-08-10 14:29 ` Arnd Bergmann
2010-08-10 16:06 ` Arnaldo Carvalho de Melo
2010-08-10 14:32 ` Sam Ravnborg
2010-08-10 16:05 ` Arnaldo Carvalho de Melo
2010-08-10 15:13 ` Matthew Wilcox
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=4C6147DE.9050608@tilera.com \
--to=cmetcalf@tilera.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@linux.intel.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 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.