ay to know that they're from the same instruction. Any pointers?
Thanks,
AK
_
From: Richard Henderson [mailto:r...@twiddle.net]
To: ad...@khaleel.us
Cc: qemu-devel@nongnu.org, blauwir...@gmail.com
Sent: Fri, 02 Sep 2011 20:53:30 -0500
Subject: Re: [Qemu-devel] Single 64bit memory t
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 c
es are from the same instruction.
Thanks
AK
Re: [Qemu-devel] Single 64bit memory transaction instead of two 32bit me
_
From: Blue Swirl
Subject: Re: [Qemu-devel] Single 64bit memory transaction instead of
two 32bit memory transaction.
Da
On Mon, Nov 8, 2010 at 11:27 PM, Adnan Khaleel wrote:
> In the file exec.c:
>
> The memory Write/Read functions are declared as an array of 4 entries where
> the index values of 0,1,2 correspond to 8,16 and 32bit write and read
> functions respectively.
>
> CPUWriteMemoryFunc *io_mem_write[IO_MEM_
In the file exec.c:
The memory Write/Read functions are declared as an array of 4 entries where the
index values of 0,1,2 correspond to 8,16 and 32bit write and read functions
respectively.
CPUWriteMemoryFunc *io_mem_write[IO_MEM_NB_ENTRIES][4];
CPUReadMemoryFunc *io_mem_read[IO_MEM_NB_ENTRIES]
