From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ik5ss-0006pK-1f
	for qemu-devel@nongnu.org; Mon, 22 Oct 2007 18:36:30 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ik5sp-0006nD-Vy
	for qemu-devel@nongnu.org; Mon, 22 Oct 2007 18:36:29 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ik5sp-0006n5-NX
	for qemu-devel@nongnu.org; Mon, 22 Oct 2007 18:36:27 -0400
Received: from bangui.magic.fr ([195.154.194.245])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <l_indien@magic.fr>) id 1Ik5sp-0001DF-6Z
	for qemu-devel@nongnu.org; Mon, 22 Oct 2007 18:36:27 -0400
Subject: Re: [Qemu-devel] PreP kernels boot using Qemu
From: "J. Mayer" <l_indien@magic.fr>
In-Reply-To: <471D1E98.50303@aurel32.net>
References: <1193038567.16781.108.camel@rapid>
	<20071022162810.GA12778@hall.aurel32.net>
	<1193087522.16781.121.camel@rapid>  <471D1E98.50303@aurel32.net>
Content-Type: text/plain; charset=ISO-8859-15
Date: Tue, 23 Oct 2007 00:36:12 +0200
Message-Id: <1193092572.16781.128.camel@rapid>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org


On Tue, 2007-10-23 at 00:05 +0200, Aurelien Jarno wrote:
> J. Mayer a =E9crit :
> > On Mon, 2007-10-22 at 18:28 +0200, Aurelien Jarno wrote:
> >> On Mon, Oct 22, 2007 at 09:36:07AM +0200, J. Mayer wrote:
> >>> Hi all,
> >>>
> >>> I've been investigating more about PreP kernel boot using Qemu and =
I
> >>> achieved to boot 2.4.35, 2.6.12 and 2.6.22 kernels using Qemu CVS a=
nd
> >>> unmodified OHW.
[...]
> >> - The "floating point" problem I reported during the week-end does
> not
> >>   exists, probably because of the switch from powerpc to ppc. I
> still=20
> >>   don't know if it is a kernel problem or a QEMU problem (or both).
> >=20
> > There may be issues with the floating point emulation, especially if
> > some kernel or programs relies on the FPSCR (floating-point status)
> > register which is never updated in Qemu.
> >=20
>=20
> Is there any technical reason behind that, or is it just a lack of
> time?

I can say  both:
for most program, using floating point arithmetic ala "fast-math", it's
not necessary to maintain a precise FPU state, as those program will
never raise any FPU exception, never generate NaNs, infinites, ...
The other reason is that it would need to check every FPU insn arguments
and results at run time and treat all special cases following the actual
PowerPC implementations behavior if we want to get a precise emulation.
This behavior could be for example selected at compile time: then one
would have the choice to have a quick FPU emulation model or a precise
one.

--=20
J. Mayer <l_indien@magic.fr>
Never organized