From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Michael S. Tsirkin" <mst@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: Mon, 25 Oct 2010 13:50:40 +0200 [thread overview]
Message-ID: <4CC56F10.8040803@redhat.com> (raw)
In-Reply-To: <4CC56CC6.4020703@siemens.com>
On 10/25/2010 01:40 PM, Jan Kiszka wrote:
> >
> > Excellent catch, I stared at this code for a while and didn't see the
> > bug. Patch applied.
> >
>
> BTW, while this was an annoying one for graphic emulation, wasn't it
> potentially lethal for live migration?
Deadly. Yes autofs passed it happily.
We need a unit test that bangs on pages and the bitmap with tighter timing.
> The issue looks like is was introduced with the switch to SRCU, so every
> kernel since 2.6.34 should be affected, correct?
Yes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-10-25 11:51 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
2010-10-25 9:32 ` Avi Kivity
2010-10-25 11:40 ` Jan Kiszka
2010-10-25 11:50 ` Avi Kivity [this message]
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=4CC56F10.8040803@redhat.com \
--to=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 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.