From: Jan Kiszka <jan.kiszka@siemens.com>
To: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Frame buffer corruptions with KVM >= 2.6.36
Date: Mon, 18 Oct 2010 14:17:40 +0200 [thread overview]
Message-ID: <4CBC3AE4.2090107@siemens.com> (raw)
In-Reply-To: <4CBC3A1A.40307@oss.ntt.co.jp>
Am 18.10.2010 14:14, Takuya Yoshikawa wrote:
> (2010/10/15 15:41), Takuya Yoshikawa wrote:
>> (2010/10/14 21:38), Avi Kivity wrote:
>>> On 10/14/2010 02:36 PM, Jan Kiszka wrote:
>>>>>
>>>>>> and this commit just makes the
>>>>>> corruptions more likely. This may even be a QEMU issue in the cirrus/vga
>>>>>> model (both qemu-kvm and upstream show the effect).
>>>>>>
>>>>>
>>>>> What about -no-kvm?
>>>>
>>>> Just booted it (took ages), and the result was actually a completely
>>>> black screen. Kind of persistent corruption. This really looks like a
>>>> qemu issue now, maybe even a regression as I don't remember running into
>>>> such effects a while back.
>>>
>>> Worked fine for me (though yes it was slow - did tcg regress?).
>>>
>>
>> I reread my commit but could not find any reason to make this corruption
>> in kernel side.
>>
>> But at least, I want to make it clear whether my commit was just a magnifier
>> of this problem, I know that magnifier itself is bad, or not.
>>
>> Though I'm now trying some debugging but have not got a way to show
>> kvm_vm_ioctl_get_dirty_log() is 100% correct yet.
>>
>
> I tried some tests and found another issue.
>
> I opened a terminal in one workspace and did "find /" on it. Then I switched
> to another workspace. When I switched back to the first one, the display of
> "find /" result was frozen.
>
> I also replaced kvm_vm_ioctl_get_dirty_log() with the version before my patch was
> applied and got the same result.
>
> I don't know this is related to your report, but something seems wrong.
Besides corruptions, I'm getting those freezes from time to time as well
(fairly annoying now). Once that happened, (SDL) display updates can
only be achieved by pressing CTRL-ATL-1 (ie. switching qemu consoles).
Thanks for looking into this. I also think your patch is not guilty. But
we still need to understand the real issue.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-10-18 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 7:27 Frame buffer corruptions with KVM >= 2.6.36 Jan Kiszka
2010-10-14 12:04 ` Avi Kivity
2010-10-14 12:11 ` Avi Kivity
2010-10-14 12:13 ` Jan Kiszka
2010-10-14 12:10 ` Jan Kiszka
2010-10-14 12:13 ` Avi Kivity
2010-10-14 12:31 ` Avi Kivity
2010-10-14 12:36 ` Jan Kiszka
2010-10-14 12:38 ` Avi Kivity
2010-10-15 6:41 ` Takuya Yoshikawa
2010-10-18 12:14 ` Takuya Yoshikawa
2010-10-18 12:17 ` Jan Kiszka [this message]
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=4CBC3AE4.2090107@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox