kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Avi Kivity <avi@redhat.com>
Cc: Andrew Theurer <habanero@linux.vnet.ibm.com>, kvm@vger.kernel.org
Subject: Re: kernel bug in kvm_intel
Date: Sun, 01 Nov 2009 11:00:31 +0100	[thread overview]
Message-ID: <4AED5C3F.9050506@kernel.org> (raw)
In-Reply-To: <4AEC6821.7010801@redhat.com>

Hello,

Avi Kivity wrote:
> Only, that merge doesn't change virt/kvm or arch/x86/kvm.
> 
> Tejun, anything known bad about that merge?  ada3fa15 kills kvm.

Nothing rings a bell at the moment.  How does it kill kvm?  One big
difference caused by that merge is use of sparse areas near the top of
vmalloc area.  This caused vmalloc area shortage on sparc64 and
exposed paging code bug on ppc64 which caused the cpu to fault
repeatedly on the same address.  Maybe something similiar is happening
with kvm?

Thanks.

-- 
tejun

  reply	other threads:[~2009-11-01  9:59 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 [this message]
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
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=4AED5C3F.9050506@kernel.org \
    --to=tj@kernel.org \
    --cc=avi@redhat.com \
    --cc=habanero@linux.vnet.ibm.com \
    --cc=kvm@vger.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;
as well as URLs for NNTP newsgroup(s).