From xen-devel-bounces@lists.xen.org Wed May 29 11:26:44 2013 Received: (at maildrop) by bugs.xenproject.org; 29 May 2013 10:26:44 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.72) (envelope-from ) id 1Uhdae-0005f2-9a for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Wed, 29 May 2013 11:26:44 +0100 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhdYt-0005zu-Vz; Wed, 29 May 2013 10:24:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1UhdYs-0005zp-Pz for xen-devel@lists.xen.org; Wed, 29 May 2013 10:24:54 +0000 Received: from [193.109.254.147:17534] by server-16.bemta-14.messagelabs.com id 65/E1-10369-677D5A15; Wed, 29 May 2013 10:24:54 +0000 X-Env-Sender: George.Dunlap@eu.citrix.com X-Msg-Ref: server-3.tower-27.messagelabs.com!1369823064!9427544!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6333 invoked from network); 29 May 2013 10:24:26 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 May 2013 10:24:26 -0000 X-IronPort-AV: E=Sophos;i="4.87,763,1363132800"; d="scan'208";a="27935591" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP/TLS/AES128-SHA; 29 May 2013 10:24:23 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.3; Wed, 29 May 2013 06:24:23 -0400 Received: from elijah.uk.xensource.com ([10.80.2.24]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1UhdYN-0004PM-8c; Wed, 29 May 2013 11:24:23 +0100 Message-ID: <51A5D755.1090800@eu.citrix.com> Date: Wed, 29 May 2013 11:24:21 +0100 From: George Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Keir Fraser References: In-Reply-To: Cc: Fabio Fantoni , Ian Jackson , Ian Campbell , xen-devel@lists.xen.org Subject: Re: [Xen-devel] [PATCH] libxl: Remove qxl support for the 4.3 release X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org On 28/05/13 19:09, Keir Fraser wrote: > On 28/05/2013 17:51, "Ian Jackson" wrote: > >> George Dunlap writes ("[PATCH] libxl: Remove qxl support for the 4.3 >> release"): >>> The qxl drivers for Windows and Linux end up calling instructions >>> that cannot be used for MMIO at the moment. Just for the 4.3 release, >>> remove qxl support. >>> >>> This patch should be reverted as soon as the 4.4 development window opens. >>> >>> The issue in question: >>> >>> (XEN) emulate.c:88:d18 bad mmio size 16 >>> (XEN) io.c:201:d18 MMIO emulation failed @ 0033:7fd2de390430: f3 0f 6f >>> 19 41 83 e8 403 >>> >>> The instruction in question is "movdqu (%rcx),%xmm3". Xen knows how >>> to emulate it, but unfortunately %xmm3 is 16 bytes long, and the interface >>> between Xen and qemu at the moment would appear to only allow MMIO accesses >>> of 8 bytes. >>> >>> It's too late in the release cycle to find a fix or a workaround. >> Acked-by: Ian Jackson > It could be plumbed through hvmemul_do_io's multi-cycle read/write logic, > and done as two 8-byte cycles to qemu. This would avoid bloating the ioreq > structure that communicates to qemu. Would this require changes to qemu? It's definitely too late in the release cycle to be making this kind of change, especially because, as Ian said, we don't know how many more niggles we may run into if we fix this one. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel