From: Laszlo Ersek <lersek@redhat.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Miroslav Rezanina <mrezanin@redhat.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Petr Matousek <pmatouse@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Xen-devel] qemu(-dm): aborting on wrong mmio size?
Date: Tue, 31 Jan 2012 12:04:14 +0100 [thread overview]
Message-ID: <4F27CAAE.8070602@redhat.com> (raw)
In-Reply-To: <4F27D232020000780007012B@nat28.tlf.novell.com>
On 01/31/12 11:36, Jan Beulich wrote:
>>>> On 31.01.12 at 10:34, Laszlo Ersek<lersek@redhat.com> wrote:
>> Is it justified to kill the emulator when this happens (eg. memory
>> mapped IO with 64-bit operand)?
> The AMD manual specifies that REX.W is ignored; the Intel manual
> doesn't mention REX at all here. However, if a decoder incorrectly
> decodes the guest instruction, that's a bug there. So imo qemu
> validly treats this condition as fatal.
From the Itanium(R) SDM rev 2.3,
10.7.2.1 I/O Port Addressing Restrictions
For the 64MB physical I/O port block the following operations are
undefined and may result in unpredictable processor operation;
references larger than 4-bytes, [...]
It seems that not only a decoding failure can trigger this.
Laszlo
WARNING: multiple messages have this Message-ID (diff)
From: Laszlo Ersek <lersek@redhat.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Miroslav Rezanina <mrezanin@redhat.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Petr Matousek <pmatouse@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Xen-devel] qemu(-dm): aborting on wrong mmio size?
Date: Tue, 31 Jan 2012 12:04:14 +0100 [thread overview]
Message-ID: <4F27CAAE.8070602@redhat.com> (raw)
In-Reply-To: <4F27D232020000780007012B@nat28.tlf.novell.com>
On 01/31/12 11:36, Jan Beulich wrote:
>>>> On 31.01.12 at 10:34, Laszlo Ersek<lersek@redhat.com> wrote:
>> Is it justified to kill the emulator when this happens (eg. memory
>> mapped IO with 64-bit operand)?
> The AMD manual specifies that REX.W is ignored; the Intel manual
> doesn't mention REX at all here. However, if a decoder incorrectly
> decodes the guest instruction, that's a bug there. So imo qemu
> validly treats this condition as fatal.
From the Itanium(R) SDM rev 2.3,
10.7.2.1 I/O Port Addressing Restrictions
For the 64MB physical I/O port block the following operations are
undefined and may result in unpredictable processor operation;
references larger than 4-bytes, [...]
It seems that not only a decoding failure can trigger this.
Laszlo
next prev parent reply other threads:[~2012-01-31 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 9:34 [Qemu-devel] qemu(-dm): aborting on wrong mmio size? Laszlo Ersek
2012-01-31 9:34 ` Laszlo Ersek
2012-01-31 10:36 ` [Qemu-devel] [Xen-devel] " Jan Beulich
2012-01-31 10:36 ` Jan Beulich
2012-01-31 10:54 ` [Qemu-devel] " Laszlo Ersek
2012-01-31 10:54 ` Laszlo Ersek
2012-01-31 11:04 ` Laszlo Ersek [this message]
2012-01-31 11:04 ` Laszlo Ersek
2012-01-31 13:14 ` [Qemu-devel] " Jan Beulich
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=4F27CAAE.8070602@redhat.com \
--to=lersek@redhat.com \
--cc=JBeulich@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.