linux-kernel - Re: [PATCH 10/11] x86/xip: resolve alternative instructions at build

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: <20150323083821.GB31992@pd.tnic>
Date:	Mon, 23 Mar 2015 09:38:21 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Jim Kukunas <james.t.kukunas@...ux.intel.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	tom.zanussi@...ux.intel.com,
	Arjan van de Ven <arjan@...ux.intel.com>,
	"H. Peter Anvin" <hpa@...or.com>, tglx@...utronix.de,
	mingo@...hat.com, x86@...nel.org
Subject: Re: [PATCH 10/11] x86/xip: resolve alternative instructions at build

On Mon, Mar 23, 2015 at 09:33:02AM +0100, Borislav Petkov wrote:
> is this it? To save some memory? Probably embedded, maybe some light
> bulb running linux... Yuck.

Oh, one more thing: AFAICT, you're adding the whole XIP functionality
with a bunch of ifdeffery in the main code paths. It might be better to
extract and put all that code in arch/x86/xip/, away from the generic
paths. I'm thinking there will be more XIP code coming besides this
patchset so designing it clean from the get-go should pay out handsomely
later.

Hmm.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/