From owner-freebsd-amd64@FreeBSD.ORG  Tue Dec 15 19:20:27 2009
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 895C81065676
	for <freebsd-amd64@FreeBSD.org>; Tue, 15 Dec 2009 19:20:27 +0000 (UTC)
	(envelope-from patfbsd@davenulle.org)
Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19])
	by mx1.freebsd.org (Postfix) with ESMTP id 4D4C48FC08
	for <freebsd-amd64@FreeBSD.org>; Tue, 15 Dec 2009 19:20:27 +0000 (UTC)
Received: from baby-jane.lamaiziere.net (11.158.192-77.rev.gaoland.net
	[77.192.158.11])
	by smtp.lamaiziere.net (Postfix) with ESMTPA id 2926163317E;
	Tue, 15 Dec 2009 20:05:00 +0100 (CET)
Received: from baby-jane.lamaiziere.net (localhost [127.0.0.1])
	by baby-jane.lamaiziere.net (Postfix) with ESMTP id 47B882CEC18;
	Tue, 15 Dec 2009 20:05:00 +0100 (CET)
Date: Tue, 15 Dec 2009 20:04:59 +0100
From: Patrick Lamaiziere <patfbsd@davenulle.org>
To: bug-followup@freebsd.org
Message-ID: <20091215200459.3dbe84eb@baby-jane.lamaiziere.net>
In-Reply-To: <20091216005926.T34815@delplex.bde.org>
References: <200912150035.nBF0ZsLi088804@freefall.freebsd.org>
	<20091216005926.T34815@delplex.bde.org>
X-Mailer: Claws Mail 3.7.3 (GTK+ 2.18.3; i386-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 15 Dec 2009 19:55:31 +0000
Cc: freebsd-amd64@FreeBSD.org
Subject: Re: amd64/135014: [padlock] Using padlock(4) in 8-current triggers
 "fpudna in kernel mode!" warnings
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2009 19:20:27 -0000

Le Wed, 16 Dec 2009 01:35:07 +1100 (EST),
Bruce Evans <brde@optusnet.com.au> a =E9crit :

> [This probably won't make it into the followup, since gnats still
> doesn't generate useful followup addresses and I didn't tyy to edit
> the headers.]
>=20
> > Synopsis: [padlock] Using padlock(4) in 8-current triggers "fpudna
> > in kernel mode!" warnings
>=20
> > By request of Michael Moll in followup, reclassify this as an amd64
> > bug.  His theory is that the floating-point registers may not be
> > being handled correctly in the kernel.
>=20
> This seems to be a bug in padlock(4).  Apparently the inline asm that
> it uses requires the FPU.  But use of the FPU in the kernel is not
> supported. (except the obsolete i586 copy optimizations).

According to the Linux code, padlock does not use the FPU but can
generate a DNA fault:
http://fxr.watson.org/fxr/source/drivers/crypto/padlock-aes.c?v=3Dlinux-2.6=
#L182
=20
They use a irq_ts_save() / restore operation between padlock
intruction. I don't know if there are similar things into the FreeBSD
kernel:
http://fxr.watson.org/fxr/source/drivers/crypto/padlock-aes.c?v=3Dlinux-2.6=
#L296

See also this thread:
http://lkml.indiana.edu/hypermail/linux/kernel/0808.1/0306.html

HTH, regards.