LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
David Miller <davem@davemloft.net>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH 0/3] [GIT PULL][v2.6.38] tracing: fix unaligned event arrays
Date: Wed, 26 Jan 2011 07:47:23 +0100 [thread overview]
Message-ID: <20110126064723.GA15752@elte.hu> (raw)
In-Reply-To: <20110126040459.289776311@goodmis.org>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> Ingo,
>
> It was discovered that the alignment of the trace event sections
> break sparc64. The trace events are created by linker magic, so
> gcc does not realize that the structures being allocated will end
> up in an array. Without adding any alignment, x86_64 would create
> the trace event arrays with holes that would break reading the
> events in serial. The fix for that was to force a align(4) to
> keep gcc and the linker from spacing the event structures at various
> alignments. But recent changes have caused this change to break
> sparc due to bad alignment in the structures, caused by the 4 byte
> alignment.
>
> After some discussions, Mathieu came up with the following patch set
> to correctly fix the alignment issues with the trace event structures.
>
> Please pull the latest tip/perf/urgent tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/perf/urgent
>
>
> Mathieu Desnoyers (3):
> Introduce __u64_aligned and U64_ALIGN() for structure alignment in custom sections
> tracing: Fix sparc64 alignment crash with __u64_aligned/U64_ALIGN()
> tracepoints: Use __u64_aligned/U64_ALIGN()
>
> ----
> include/asm-generic/vmlinux.lds.h | 27 +++++++++++-------
> include/linux/align-section.h | 54 +++++++++++++++++++++++++++++++++++++
> include/linux/compiler.h | 8 +++--
> include/linux/ftrace_event.h | 2 +-
> include/linux/syscalls.h | 12 ++++----
> include/linux/tracepoint.h | 12 +++-----
> include/trace/ftrace.h | 8 +++---
> include/trace/syscall.h | 2 +-
> kernel/trace/trace.h | 2 +-
> kernel/trace/trace_export.c | 2 +-
> 10 files changed, 94 insertions(+), 35 deletions(-)
Pulled, thanks a lot Steve!
Ingo
next prev parent reply other threads:[~2011-01-26 6:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 4:04 Steven Rostedt
2011-01-26 4:05 ` [PATCH 1/3] Introduce __u64_aligned and U64_ALIGN() for structure alignment in custom sections Steven Rostedt
2011-01-26 4:05 ` [PATCH 2/3] tracing: Fix sparc64 alignment crash with __u64_aligned/U64_ALIGN() Steven Rostedt
2011-01-26 4:05 ` [PATCH 3/3] tracepoints: Use __u64_aligned/U64_ALIGN() Steven Rostedt
2011-01-27 18:19 ` Jiri Olsa
2011-01-27 18:22 ` Steven Rostedt
2011-01-27 19:09 ` Ingo Molnar
2011-01-27 19:11 ` Steven Rostedt
2011-01-26 6:47 ` Ingo Molnar [this message]
2011-01-26 18:55 ` [PATCH 0/3] [GIT PULL][v2.6.38] tracing: fix unaligned event arrays Steven Rostedt
2011-01-26 20:59 ` Ingo Molnar
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=20110126064723.GA15752@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--subject='Re: [PATCH 0/3] [GIT PULL][v2.6.38] tracing: fix unaligned event arrays' \
/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
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).