Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 May 2006 16:06:43 +0800
From:      David Xu <davidxu@freebsd.org>
To:        Rostislav Krasny <rosti.bsd@gmail.com>
Cc:        Igor Sysoev <is@rambler-co.ru>, Colin Percival <cperciva@freebsd.org>, freebsd-current@freebsd.org
Subject:   Re: [PATCH] FreeBSD-SA-06:14.fpu
Message-ID:  <200605211606.43381.davidxu@freebsd.org>
In-Reply-To: <20060520012653.41cf7366.rosti.bsd@gmail.com>
References:  <20060430142408.fcd60069.rosti.bsd@gmail.com> <20060519210105.d4418b6f.rosti.bsd@gmail.com> <20060520012653.41cf7366.rosti.bsd@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605211606.43381.davidxu>