From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41004) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNxiO-0001Xn-DS for qemu-devel@nongnu.org; Fri, 15 Jul 2016 03:39:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bNxiK-0005WW-C8 for qemu-devel@nongnu.org; Fri, 15 Jul 2016 03:39:16 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:42420 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bNxiK-0005WA-11 for qemu-devel@nongnu.org; Fri, 15 Jul 2016 03:39:12 -0400 Message-ID: <57889319.3030609@kamp.de> Date: Fri, 15 Jul 2016 09:39:05 +0200 From: Peter Lieven MIME-Version: 1.0 References: <57888385.1080403@suse.com> In-Reply-To: <57888385.1080403@suse.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Regression with commit 095497ffc66b7f031 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juergen Gross , xen-devel , "qemu-devel@nongnu.org" Cc: Gerd Hoffmann , Paolo Bonzini Am 15.07.2016 um 08:32 schrieb Juergen Gross: > Commit 095497ffc66b7f031ff2a17f1e50f5cb105ce588 ("vnc-enc-tight: use > thread local storage for palette") introduced a regression with Xen: > Since this commit qemu used as a device model is no longer capable > to register Xenstore watches (that's the effect visible to a user). > Reverting this commit makes qemu behave well again. I have no idea > why that commit would have this effect with Xen, may be some memory > is clobbered? I personally have no idea, maybe @Paolo has? Maybe the corruption happens somewhere else and is just visible due to this change. Do you see sth when you ran qemu/xen in valgrind? Peter