On 09/04/2012 03:51 PM, Mathias Krause wrote:
On Tue, Sep 4, 2012 at 2:13 PM, Avi Kivity a...@redhat.com wrote:
On 09/04/2012 03:09 PM, Avi Kivity wrote:
On 08/30/2012 02:30 AM, Mathias Krause wrote:
As the the compiler ensures that the memory operand is always aligned
to a 16 byte memory
On 08/30/2012 02:30 AM, Mathias Krause wrote:
As the the compiler ensures that the memory operand is always aligned
to a 16 byte memory location,
I'm not sure it does. Is V4SI aligned? Do we use alignof() to
propagate the alignment to the vcpu allocation code?
use the aligned variant of
On 09/04/2012 03:09 PM, Avi Kivity wrote:
On 08/30/2012 02:30 AM, Mathias Krause wrote:
As the the compiler ensures that the memory operand is always aligned
to a 16 byte memory location,
I'm not sure it does. Is V4SI aligned? Do we use alignof() to
propagate the alignment to the vcpu
On Tue, Sep 4, 2012 at 2:13 PM, Avi Kivity a...@redhat.com wrote:
On 09/04/2012 03:09 PM, Avi Kivity wrote:
On 08/30/2012 02:30 AM, Mathias Krause wrote:
As the the compiler ensures that the memory operand is always aligned
to a 16 byte memory location,
I'm not sure it does. Is V4SI
As the the compiler ensures that the memory operand is always aligned
to a 16 byte memory location, use the aligned variant of MOVDQ for
read_sse_reg() and write_sse_reg().
Signed-off-by: Mathias Krause mini...@googlemail.com
---
arch/x86/kvm/emulate.c | 64
