From: Avi Kivity <avi@redhat.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] race between kvm-kmod-3.0 and kvm-kmod-3.3 // was: race condition in qemu-kvm-1.0.1
Date: Tue, 03 Jul 2012 16:13:04 +0300 [thread overview]
Message-ID: <4FF2EFE0.2090400@redhat.com> (raw)
In-Reply-To: <4FF2ED2A.7080300@dlhnet.de>
On 07/03/2012 04:01 PM, Peter Lieven wrote:
> Further output from my testing.
>
> Working:
> Linux 2.6.38 with included kvm module
> Linux 3.0.0 with included kvm module
>
> Not-Working:
> Linux 3.2.0 with included kvm module
> Linux 2.6.28 with kvm-kmod 3.4
> Linux 3.0.0 with kvm-kmod 3.4
> Linux 3.2.0 with kvm-kmod 3.4
>
> I can trigger the race with any of qemu-kvm 0.12.5, 1.0 or 1.0.1.
> It might be that the code was introduced somewhere between 3.0.0
> and 3.2.0 in the kvm kernel module and that the flaw is not
> in qemu-kvm.
>
> Any hints?
>
A bisect could tell us where the problem is.
To avoid bisecting all of linux, try
git bisect v3.2 v3.0 virt/kvm arch/x86/kvm
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-07-03 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FEB2945.1030607@dlhnet.de>
[not found] ` <4FEB3AC6.6010206@web.de>
[not found] ` <4FEC1FC9.7050103@dlhnet.de>
[not found] ` <4FEC2210.1030005@siemens.com>
[not found] ` <4FEC2475.4030202@dlhnet.de>
[not found] ` <4FEC2626.90402@dlhnet.de>
2012-07-02 15:05 ` [Qemu-devel] race between kvm-kmod-3.0 and kvm-kmod-3.3 // was: race condition in qemu-kvm-1.0.1 Avi Kivity
2012-07-02 15:57 ` Peter Lieven
2012-07-03 13:01 ` Peter Lieven
2012-07-03 13:13 ` Avi Kivity [this message]
2012-07-03 13:15 ` Peter Lieven
2012-07-03 13:25 ` Avi Kivity
2012-07-04 14:57 ` Peter Lieven
2012-07-04 23:12 ` Peter Lieven
2012-07-05 6:48 ` Xiao Guangrong
2012-07-05 8:51 ` Xiao Guangrong
2012-07-05 12:42 ` Peter Lieven
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=4FF2EFE0.2090400@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlhnet.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).