linux-kernel - Re: [PATCH] x86: clean up after: move entry_64.S register saving out of the macros

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: <20081120162924.GA4243@mailshack.com>
Date:	Thu, 20 Nov 2008 17:29:24 +0100
From:	Alexander van Heukelum <heukelum@...lshack.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andi Kleen <andi@...stfloor.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Jan Beulich <jbeulich@...ell.com>,
	Glauber Costa <gcosta@...hat.com>,
	Matt Mackall <mpm@...enic.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Cyrill Gorcunov <gorcunov@...il.com>
Subject: Re: [PATCH] x86: clean up after: move entry_64.S register saving out of the macros

On Thu, Nov 20, 2008 at 04:57:44PM +0100, Alexander van Heukelum wrote:
> On Thu, Nov 20, 2008 at 04:39:54PM +0100, Ingo Molnar wrote:
> > > > Note, i did a small rename:
> > > > 
> > > >     cfi_pushq  =>  pushq_cfi
> > > >     cfi_popq   =>  popq_cfi
> > > >     cfi_store  =>  movq_cfi
> 
> Does not work... But if you are attached to the underscores, I
> think we can force it to work by using CPP to convert it to
> something the assembler does parse right:

Hi Ingo,

False alarm. It's happily building at the moment. Does it still
fail for you?

Greetings,
	Alexander

> #define pushq_cfi pushq.cfi
> 
> etc?
> 
> Or is that just too ugly?
> 
> Alexander
--
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/