linux-kernel - Re: [RFC,v2] x86_64: save

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: <20081118225336.60FFA1544EB@magilla.localdomain>
Date:	Tue, 18 Nov 2008 14:53:36 -0800 (PST)
From:	Roland McGrath <roland@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Jan Beulich <jbeulich@...ell.com>, heukelum@...tmail.fm,
	Andi Kleen <andi@...stfloor.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alexander van Heukelum <heukelum@...lshack.com>,
	Glauber Costa <gcosta@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [RFC,v2] x86_64: save_args out of line

> but that's the exception. Most of the annotations could be
> auto-generated.

Not really.  An implicit .cfi_undefined can be auto-generated for an
unannotated instruction with an output register.  An implicit .cfi_register
can be auto-generated for an unannotated register-to-register move.  An
implicit .cfi_same_value can be auto-generated when you can tell a register
is being written with the register or stack slot tha the current CFI state
says holds the caller's value of that register.  Beyond that, it gets into
either assumptions or hairy analysis of how stack slots are being used and
so forth.  

I don't think auto-generation is very a useful angle to take for this any
time soon.  Explicit (but simple) macros in the assembly is what I favor.

Thanks,
Roland
--
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/