Revert previous: calling fpuinit() leads to a panic, as a domU is not

allowed to manipulate cr0 directly. Xen doesn't need this, the fpu is
handled by the hypervisor.
This commit is contained in:
bouyer 2014-02-01 20:07:07 +00:00
parent 6d602218df
commit 454d551267
1 changed files with 2 additions and 3 deletions

View File

@ -1,4 +1,4 @@
/* $NetBSD: hypervisor.c,v 1.64 2014/02/01 17:48:04 dsl Exp $ */
/* $NetBSD: hypervisor.c,v 1.65 2014/02/01 20:07:07 bouyer Exp $ */
/*
* Copyright (c) 2005 Manuel Bouyer.
@ -53,7 +53,7 @@
#include <sys/cdefs.h>
__KERNEL_RCSID(0, "$NetBSD: hypervisor.c,v 1.64 2014/02/01 17:48:04 dsl Exp $");
__KERNEL_RCSID(0, "$NetBSD: hypervisor.c,v 1.65 2014/02/01 20:07:07 bouyer Exp $");
#include <sys/param.h>
#include <sys/systm.h>
@ -256,7 +256,6 @@ hypervisor_attach(device_t parent, device_t self, void *aux)
hac.hac_xencons.xa_device = "xencons";
config_found_ia(self, "xendevbus", &hac.hac_xencons, hypervisor_print);
#endif
fpuinit(&cpu_info_primary);
#ifdef DOM0OPS
#if NPCI > 0
#if NACPICA > 0