WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] regression from c/s 22071:c5aed2e049bc (ept: Put locks a

To: Keir Fraser <keir@xxxxxxx>
Subject: Re: [Xen-devel] regression from c/s 22071:c5aed2e049bc (ept: Put locks around ept_get_entry) ?
From: Olaf Hering <olaf@xxxxxxxxx>
Date: Fri, 17 Dec 2010 15:03:53 +0100
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Fri, 17 Dec 2010 06:04:54 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1292594642; l=4689; s=domk; d=aepfle.de; h=In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version: References:Subject:Cc:To:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=w5d8+8AQnNb+bArfveS9/eGo9Do=; b=a+sbKGHDn4WjUSPZp728dSgpeuLa7LqnSWxFhwJ8oIBj5L57nIVlw59jK/v+YJQDSDQ YC6Z+IdTA4DjTD/uR3p8so1co+hDA+cdwhaRLIm833WNUrvImPAOBCPi/1JzLsTJdLkzX 207wsZHyGkPQRJAeHmDz2q4UIEWVnOkY55k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C92FF6CF.295FC%keir@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D0A516B0200007800028755@xxxxxxxxxxxxxxxxxx> <C92FF6CF.295FC%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Thu, Dec 16, Keir Fraser wrote:

> Excellent. I will lay groundwork and fix pte_{read,write}_atomic directly in
> -unstable and -4.0-testing. I will then post a proposed fix for EPT to the
> list. I don't know that code so well and I may not otherwise catch all
> places that require use of the new accessor macros.

Keir,

this failure may be related to the changes that went just into
xen-unstable, fails in openSuSE 11.2 and 11.3 on 32bit:

make[2]: Entering directory 
`/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/arch/x86'
gcc -fomit-frame-pointer -fmessage-length=0 -O2 -Wall  -D_FORTIFY_SOURCE=2 
-fstack-protector -funwind-tables  -fasynchronous-unwind-tables -O1 
-fno-omit-frame-pointer  -fno-optimize-sibling-calls -m32 -march=i686 -g 
-fno-strict-aliasing  -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value  
-Wdeclaration-after-statement  -nostdinc -fno-builtin -fno-common  
-Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe  
-I/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include   
-I/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/asm-x86/mach-generic
   
-I/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/asm-x86/mach-default
  -msoft-float -fno-stack-protector -fno-exceptions -g -D__XEN__  -DVERBOSE 
-DCRASH_DEBUG -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER  
-DMAX_PHYS_CPUS=32 -MMD -MF .xen.d -O1 -fno-omit-frame-pointer  
-fno-optimize-sibling-calls -m32 -march=i686 -g -fno-strict-aliasing  
-std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value  
-Wdeclaration-after-statement  -nostdinc -fno-builtin -fno-common  
-Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe  
-I/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include   
-I/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/asm-x86/mach-generic
   
-I/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/asm-x86/mach-default
  -msoft-float -fno-stack-protector -fno-exceptions -g -D__XEN__  -DVERBOSE 
-DCRASH_DEBUG -fno-omit-frame-pointer -DCONFIG_FRAME_POINTER  
-DMAX_PHYS_CPUS=32 -MMD -MF .asm-offsets.s.d -S -o asm-offsets.s  
x86_32/asm-offsets.c
cc1: warnings being treated as errors
In file included from 
/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/asm/spinlock.h:6,
                 from 
/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/xen/spinlock.h:6,
                 from 
/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/xen/sched.h:7,
                 from x86_32/asm-offsets.c:9:
/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/asm/atomic.h: In 
function 'atomic_write64':
/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/include/asm/atomic.h:39: 
error: operation on 'old' may be undefined
make[2]: *** [asm-offsets.s] Error 1
make[2]: Leaving directory 
`/usr/src/packages/BUILD/xen-unstable.hg-4.1.22571/xen/arch/x86'

 36 static inline void atomic_write64(volatile uint64_t *addr, uint64_t val)
 37 {
 38     uint64_t old = *addr, new, *__addr = (uint64_t *)addr;
 39     while ( (old = __cmpxchg8b(__addr, old, val)) != old )
 40         old = new;
 41 }


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>