From: Alexander Graf <agraf@suse.de>
To: Andrew Jones <drjones@redhat.com>,
kvmarm@lists.cs.columbia.edu, qemu-devel@nongnu.org,
ard.biesheuvel@linaro.org, christoffer.dall@linaro.org,
marc.zyngier@arm.com, peter.maydell@linaro.org,
pbonzini@redhat.com
Cc: catalin.marinas@arm.com, lersek@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/3] KVM: Introduce KVM_MEM_UNCACHED
Date: Wed, 29 Apr 2015 11:03:10 +0200 [thread overview]
Message-ID: <55409E4E.3090905@suse.de> (raw)
In-Reply-To: <1426705833-2679-1-git-send-email-drjones@redhat.com>
On 18.03.15 20:10, Andrew Jones wrote:
> Introduce a new memory region flag, KVM_MEM_UNCACHED, which
> is needed by ARM. This flag informs KVM that the given memory
> region is typically mapped by the guest as uncached. KVM for
> ARM then maps that region as uncached for userspace as well,
> in order to keep coherency.
I finally managed to give this a spin and immediately ran into an
unaligned access trap:
[ 116.509976] Unhandled fault: alignment fault (0x92000061) at
0x000003ffb1300000
Program received signal SIGBUS, Bus error.
[Switching to Thread 0x3ffb317ecb0 (LWP 1956)]
0x000003ffb685ed68 in memset () from /lib64/libc.so.6
(gdb) bt
#0 0x000003ffb685ed68 in memset () from /lib64/libc.so.6
#1 0x000002aaaac013ec in memset (__len=<optimized out>, __ch=0,
__dest=<optimized out>) at /usr/include/bits/string3.h:90
#2 vbe_ioport_write_data (opaque=0x2aaabbd3600, addr=<optimized out>,
val=65) at /usr/src/debug/qemu-2.3.0-rc4/hw/display/vga.c:739
#3 0x000002aaaabe07dc in memory_region_write_accessor (mr=<optimized
out>, addr=<optimized out>, value=<optimized out>, size=<optimized out>,
shift=<optimized out>, mask=<optimized out>) at
/usr/src/debug/qemu-2.3.0-rc4/memory.c:430
[...]
So maybe forcing the guest to see VRAM as cached is the safer choice
after all?
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: Andrew Jones <drjones@redhat.com>,
kvmarm@lists.cs.columbia.edu, qemu-devel@nongnu.org,
ard.biesheuvel@linaro.org, christoffer.dall@linaro.org,
marc.zyngier@arm.com, peter.maydell@linaro.org,
pbonzini@redhat.com
Cc: catalin.marinas@arm.com, lersek@redhat.com, m.smarduch@samsung.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/3] KVM: Introduce KVM_MEM_UNCACHED
Date: Wed, 29 Apr 2015 11:03:10 +0200 [thread overview]
Message-ID: <55409E4E.3090905@suse.de> (raw)
In-Reply-To: <1426705833-2679-1-git-send-email-drjones@redhat.com>
On 18.03.15 20:10, Andrew Jones wrote:
> Introduce a new memory region flag, KVM_MEM_UNCACHED, which
> is needed by ARM. This flag informs KVM that the given memory
> region is typically mapped by the guest as uncached. KVM for
> ARM then maps that region as uncached for userspace as well,
> in order to keep coherency.
I finally managed to give this a spin and immediately ran into an
unaligned access trap:
[ 116.509976] Unhandled fault: alignment fault (0x92000061) at
0x000003ffb1300000
Program received signal SIGBUS, Bus error.
[Switching to Thread 0x3ffb317ecb0 (LWP 1956)]
0x000003ffb685ed68 in memset () from /lib64/libc.so.6
(gdb) bt
#0 0x000003ffb685ed68 in memset () from /lib64/libc.so.6
#1 0x000002aaaac013ec in memset (__len=<optimized out>, __ch=0,
__dest=<optimized out>) at /usr/include/bits/string3.h:90
#2 vbe_ioport_write_data (opaque=0x2aaabbd3600, addr=<optimized out>,
val=65) at /usr/src/debug/qemu-2.3.0-rc4/hw/display/vga.c:739
#3 0x000002aaaabe07dc in memory_region_write_accessor (mr=<optimized
out>, addr=<optimized out>, value=<optimized out>, size=<optimized out>,
shift=<optimized out>, mask=<optimized out>) at
/usr/src/debug/qemu-2.3.0-rc4/memory.c:430
[...]
So maybe forcing the guest to see VRAM as cached is the safer choice
after all?
Alex
next prev parent reply other threads:[~2015-04-29 8:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 19:08 the arm cache coherency cluster "v2" Andrew Jones
2015-03-18 19:08 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:10 ` [RFC PATCH 0/3] KVM: Introduce KVM_MEM_UNCACHED Andrew Jones
2015-03-18 19:10 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:10 ` [RFC PATCH 1/3] KVM: promote KVM_MEMSLOT_INCOHERENT to uapi Andrew Jones
2015-03-18 19:10 ` [Qemu-devel] " Andrew Jones
2015-04-20 15:26 ` Christoffer Dall
2015-04-20 15:26 ` [Qemu-devel] " Christoffer Dall
2015-03-18 19:10 ` [RFC PATCH 2/3] arm/arm64: KVM: decouple READONLY and UNCACHED Andrew Jones
2015-03-18 19:10 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:10 ` [RFC PATCH 3/3] arm/arm64: KVM: implement KVM_MEM_UNCACHED Andrew Jones
2015-03-18 19:10 ` [Qemu-devel] " Andrew Jones
2015-03-19 16:56 ` [RFC PATCH 0/3] KVM: Introduce KVM_MEM_UNCACHED Paolo Bonzini
2015-03-19 16:56 ` [Qemu-devel] " Paolo Bonzini
2015-03-19 17:24 ` Andrew Jones
2015-03-19 17:24 ` [Qemu-devel] " Andrew Jones
2015-04-29 9:03 ` Alexander Graf [this message]
2015-04-29 9:03 ` Alexander Graf
2015-04-29 9:19 ` Peter Maydell
2015-04-29 9:19 ` Peter Maydell
2015-04-29 11:19 ` Andrew Jones
2015-04-29 11:19 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:11 ` [RFC PATCH 0/4] support KVM_MEM_UNCACHED Andrew Jones
2015-03-18 19:11 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:11 ` [RFC PATCH 1/4] kvm-all: put kvm_mem_flags to more work Andrew Jones
2015-03-18 19:11 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:11 ` [RFC PATCH 2/4] HACK: linux header update Andrew Jones
2015-03-18 19:11 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:11 ` [RFC PATCH 3/4] memory: add uncached flag Andrew Jones
2015-03-18 19:11 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:11 ` [RFC PATCH 4/4] vga: flag vram as uncached Andrew Jones
2015-03-18 19:11 ` [Qemu-devel] " Andrew Jones
2015-03-18 19:18 ` the arm cache coherency cluster "v2" Andrew Jones
2015-03-18 19:18 ` [Qemu-devel] " Andrew Jones
2015-05-03 21:29 ` Alexander Graf
2015-05-03 21:29 ` [Qemu-devel] " Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55409E4E.3090905@suse.de \
--to=agraf@suse.de \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lersek@redhat.com \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.