linux-kernel - Re: [PATCH] ftrace: update recordmount.pl arch changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.1.10.0808151156170.2188@gandalf.stny.rr.com>
Date:	Fri, 15 Aug 2008 11:57:24 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] ftrace: update recordmount.pl arch changes


On Fri, 15 Aug 2008, Ingo Molnar wrote:

> 
> * Steven Rostedt <rostedt@...dmis.org> wrote:
> 
> > Ingo,
> > 
> > I'm trying to keep all the arch changes in recordmcount.pl in one 
> > place. I moved your code into that area, by adding the flags to the 
> > commands that were passed in.
> > 
> > Does this change still work for you when compiling i386 on a x86_64 
> > box?
> 
> actually, i thought of this as a quick hack to let -tip testing 
> continue. Dont we have all the proper information available in kbuild 
> and should just pass that to scripts/recordmcount.pl when called - like 
> we pass in things like OBJDUMP which might have cross-build overrides, 
> etc.

OK, I'll set up one of my x86_64 boxes to compile the kernel for i386s, 
and see if I can come up with something.

The reason I did this patch, is to get the PPC patches ready to go on top.

I still need to port to ppc32 (I have 64 working).

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/