[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.02.1202211338420.5354@i5.linux-foundation.org>
Date: Tue, 21 Feb 2012 13:39:42 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "H. Peter Anvin" <hpa@...or.com>
cc: Josh Boyer <jwboyer@...il.com>,
Jongman Heo <jongman.heo@...sung.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] i387: FP state interface cleanups
From: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Tue, 21 Feb 2012 13:32:49 -0800
Subject: [PATCH 0/2] i387: FP state interface cleanups
This cleans up some of our FP-state mess. The aim is to expose much
less of the internal interfaces and implementation to various users that
really don't care.
We shouldn't export our internal 'fpu_owner_task' tracking to modules,
and we shouldn't expose all the low-level FP state save/restore code to
code that simply must never use it anyway.
This passed allmodconfig on x86-32 and -64.
Linus
Linus Torvalds (2):
i387: uninline the generic FP helpers that we expose to kernel
modules
i387: split up <asm/i387.h> into exported and internal interfaces
arch/x86/ia32/ia32_signal.c | 1 +
arch/x86/include/asm/fpu-internal.h | 520 ++++++++++++++++++++++++++++++
arch/x86/include/asm/i387.h | 590 +----------------------------------
arch/x86/kernel/cpu/common.c | 3 +-
arch/x86/kernel/i387.c | 83 +++++-
arch/x86/kernel/process.c | 1 +
arch/x86/kernel/process_32.c | 1 +
arch/x86/kernel/process_64.c | 1 +
arch/x86/kernel/ptrace.c | 1 +
arch/x86/kernel/signal.c | 1 +
arch/x86/kernel/traps.c | 1 +
arch/x86/kernel/xsave.c | 1 +
arch/x86/kvm/vmx.c | 2 +-
arch/x86/kvm/x86.c | 1 +
arch/x86/power/cpu.c | 1 +
15 files changed, 624 insertions(+), 584 deletions(-)
create mode 100644 arch/x86/include/asm/fpu-internal.h
--
1.7.9.188.g12766.dirty
--
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/
Powered by blists - more mailing lists