From xen-devel-bounces@lists.xen.org Wed Sep 18 15:14:48 2013 Received: (at maildrop) by bugs.xenproject.org; 18 Sep 2013 14:14:48 +0000 Received: from lists.xen.org ([50.57.142.19]) by bugs.xenproject.org with esmtp (Exim 4.80) (envelope-from ) id 1VMIWm-0000mp-Dv for xen-devel-maildrop-Eithu9ie@bugs.xenproject.org; Wed, 18 Sep 2013 15:14:48 +0100 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VMIUC-0000Kp-52; Wed, 18 Sep 2013 14:12:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VMIUB-0000Kh-2X for xen-devel@lists.xenproject.org; Wed, 18 Sep 2013 14:12:07 +0000 Received: from [85.158.143.35:6272] by server-2.bemta-4.messagelabs.com id E5/8C-26052-6B4B9325; Wed, 18 Sep 2013 14:12:06 +0000 X-Env-Sender: fabio.fantoni@m2r.biz X-Msg-Ref: server-14.tower-21.messagelabs.com!1379513525!223030!1 X-Originating-IP: [209.85.214.43] X-SpamReason: No, hits=2.2 required=7.0 tests=BIZ_TLD,BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.12; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24242 invoked from network); 18 Sep 2013 14:12:05 -0000 Received: from mail-bk0-f43.google.com (HELO mail-bk0-f43.google.com) (209.85.214.43) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2013 14:12:05 -0000 Received: by mail-bk0-f43.google.com with SMTP id mz13so2907555bkb.30 for ; Wed, 18 Sep 2013 07:12:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VnkvGHFGYZHH5OJEuqxYy8HusPQfCUWSVqpaBdOEa/k=; b=auVZHatIbluun6s5aaay+3dzeN5l2cnDuweKcPdPyPmJ039y64QoVJMaPEnWPR8QuL pnCMRrwoUNuWhfUwYkfq6N+LQ+qxAI9mrLACbE+1LfjCaSQXborqY6NBjFLEV8d8fuJk m8fQF+HXr4YqdJYTJdi5UuxfPWHj4jVKJ8zFiqi5tytvkmSCJJMa8Eu0v3ABQ57ueMik hx9T473siGNJBXw1kVNEabQ8RpU6IYgTfvsZaj6dq0o4wZI5iinrpNWhHER7uFza5SQK pLRiHc+V1jocZi5m2uio7gXVu4I4nbv/cAx1kfBDERHFCbV9mWgjCkjmvwt+VXhHVfPS ChSg== X-Gm-Message-State: ALoCoQlYtKOi2g1BQTtNnDtIf7yZc3RrBLOPmd8RM2Hk1EN62FEZ6ii71cAHsQrc53BOst9Ga/Q8 X-Received: by 10.204.226.135 with SMTP id iw7mr34822225bkb.4.1379513525109; Wed, 18 Sep 2013 07:12:05 -0700 (PDT) Received: from [192.168.1.34] (ip-73-126.sn2.eutelia.it. [83.211.73.126]) by mx.google.com with ESMTPSA id 14sm1004529bkl.17.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Sep 2013 07:12:04 -0700 (PDT) Message-ID: <5239B4B9.8000604@m2r.biz> Date: Wed, 18 Sep 2013 16:12:09 +0200 From: Fabio Fantoni User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Jan Beulich References: <52397B4C02000078000F43F7@nat28.tlf.novell.com> <52399CA2.6030701@m2r.biz> <5239BBBB02000078000F4565@nat28.tlf.novell.com> In-Reply-To: <5239BBBB02000078000F4565@nat28.tlf.novell.com> Cc: George Dunlap , Andrew Cooper , Keir Fraser , xen-devel 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: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org Il 18/09/2013 14:42, Jan Beulich ha scritto: >>>> On 18.09.13 at 14:29, Fabio Fantoni wrote: >> Il 18/09/2013 10:07, Jan Beulich ha scritto: >>>>>> On 16.09.13 at 16:10, Fabio Fantoni wrote: >>>> Il 05/07/2013 18:59, George Dunlap ha scritto: >>>>> On Wed, May 29, 2013 at 11:25 PM, Andrew Cooper >>>>> wrote: >>>>>> On 29/05/2013 08:43, Ian Campbell wrote: >>>>>>> On Tue, 2013-05-28 at 19:09 +0100, Keir Fraser wrote: >>>>>>>> On 28/05/2013 17:51, "Ian Jackson" wro= te: >>>>>>>> >>>>>>>>> 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 re= lease, >>>>>>>>>> remove qxl support. >>>>>>>>>> >>>>>>>>>> This patch should be reverted as soon as the 4.4 development win= dow 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=E0=E8- >>>>>>>>>> >>>>>>>>>> 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 MM= IO 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 t= he ioreq >>>>>>>> structure that communicates to qemu. >>>>>>> Are you proposing we do this for 4.3? I'm not sure how big that cha= nge >>>>>>> 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 i= ssue >>>>>>> will be with QXL. >>>>>>> >>>>>>> Ian. >>>>>> Furthermore, AVX instruction emulation would require support for 32b= yte >>>>>> operands. I don't see the multi-cycle logic scaling sensibly. >>>>> Andrew, Keir, Jan, does any one of you fancy taking this on for 4.4? >>>> Is there someone that can add full support for SSE on hvm domUs? >>>> Thanks for any reply. >>> Mind giving the attached patch a try? >> Thanks, I have tested your patch but qxl seems to have the same problem >> (qemu crash on domU xorg start). >> I not see the MMIO error on logs, what must I do to see it or any >> similar debug information? >> Tell me if I must do other specific test or you need other details. > Without the patch you ought to have seen "bad mmio size ..." I was unable to see the MMIO error on each log files also before the patch. I don't know if I have enable sufficent debug to log them. And I have no ideaon how to do it. Is there another method to test effettive working of SSE >=3D2 istructions? Thanks for any reply. > warning in the hypervisor log. Those should be gone with the > patch I handed you. If you didn't see such warnings, then your > problem wasn't with the emulation of SSE instructions in the first > place. > As to qemu crashing - I'll have to defer to those knowing qemu > much better than I do. I merely wanted to provide the hypervisor > side change that I deemed necessary based on the information I > had (and I think that change ought to go in anyway, regardless > of whether it helps in your specific case). > > Jan > _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel