LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
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>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/3] [GIT PULL][v2.6.38] tracing: fix unaligned event arrays
Date: Wed, 26 Jan 2011 13:55:07 -0500 [thread overview]
Message-ID: <1296068107.10144.71.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20110126064723.GA15752@elte.hu>
On Wed, 2011-01-26 at 07:47 +0100, Ingo Molnar wrote:
> > 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()
> >
> Pulled, thanks a lot Steve!
>
> Ingo
Hi Ingo,
We (well Peter really) just discovered that this can cause alignment
issues with gcc 4.4.4 and 4.4.5 (I unfortunately only tested it with gcc
4.5.1). We are currently looking into fixing it.
Letting you know so that you don't push this off to Linus ;-)
-- Steve
next prev parent reply other threads:[~2011-01-26 18:55 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 ` [PATCH 0/3] [GIT PULL][v2.6.38] tracing: fix unaligned event arrays Ingo Molnar
2011-01-26 18:55 ` Steven Rostedt [this message]
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=1296068107.10144.71.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--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=mingo@elte.hu \
--cc=peterz@infradead.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).