From xen-devel-bounces@lists.xen.org Wed May 29 08:45:31 2013 Received: (at maildrop) by bugs.xenproject.org; 29 May 2013 07:45:31 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.72) (envelope-from ) id 1Uhb4d-0003ot-U2 for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Wed, 29 May 2013 08:45:31 +0100 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uhb31-00009X-1n; Wed, 29 May 2013 07:43:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Uhb30-00009L-5q for xen-devel@lists.xen.org; Wed, 29 May 2013 07:43:50 +0000 Received: from [85.158.139.211:12972] by server-9.bemta-5.messagelabs.com id E3/E4-14875-5B1B5A15; Wed, 29 May 2013 07:43:49 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1369813428!20024545!1 X-Originating-IP: [46.33.159.39] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNDYuMzMuMTU5LjM5ID0+IDI2MzI1\n X-StarScan-Received: X-StarScan-Version: 6.9.6; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26525 invoked from network); 29 May 2013 07:43:48 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (46.33.159.39) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 29 May 2013 07:43:48 -0000 X-IronPort-AV: E=Sophos;i="4.87,763,1363132800"; d="scan'208";a="5078020" Received: from lonpmailmx01.citrite.net ([10.30.203.162]) by LONPIPO01.EU.CITRIX.COM with ESMTP/TLS/RC4-MD5; 29 May 2013 07:43:49 +0000 Received: from [127.0.0.1] (10.80.16.67) by smtprelay.citrix.com (10.30.203.162) with Microsoft SMTP Server id 8.3.298.1; Wed, 29 May 2013 08:43:48 +0100 Message-ID: <1369813427.22605.38.camel@dagon.hellion.org.uk> From: Ian Campbell To: Keir Fraser Date: Wed, 29 May 2013 08:43:47 +0100 In-Reply-To: References: Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Cc: George Dunlap , Fabio Fantoni , Ian Jackson , 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org On Tue, 2013-05-28 at 19:09 +0100, 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. Are you proposing we do this for 4.3? I'm not sure how big that change would be in terms of impact (just that one instruction, any 16 byte operand?). Of course even if we did this for 4.3 we don't know what the next issue will be with QXL. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel