linux-kernel - Re: [PATCH 09/10] x86-32: use SSE for atomic64

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]

Date:	Thu, 18 Feb 2010 13:32:26 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Luca Barbieri <luca@...a-barbieri.com>
Cc:	mingo@...e.hu, hpa@...or.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 09/10] x86-32: use SSE for atomic64_read/set if
 available

On Thu, 2010-02-18 at 13:29 +0100, Luca Barbieri wrote:
> >> If we use the stack instead of per-CPU variables, all IRQs and NMIs
> >> preserve CR0 and the SSE registers, so this would be safe, right?
> >
> > You'd have to take special care to deal with nested IRQs I think.
> 
> Could you elaborate on that?
> Which issue could there be with nested IRQs?

Depends on where on the stack you're going to save things, I through
you'd take space in the thread_info struct, but I guess if you're simply
going to push the reg onto the stack it should be fine.

--
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/