From: Ingo Molnar <mingo@elte.hu>
To: Paul Mundt <lethal@linux-sh.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Jason Baron <jbaron@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.o>
Subject: Re: [GIT PULL] tracing: Syscalls trace events + perf support
Date: Tue, 18 Aug 2009 09:32:11 +0200 [thread overview]
Message-ID: <20090818073211.GA26670@elte.hu> (raw)
In-Reply-To: <20090818004654.GA4402@linux-sh.org>
* Paul Mundt <lethal@linux-sh.org> wrote:
> [ Adding to Cc everyone that now has a broken tree thanks to this .. ]
>
> On Wed, Aug 12, 2009 at 11:11:33AM +0200, Ingo Molnar wrote:
> > * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > > This pull request integrate one cleanup/fix for ftrace and an
> > > update for syscall tracing: the migration from old-style tracer to
> > > individual tracepoints/trace_events and the support for perf
> > > counter.
> > >
> > > I've tested it with success either with ftrace (every syscall
> > > tracepoints enabled at the same time without problems) and with
> > > perfcounter.
> > >
> > > May be one drawback: it creates so much trace events that the
> > > ftrace selftests can take some time :-)
> >
> > Pulled, thanks a lot!
>
> And this has now subsequently broken every single SH and S390
> configuration, [...]
I test SH cross-builds regularly. I just checked the SH defconfig
and it builds just fine here:
$ make -j32 CROSS_COMPILE=sh3-linux- ARCH=sh vmlinux
...
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
phoenix:~/linux/linux> head .config
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.31-rc6
# Tue Aug 18 09:24:28 2009
#
CONFIG_SUPERH=y
CONFIG_SUPERH32=y
# CONFIG_SUPERH64 is not set
CONFIG_ARCH_DEFCONFIG="arch/sh/configs/shx3_defconfig"
AFAICS SH does not even have any syscall tracing added upstream.
Apparently you added them in the SH tree and then they got
integrated in linux-next, and the integrated end result broke?
Mind putting those bits into a separate Git branch and sending them
to the tracing tree too so that we can make sure it's properly
integrated and tested and that any changes to the generic facility
are propagated to SH too?
Thanks,
Ingo
next prev parent reply other threads:[~2009-08-18 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1250016545-6601-1-git-send-email-fweisbec@gmail.com>
[not found] ` <20090812091133.GA21655@elte.hu>
2009-08-18 0:46 ` [GIT PULL] tracing: Syscalls trace events + perf support Paul Mundt
2009-08-18 7:32 ` Ingo Molnar [this message]
2009-08-18 8:51 ` [S390] ftrace: update system call tracer support Ingo Molnar
[not found] ` <20090818085110.GA2074@elte.hu>
2009-08-18 8:59 ` Martin Schwidefsky
2009-08-18 10:05 ` Ingo Molnar
2009-08-18 10:22 ` Martin Schwidefsky
2009-08-18 14:56 ` Jason Baron
2009-08-18 10:25 ` [GIT PULL] tracing: Syscalls trace events + perf support Frederic Weisbecker
2009-08-18 11:06 ` Ingo Molnar
2009-08-18 11:56 ` Paul Mundt
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=20090818073211.GA26670@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.o \
--cc=sfr@canb.auug.org.au \
/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).