From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laszlo Ersek Subject: qemu(-dm): aborting on wrong mmio size? Date: Tue, 31 Jan 2012 10:34:37 +0100 Message-ID: <4F27B5AD.9050709@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: "xen-devel@lists.xensource.com" , qemu-devel@nongnu.org Cc: Miroslav Rezanina , Petr Matousek List-Id: xen-devel@lists.xenproject.org Hi, in the qemu-xen-unstable tree (git://xenbits.xen.org/qemu-xen-unstable.git), the do_inp() function [i386-dm/helper2.c] makes the process exit if the operand size is wrong. Blame: 6040eea5 ("More files imported from xen-unstable 17192:59b8768d0d0d"). In the qemu tree (git://git.qemu.org/qemu.git), the do_inp() function [xen-all.c] does the same (via hw_error() / abort()). Blame: 9ce94e7c ("xen: Initialize event channels and io rings"). Is it justified to kill the emulator when this happens (eg. memory mapped IO with 64-bit operand)? What would happen on real hardware? If it's "undefined", wouldn't it be "better" (for some definition of "better") to return a constant? Thank you, Laszlo