From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53276) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZFU6N-0004VO-1s for qemu-devel@nongnu.org; Wed, 15 Jul 2015 17:20:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZFU6M-0001wi-1P for qemu-devel@nongnu.org; Wed, 15 Jul 2015 17:20:26 -0400 Received: from mail-ob0-x233.google.com ([2607:f8b0:4003:c01::233]:36316) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZFU6L-0001wB-TV for qemu-devel@nongnu.org; Wed, 15 Jul 2015 17:20:25 -0400 Received: by obnw1 with SMTP id w1so34965409obn.3 for ; Wed, 15 Jul 2015 14:20:25 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Pranith Kumar Date: Wed, 15 Jul 2015 17:19:55 -0400 Message-ID: Content-Type: multipart/alternative; boundary=001a113d7ba6f2e421051af085f3 Subject: Re: [Qemu-devel] crash using qemu-aarch64-softmmu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: qemu-devel --001a113d7ba6f2e421051af085f3 Content-Type: text/plain; charset=UTF-8 On Wed, Jul 15, 2015 at 4:28 PM, Peter Maydell wrote: > Googling suggests "qsim" is "a project which aims, as part of the > Manifold simulation effort at Georgia Tech, to create a thread safe > multicore emulation library based on the QEMU emulator". > > My immediate guess is that this is buggy and you're causing > QEMU to corrupt some of its data structures by updating > and/or using them from multiple threads at once. > > Can you reproduce the problem with a stock upstream QEMU? > > The qsim changes AFAIU are not causing this. But I understand the apprehension that might be. I will try to reproduce this with an upstream virgin QEMU. Thanks! -- Pranith --001a113d7ba6f2e421051af085f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Jul 15, 2015 at 4:28 PM, Peter Maydell <peter.maydell@l= inaro.org> wrote:
Googling suggests "qsim" is "a project which aims, as= part of the
Manifold simulation effort at Georgia Tech, to create a thread safe
multicore emulation library based on the QEMU emulator".

My immediate guess is that this is buggy and you're causing
QEMU to corrupt some of its data structures by updating
and/or using them from multiple threads at once.

Can you reproduce the problem with a stock upstream QEMU?


The qsim changes AFAIU are not caus= ing this. But I understand the apprehension that might be. I will try to re= produce this with an upstream virgin QEMU.

Thanks!

--
Pranith
--001a113d7ba6f2e421051af085f3--