From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57077) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QzfQV-0007ou-Cm for qemu-devel@nongnu.org; Fri, 02 Sep 2011 21:53:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QzfQU-0004UQ-IV for qemu-devel@nongnu.org; Fri, 02 Sep 2011 21:53:43 -0400 Received: from mail-gw0-f45.google.com ([74.125.83.45]:41939) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QzfQU-0004UM-EJ for qemu-devel@nongnu.org; Fri, 02 Sep 2011 21:53:42 -0400 Received: by gwb19 with SMTP id 19so2308376gwb.4 for ; Fri, 02 Sep 2011 18:53:41 -0700 (PDT) Sender: Richard Henderson Message-ID: <4E61889A.9080707@twiddle.net> Date: Sat, 03 Sep 2011 07:23:30 +0530 From: Richard Henderson MIME-Version: 1.0 References: <20110901191655.5b42e714@shadowfax.no-ip.com> In-Reply-To: <20110901191655.5b42e714@shadowfax.no-ip.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Single 64bit memory transaction instead of two 32bit memory transaction List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: adnan@khaleel.us Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org On 09/02/2011 12:46 AM, Adnan Khaleel wrote: > Is there anyway we can prevent Qemu breaking up 64,128 and 256bit XMM or YMM instructions into smaller chunks and have them issue as a single transaction of the original width? Not yet. The new MemoryRegion API will allow this, but we need to convert all the devices first, then rip out the old API. It's a work in progress... r~