From: Avi Kivity <avi@redhat.com>
To: Andrew Theurer <habanero@linux.vnet.ibm.com>
Cc: Tejun Heo <tj@kernel.org>,
kvm@vger.kernel.org, Linux-kernel@vger.kernel.org
Subject: Re: kernel bug in kvm_intel
Date: Sun, 29 Nov 2009 16:46:50 +0200 [thread overview]
Message-ID: <4B12895A.2010706@redhat.com> (raw)
In-Reply-To: <4B0DDB5D.9030202@linux.vnet.ibm.com>
On 11/26/2009 03:35 AM, Andrew Theurer wrote:
> I just tried testing tip of kvm.git, but unfortunately I think I might
> be hitting a different problem, where processes run 100% in kernel
> mode. In my case, cpus 9 and 13 were stuck, running qemu processes.
> A stack backtrace for both cpus are below. FWIW, kernel.org
> 2.6.32-rc7 does not have this problem, or the original problem.
I just posted a patch fixing this, titled "[PATCH tip:x86/entry] core:
fix user return notifier on fork()".
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-29 14:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 20:04 kernel bug in kvm_intel Andrew Theurer
2009-10-11 5:19 ` Avi Kivity
2009-10-12 18:42 ` Andrew Theurer
2009-10-13 6:50 ` Avi Kivity
2009-10-13 14:04 ` Andrew Theurer
2009-10-14 17:10 ` Avi Kivity
2009-10-15 20:18 ` Andrew Theurer
2009-10-30 18:07 ` Andrew Theurer
2009-10-31 15:47 ` Avi Kivity
2009-10-31 16:25 ` Andrew Theurer
2009-10-31 16:32 ` Avi Kivity
2009-10-31 16:38 ` Avi Kivity
2009-11-01 10:00 ` Tejun Heo
2009-11-01 10:20 ` Avi Kivity
2009-11-01 10:45 ` Tejun Heo
2009-11-01 11:31 ` Avi Kivity
2009-11-18 9:26 ` Tejun Heo
2009-11-26 1:35 ` Andrew Theurer
2009-11-26 1:41 ` Tejun Heo
2009-11-26 10:31 ` Avi Kivity
2009-11-26 13:47 ` Andrew Theurer
2009-11-29 14:46 ` Avi Kivity [this message]
2009-11-30 16:27 ` Andrew Theurer
2009-10-13 14:31 ` Marcelo Tosatti
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=4B12895A.2010706@redhat.com \
--to=avi@redhat.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=habanero@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=tj@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.