From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: xenstored crashes with SIGSEGV
Date: Tue, 16 Dec 2014 16:23:49 +0000
Message-ID: <1418747029.16425.238.camel@citrix.com>
References: <546461A2.2070908@univention.de>
	<1415869951.31613.26.camel@citrix.com> <548B1472.5080302@univention.de>
	<1418401932.16425.34.camel@citrix.com> <548B1BA8.3090504@univention.de>
	<1418403387.16425.38.camel@citrix.com> <548B23FA.6070108@univention.de>
	<1418407116.16425.53.camel@citrix.com>
	<1418649458.16425.108.camel@citrix.com> <548EEDF5.20808@univention.de>
	<1418655014.16425.138.camel@citrix.com>
	<1418665524.16425.171.camel@citrix.com>
	<548F60BF.4020901@univention.de>
	<1418726712.16425.213.camel@citrix.com>
	<1418727970.16425.217.camel@citrix.com>
	<CAHt6W4cfQ+JzhS1zBL4iCWJ3Mg9R25zhG1Wjr=1ukwW0qykNTQ@mail.gmail.com>
	<1418732635.16425.221.camel@citrix.com>
	<CAHt6W4eLJ-FNwdLmDHuZFKpEcc+eQn0AmnFdtvBW7g3KUu96QQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <CAHt6W4eLJ-FNwdLmDHuZFKpEcc+eQn0AmnFdtvBW7g3KUu96QQ@mail.gmail.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Frediano Ziglio <freddy77@gmail.com>
Cc: Philipp Hahn <hahn@univention.de>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On Tue, 2014-12-16 at 16:13 +0000, Frediano Ziglio wrote:
> What does "info all-registers" gdb command say about SSE registers?

All zeroes. No ffs anywhere.

> Do we have a bug in Xen that affect SSE instructions (possibly already
> fixed after Philipp version) ?

Possibly. When this was thought to be xenstored (which doesn't change
all that much) debugging 4.1 seemed plausible, but since it could be
anywhere else I think we either need a plausible reproduction, or a
repro on a newer hypervisor (or possibly kernel) I'm afraid.

Ian.