From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d99FI-0002SU-Ei for qemu-devel@nongnu.org; Fri, 12 May 2017 08:00:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d99FF-0001o2-E7 for qemu-devel@nongnu.org; Fri, 12 May 2017 08:00:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54424) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1d99FF-0001n8-7N for qemu-devel@nongnu.org; Fri, 12 May 2017 08:00:29 -0400 References: <6e9a0dff-949f-5ac9-2315-cbe0e4c99f58@redhat.com> <0c725626-6485-c777-46e3-99423670df89@redhat.com> From: Paolo Bonzini Message-ID: <7e48191b-d660-ded5-0382-5643b0c15ce4@redhat.com> Date: Fri, 12 May 2017 14:00:24 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Guest SIGILL when different IO is implemented List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Miltiadis Hatzimihail Cc: qemu-devel@nongnu.org On 12/05/2017 09:26, Miltiadis Hatzimihail wrote: > I ve tried the same today using a 32-bit Guest OS and the illegal > instruction this time is >=20 > fstps %(ecx) >=20 > Is it a similar case to the movss one? (the previous Guest I was using > was 64 bit). Yes, it is. Paolo > Also, I had to start QEMU using the following command line options: >=20 > qemu -cpu host,-sse2=20 >=20 > because one my programs was giving me an illegal instruction based on > the above and it worked by disabling it. >=20 > =E2=80=8BRegards > Milton >=20 > On Thu, May 11, 2017 at 2:12 PM, Miltiadis Hatzimihail > > wrote: >=20 > Ok many thanks for your help. >=20 > =E2=80=8BMilton >=20 > On Thu, May 11, 2017 at 2:11 PM, Paolo Bonzini > wrote: >=20 >=20 >=20 > On 11/05/2017 14:47, Miltiadis Hatzimihail wrote: > > That's great thanks for the clarification. > > > > Is this patch going to make it to the mainline at some point? >=20 > Not exactly as is, because it has a small defect (it always rea= ds 16 > bytes from memory), but something like that will. >=20 > Paolo >=20 >=20 >=20