From owner-freebsd-current@FreeBSD.ORG  Sun May 21 08:06:54 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from localhost.my.domain (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP id D186416A420;
	Sun, 21 May 2006 08:06:53 +0000 (UTC)
	(envelope-from davidxu@freebsd.org)
From: David Xu <davidxu@freebsd.org>
To: Rostislav Krasny <rosti.bsd@gmail.com>
Date: Sun, 21 May 2006 16:06:43 +0800
User-Agent: KMail/1.8.2
References: <20060430142408.fcd60069.rosti.bsd@gmail.com>
	<20060519210105.d4418b6f.rosti.bsd@gmail.com>
	<20060520012653.41cf7366.rosti.bsd@gmail.com>
In-Reply-To: <20060520012653.41cf7366.rosti.bsd@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200605211606.43381.davidxu@freebsd.org>
Content-Type: text/plain;
  charset="gb2312"
Content-Transfer-Encoding: 7bit
Cc: Igor Sysoev <is@rambler-co.ru>, Colin Percival <cperciva@freebsd.org>,
	freebsd-current@freebsd.org
Subject: Re: [PATCH] FreeBSD-SA-06:14.fpu
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 May 2006 08:06:54 -0000

On Saturday 20 May 2006 06:26, Rostislav Krasny wrote:
> Ok, there is the patch. Attached to this email. I tested it on my i386
> 6.1-STABLE with GENERIC and with custom MYKERNEL. MYKERNEL doesn't have
> "options CPU_FXSAVE_LEAK" and it also attached to this email. I changed
> FXSAVE_LEAK to CPU_FXSAVE_LEAK for consistency with other CPU_* options.
> I don't have any amd64 machine, so I didn't test this patch on that
> architecture. Could somebody with amd64 test it?
>
> By the way, following command could be used to check how kernel has
> been compiled, regarding the CPU_FXSAVE_LEAK option:
>
> objdump -x /boot/kernel/kernel | grep fpu_clean_state

The patch looks fine to me, but can it be CPU_FXSAVE_NOLEAK ?
so only people know the problem will turn it on.

David Xu