From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IoKRy-00014s-Ui for qemu-devel@nongnu.org; Sat, 03 Nov 2007 10:58:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IoKRv-0000xX-K7 for qemu-devel@nongnu.org; Sat, 03 Nov 2007 10:58:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IoKRv-0000wP-4M for qemu-devel@nongnu.org; Sat, 03 Nov 2007 10:58:11 -0400 Received: from mail.gmx.net ([213.165.64.20]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1IoKRu-0000eX-8z for qemu-devel@nongnu.org; Sat, 03 Nov 2007 10:58:10 -0400 From: Michal Schulz Date: Sat, 3 Nov 2007 15:58:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711031558.03764.michal.schulz@gmx.de> Subject: [Qemu-devel] BUG: fxsave/fxrstor on unaligned address Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hello. According to AMD docs both FXSAVE and FXRSTOR instuctions have to generate GPF if the memory operand is not aligned on a 16-byte boundary. Qemu in contrary does not generate such exception in this case. Unfortunatelly, I'm not able to write proper patch since I have no experience in hacking qemu code (it has to be most likely fixed in the target-i386/translate.c file, around lines 6210-6237). regards, M. -- Michal Schulz