From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: Trilok Soni <soni.trilok@gmail.com>,
ltt-dev@lists.casi.polymtl.ca,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [ltt-dev] LTTng 0.89 for Linux 2.6.29-rc3
Date: Sun, 8 Feb 2009 07:47:11 -0800 [thread overview]
Message-ID: <20090208154711.GA527@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090206213701.GN10918@linux.vnet.ibm.com>
On Fri, Feb 06, 2009 at 01:37:01PM -0800, Paul E. McKenney wrote:
> On Fri, Feb 06, 2009 at 03:03:29PM -0500, Mathieu Desnoyers wrote:
> > * Paul E. McKenney (paulmck@linux.vnet.ibm.com) wrote:
> > > On Thu, Feb 05, 2009 at 09:00:05PM -0500, Mathieu Desnoyers wrote:
> > > > * Paul E. McKenney (paulmck@linux.vnet.ibm.com) wrote:
[ . . . ]
> > > > > CC arch/powerpc/kernel/asm-offsets.s
> > > > > In file included from include/linux/module.h:18,
> > > > > from include/linux/sysdev.h:25,
> > > > > from include/linux/node.h:22,
> > > > > from include/linux/swap.h:10,
> > > > > from include/linux/suspend.h:7,
> > > > > from arch/powerpc/kernel/asm-offsets.c:24:
> > > > > include/linux/immediate.h:15:27: error: asm/immediate.h: No such file or directory
> > > > > In file included from include/linux/module.h:18,
> > > > > from include/linux/sysdev.h:25,
> > > > > from include/linux/node.h:22,
> > > > > from include/linux/swap.h:10,
> > > > > from include/linux/suspend.h:7,
> > > > > from arch/powerpc/kernel/asm-offsets.c:24:
> > > > > include/linux/immediate.h:37: warning: ‘struct __imv’ declared
> > > > > inside parameter list
> > > > > include/linux/immediate.h:37: warning: its scope is only this definition
> > > > > or declaration, which is probably not what you want
> > > > > include/linux/immediate.h:40: warning: ‘struct __imv’ declared
> > > > > inside parameter list
> > > > > make[1]: *** [arch/powerpc/kernel/asm-offsets.s] Error 1
> > > > > make: *** [prepare0] Error 2
> > > > > 02/05/2009-17:57:41 Build the kernel. Failed rc = 2
> > > > > 02/05/2009-17:57:41 build: Building kernel... Failed rc = 1
> > > > >
> > > >
> > > > Hrm, does the file
> > > >
> > > > arch/powerpc/include/asm/immediate.h exist in your tree ?
> > > >
> > > > Here, with the setup done following the commands I gave you (minus the
> > > > mkdir patch), I get :
> > > >
> > > >
> > > > compudj@ok:~$ head testpaulmck/linux-2.6.29-rc3/arch/powerpc/include/asm/immediate.h
> > > > #ifndef _ASM_POWERPC_IMMEDIATE_H
> > > > #define _ASM_POWERPC_IMMEDIATE_H
> > > >
> > > > /*
> > > > * Immediate values. PowerPC architecture optimizations.
> > > > *
> > > > * (C) Copyright 2006 Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> > > > *
> > > > * This file is released under the GPLv2.
> > > > * See the file COPYING for more details.
> > > >
> > > > ....
> > > >
> > > > Which defines struct __imv. So hrm, normally the header should be there.
> > > > (/me still confused) :)
> > >
> > > It does indeed, see the patch I generated against 2.6.29-rc3:
> > >
> > > http://www.rdrop.com/users/paulmck/patches/2.6.29-rc3-ltt-1.patch
> > >
> > > I get a similar failure on x86 -- perhaps my tools or build environment
> > > does not match yours?
> > >
> >
> > Maybe. If you want a quick and dirty solution, try :
> >
> > CONFIG_IMMEDIATE=n
> >
> > Immediate values are just an optimization, not necessary anyway.
>
> K -- kicking it off.
One thing that helps on 32-bit x86 is removing the "select HAVE_IMMEDIATE"
that you added to arch/x86/Kconfig. I then get assembly errors:
AS arch/x86/kernel/entry_32.o
arch/x86/kernel/entry_32.S: Assembler messages:
arch/x86/kernel/entry_32.S:272: Error: invalid character '_' in
mnemonic
make[1]: *** [arch/x86/kernel/entry_32.o] Error 1
make: *** [arch/x86/kernel] Error 2
This seems to point to the following new line:
INTERRUPT_RETURN_NMI_SAFE
Replacing this with the NATIVE_INTERRUPT_RETURN_NMI_SAFE that appears
elsewhere did not help.
Over to you!
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-08 15:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 20:07 LTTng 0.89 for Linux 2.6.29-rc3 Mathieu Desnoyers
2009-02-05 14:04 ` Paul E. McKenney
2009-02-05 15:02 ` Mathieu Desnoyers
2009-02-05 15:18 ` Paul E. McKenney
2009-02-05 15:38 ` [ltt-dev] " Mathieu Desnoyers
2009-02-05 15:58 ` Paul E. McKenney
2009-02-05 16:22 ` Trilok Soni
2009-02-05 18:01 ` Paul E. McKenney
2009-02-05 18:31 ` Mathieu Desnoyers
2009-02-05 18:44 ` Paul E. McKenney
2009-02-05 20:22 ` Mathieu Desnoyers
2009-02-05 21:04 ` Paul E. McKenney
2009-02-05 21:06 ` Mathieu Desnoyers
2009-02-06 0:33 ` Paul E. McKenney
2009-02-06 2:00 ` Mathieu Desnoyers
2009-02-06 13:48 ` Paul E. McKenney
2009-02-06 20:03 ` Mathieu Desnoyers
2009-02-06 21:37 ` Paul E. McKenney
2009-02-08 15:47 ` Paul E. McKenney [this message]
2009-02-05 16:28 ` Trilok Soni
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=20090208154711.GA527@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=compudj@krystal.dyndns.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=soni.trilok@gmail.com \
--cc=tytso@mit.edu \
/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).