From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [BUG] Emulation issues
Date: Thu, 30 Jul 2015 14:19:03 +0100
Message-ID: <55BA2447.90407@citrix.com>
References: <55B8A825.5020608@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD02F55E620@AMSPEX01CL02.citrite.net>
	<55B8ACB0.6060406@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD02F55E941@AMSPEX01CL02.citrite.net>
	<55B8DB02.8000904@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD02F55FBC0@AMSPEX01CL02.citrite.net>
	<55B9F98F.1000906@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD02F55FBF8@AMSPEX01CL02.citrite.net>
	<9AAE0902D5BC7E449B7C8E4E778ABCD02F55FCB3@AMSPEX01CL02.citrite.net>
	<55BA213E.2080605@citrix.com>
	<9AAE0902D5BC7E449B7C8E4E778ABCD02F560050@AMSPEX01CL02.citrite.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <prvs=64648bdfb=Andrew.Cooper3@citrix.com>)
	id 1ZKnkC-0004iQ-5F
	for xen-devel@lists.xenproject.org; Thu, 30 Jul 2015 13:19:32 +0000
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD02F560050@AMSPEX01CL02.citrite.net>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Paul Durrant <Paul.Durrant@citrix.com>, Roger Pau Monne <roger.pau@citrix.com>, xen-devel <xen-devel@lists.xenproject.org>
List-Id: xen-devel@lists.xenproject.org

On 30/07/15 14:12, Paul Durrant wrote:
>> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1.
>> (XEN) domain_crash called from io.c:166
>> (XEN) d19v0 weird emulation state 1
>> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1.
>> (XEN) domain_crash called from io.c:166
>> (XEN) d19v0 weird emulation state 1
>> (XEN) io.c:165:d19v0 Weird HVM ioemulation status 1.
>> (XEN) domain_crash called from io.c:166
>>
> Hmm. Can't understand how that's happening... handle_pio() shouldn't be called unless the state is STATE_IORESP_READY and yet the inner function is hitting the default case in the switch.

Sounds like something is changing the state between the two checks.  Is
this shared memory writeable by qemu?

~Andrew