From: Laszlo Ersek <lersek@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
qemu-devel@nongnu.org
Cc: Miroslav Rezanina <mrezanin@redhat.com>,
Petr Matousek <pmatouse@redhat.com>
Subject: [Qemu-devel] qemu(-dm): aborting on wrong mmio size?
Date: Tue, 31 Jan 2012 10:34:37 +0100 [thread overview]
Message-ID: <4F27B5AD.9050709@redhat.com> (raw)
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
next reply other threads:[~2012-01-31 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 9:34 Laszlo Ersek [this message]
2012-01-31 10:36 ` [Qemu-devel] [Xen-devel] qemu(-dm): aborting on wrong mmio size? Jan Beulich
2012-01-31 10:54 ` Laszlo Ersek
2012-01-31 11:04 ` Laszlo Ersek
2012-01-31 13:14 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F27B5AD.9050709@redhat.com \
--to=lersek@redhat.com \
--cc=mrezanin@redhat.com \
--cc=pmatouse@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).