Re: uvm_fault with -current XEN3_DOMU

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, May 16, 2008 at 03:38:37PM +0200, Manuel Bouyer wrote:
> On Fri, May 16, 2008 at 03:26:20PM +0200, Christoph Egger wrote:
> > > Will try a amd64 domU ...
> > 
> > DomU doesn't need the workaround. DomU is fine. The trouble comes
> > from the cpu/vcpu split in the Dom0.
> 
> amd64 domU doesn't work for me either. I don't undersdand how cpu/vcpu
> would make a difference, as cpu doens't call cpu_identify(), and
> vcpu is the same for dom0 or domU. Beside, cpu_class is initialised to
> I686_CPU in amd64/machdep.c ... there must be something else.

OK, cpuid_level isn't initialised on Xen/amd64. The attached patch makes
an amd64 domU boot again.

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--

Index: amd64/locore.S
===================================================================
RCS file: /cvsroot/src/sys/arch/amd64/amd64/locore.S,v
retrieving revision 1.44
diff -u -r1.44 locore.S
--- amd64/locore.S      11 May 2008 13:33:54 -0000      1.44
+++ amd64/locore.S      16 May 2008 14:21:29 -0000
@@ -770,6 +770,10 @@
        subq    $8, %rax
        movq    %rax, %rsp
 
+       xorl    %eax,%eax
+       cpuid
+       movl    %eax,_C_LABEL(cpuid_level)
+
        call    xen_pmap_bootstrap
 
        /*