Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754308Ab2BUVPI (ORCPT ); Tue, 21 Feb 2012 16:15:08 -0500 Received: from terminus.zytor.com ([198.137.202.10]:45906 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752424Ab2BUVPG (ORCPT ); Tue, 21 Feb 2012 16:15:06 -0500 Message-ID: <4F440945.1020904@zytor.com> Date: Tue, 21 Feb 2012 13:14:45 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120131 Thunderbird/10.0 MIME-Version: 1.0 To: Linus Torvalds CC: Josh Boyer , Jongman Heo , Thomas Gleixner , Ingo Molnar , x86@kernel.org, Linux Kernel Mailing List Subject: Re: [PATCH v2 3/3] i387: support lazy restore of FPU state References: <4F42FE08.5020309@zytor.com> <4F43DB69.9060509@zytor.com> In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1161 Lines: 30 On 02/21/2012 10:26 AM, Linus Torvalds wrote: > > Yes, but I'll send you this with a proper commit log. I'll also send > you another patch that splits "" into two. > > Right now has two different users: the first of which > "normal kernel use" kind of things (ie kernel_fpu_begin() and friends) > that really don't care about the internals very deeply. But the second > class of user is the actual i387 internal implementation thing that is > used by i387.c and xsave.c etc to actually implement the exposed > interfaces. > > As a result, is this mixture of exposed interfaces and > "deep internal knowledge". And as a result, that deep internal > knowledge kind of accidentally gets exposed to code that really > shouldn't be exposed to it. > > I have a patch that fixes that. I'll send you a series of two patches > with sign-offs and commentary asap. > Thanks! -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/