Subject: -current XEN3_DOM0 fail
To: None <current-users@netbsd.org>
From: Manuel Bouyer <bouyer@rp.lip6.fr>
List: current-users
Date: 01/08/2008 17:27:03
Hi,
in current building XEN3_DOM0 fails with:
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c: In function 'privpgop_reference':
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c:279: error: 'kmutex_t' has no member named 'lock_data'
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c:281: error: 'kmutex_t' has no member named 'lock_data'
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c: In function 'privpgop_detach':
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c:288: error: 'kmutex_t' has no member named 'lock_data'
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c:291: error: 'kmutex_t' has no member named 'lock_data'
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c:294: error: 'kmutex_t' has no member named 'lock_data'
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c: In function 'privcmd_map_obj':
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c:380: error: 'kmutex_t' has no member named 'lock_data'
/dsk/l1/misc/bouyer/current/src/sys/arch/xen/xen/privcmd.c:384: error: 'kmutex_t' has no member named 'lock_data'
*** [privcmd.o] Error code 1
1 error

Anyone knows what should be used in place of simple_lock()/simple_unlock()
here ?

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