linux-kernel - Re: [PATCH 2/2] x86: Introduce 'struct fpu' and related API

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:	Tue, 04 May 2010 11:12:31 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Avi Kivity <avi@...hat.com>
Cc:	"Cui, Dexuan" <dexuan.cui@...el.com>,
	Sheng Yang <sheng@...ux.intel.com>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: Re: [PATCH 2/2] x86: Introduce 'struct fpu' and related API

On Sun, 2010-05-02 at 07:53 -0700, Avi Kivity wrote:
> Currently all fpu state access is through tsk->thread.xstate.  Since we wish
> to generalize fpu access to non-task contexts, wrap the state in a new
> 'struct fpu' and convert existing access to use an fpu API.
> 
> Signal frame handlers are not converted to the API since they will remain
> task context only things.
> 
> Signed-off-by: Avi Kivity <avi@...hat.com>

One comment I have is the name 'fpu'. In future we can use this for non
fpu state aswell. For now, I can't think of a simple and better name. We
can perhaps change it in the future.

Acked-by: Suresh Siddha <suresh.b.siddha@...el.com>

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