From: Jan Kiszka <jan.kiszka@web.de>
To: Anup Patel <anup@brainfault.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
kvmarm <kvmarm@lists.cs.columbia.edu>, kvm <kvm@vger.kernel.org>
Subject: Re: vexpress: Framebuffer broken with KVM enabled
Date: Mon, 16 Feb 2015 10:26:07 +0100 [thread overview]
Message-ID: <54E1B7AF.5020905@web.de> (raw)
In-Reply-To: <CAAhSdy3mNAm6Jt=s3Nt_fy_z=mMf3kG3DqYW3jROTo-ztUGzkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On 2015-02-16 10:20, Anup Patel wrote:
> On Mon, Feb 16, 2015 at 2:43 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Hi,
>>
>> next issue related to KVM/QEMU on the TK1: The guest image I'm running
>> gives proper framebuffer output when in emulation mode. Once KVM is
>> enabled, the screen is - at best - only initially updated. Sometimes I
>> see the famous tux images and a bit of the console texts, but usually it
>> stays black. Explanations?
>
> The QEMU accesses Guest Video RAM (or any portion of Guest RAM) as
> cacheable user space memory. The Guest Kernel might access Guest Video
> RAM as non-cacheable to maintain coherency with video device. If this is
> the case then all updates by Guest kernel to Guest Video RAM will not
> be visible to QEMU.
On x86, we manage such RAM as coalesced MMIO region, sync'ing it
periodically or on specific register accesses into the video card model.
I suppose there is nothing like this for the pl111 yet, right?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: Anup Patel <anup@brainfault.org>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
kvmarm <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] vexpress: Framebuffer broken with KVM enabled
Date: Mon, 16 Feb 2015 10:26:07 +0100 [thread overview]
Message-ID: <54E1B7AF.5020905@web.de> (raw)
In-Reply-To: <CAAhSdy3mNAm6Jt=s3Nt_fy_z=mMf3kG3DqYW3jROTo-ztUGzkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On 2015-02-16 10:20, Anup Patel wrote:
> On Mon, Feb 16, 2015 at 2:43 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> Hi,
>>
>> next issue related to KVM/QEMU on the TK1: The guest image I'm running
>> gives proper framebuffer output when in emulation mode. Once KVM is
>> enabled, the screen is - at best - only initially updated. Sometimes I
>> see the famous tux images and a bit of the console texts, but usually it
>> stays black. Explanations?
>
> The QEMU accesses Guest Video RAM (or any portion of Guest RAM) as
> cacheable user space memory. The Guest Kernel might access Guest Video
> RAM as non-cacheable to maintain coherency with video device. If this is
> the case then all updates by Guest kernel to Guest Video RAM will not
> be visible to QEMU.
On x86, we manage such RAM as coalesced MMIO region, sync'ing it
periodically or on specific register accesses into the video card model.
I suppose there is nothing like this for the pl111 yet, right?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-02-16 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 9:13 vexpress: Framebuffer broken with KVM enabled Jan Kiszka
2015-02-16 9:13 ` [Qemu-devel] " Jan Kiszka
2015-02-16 9:20 ` Anup Patel
2015-02-16 9:20 ` [Qemu-devel] " Anup Patel
2015-02-16 9:26 ` Jan Kiszka [this message]
2015-02-16 9:26 ` Jan Kiszka
2015-02-16 9:34 ` Alexander Spyridakis
2015-02-16 9:34 ` [Qemu-devel] " Alexander Spyridakis
2015-02-16 10:04 ` Jan Kiszka
2015-02-16 10:04 ` [Qemu-devel] " Jan Kiszka
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=54E1B7AF.5020905@web.de \
--to=jan.kiszka@web.de \
--cc=anup@brainfault.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--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.