From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>, Gleb Natapov <gleb@redhat.com>,
Sheng Yang <sheng@linux.intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] kvm: write protect memory after slot swap
Date: Tue, 26 Oct 2010 15:38:46 +0900 [thread overview]
Message-ID: <4CC67776.809@oss.ntt.co.jp> (raw)
In-Reply-To: <20101025120545.GA17337@redhat.com>
(2010/10/25 21:05), Michael S. Tsirkin wrote:
> On Mon, Oct 25, 2010 at 11:07:13AM +0200, Jan Kiszka wrote:
>> Cool, seems to be the key to the corruptions I've seen. Applying your
>> patch make them disappear.
>
> Yes, works for me as well.
>
I did some tests on my laptop:
- kvm.git + mst's patch
- qemu.git (upstream qemu)
and still got graphics curruption.
Corruption:
On usual Desktop environment, I opened two terminals on different
workspaces. Then as Jan did, I did "find /" loop on both of them.
During these heavy updates, I tried to switch between these
workspaces some times. Then, at some turn, some part of old
workspace's images like terminals and mouse cursor remained
in the new workspace.
I could refresh these by moving mouse over the problematic parts.
But without doing so, the images remained still.
Refresh is not working on virtual machines as I expect?
Thanks,
Takuya
next prev parent reply other threads:[~2010-10-26 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 1:21 [PATCH RFC] kvm: write protect memory after slot swap Michael S. Tsirkin
2010-10-25 7:27 ` Takuya Yoshikawa
2010-10-25 9:07 ` Jan Kiszka
2010-10-25 12:05 ` Michael S. Tsirkin
2010-10-26 6:38 ` Takuya Yoshikawa [this message]
2010-10-25 9:32 ` Avi Kivity
2010-10-25 11:40 ` Jan Kiszka
2010-10-25 11:50 ` Avi Kivity
2010-10-25 11:51 ` Avi Kivity
2010-11-24 19:16 ` Jan Kiszka
2010-11-25 9:18 ` Avi Kivity
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=4CC67776.809@oss.ntt.co.jp \
--to=yoshikawa.takuya@oss.ntt.co.jp \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox