From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53396) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W644x-0003Na-Eo for qemu-devel@nongnu.org; Wed, 22 Jan 2014 15:07:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W644r-0003sN-CX for qemu-devel@nongnu.org; Wed, 22 Jan 2014 15:07:15 -0500 Received: from mail-lb0-f178.google.com ([209.85.217.178]:46540) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W644r-0003rx-69 for qemu-devel@nongnu.org; Wed, 22 Jan 2014 15:07:09 -0500 Received: by mail-lb0-f178.google.com with SMTP id u14so707125lbd.23 for ; Wed, 22 Jan 2014 12:07:08 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <52E0016D.801@redhat.com> From: Peter Maydell Date: Wed, 22 Jan 2014 20:06:47 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] Intel AVX instructions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Xin Tong Cc: Paolo Bonzini , QEMU Developers , Stefan Hajnoczi On 22 January 2014 19:35, Xin Tong wrote: > It seems that BOCHS have AVX instructions support in interpreter. I am > thinking an easy/reliable way to do this would be generate helper > calls to emulate every AVX instruction and follow how BOCHS emulates > them. Then depending on the expected frequency and difficulties, one > can decide whether to move some of the instructions into TCG JITted > code ? I would recommend implementing them from scratch for QEMU based on the Intel architecture documentation. That will produce much nicer results. > Also, it would be desirable to use the MMX/SSE structures and > functions that already exist in QEMU target-i386/translate.c It would certainly be advisable to use them where there is commonality. thanks -- PMM