From: Avi Kivity <avi@redhat.com>
To: habanero@linux.vnet.ibm.com
Cc: kvm@vger.kernel.org
Subject: Re: kernel bug in kvm_intel
Date: Sat, 31 Oct 2009 17:47:48 +0200 [thread overview]
Message-ID: <4AEC5C24.9080506@redhat.com> (raw)
In-Reply-To: <1256926052.4883.203.camel@twinturbo.austin.ibm.com>
On 10/30/2009 08:07 PM, Andrew Theurer wrote:
>
> I have finally bisected and isolated this to the following commit:
>
> ada3fa15057205b7d3f727bba5cd26b5912e350f
> http://git.kernel.org/?p=virt/kvm/kvm.git;a=commit;h=ada3fa15057205b7d3f727bba5cd26b5912e350f
>
>> Merge branch 'for-linus' of git://git./linux/kernel/git/tj/percpu
>>
>> * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu: (46 commits)
>> powerpc64: convert to dynamic percpu allocator
>> sparc64: use embedding percpu first chunk allocator
>> percpu: kill lpage first chunk allocator
>> x86,percpu: use embedding for 64bit NUMA and page for 32bit NUMA
>> percpu: update embedding first chunk allocator to handle sparse units
>> percpu: use group information to allocate vmap areas sparsely
>> vmalloc: implement pcpu_get_vm_areas()
>> vmalloc: separate out insert_vmalloc_vm()
>> percpu: add chunk->base_addr
>> percpu: add pcpu_unit_offsets[]
>> percpu: introduce pcpu_alloc_info and pcpu_group_info
>> percpu: move pcpu_lpage_build_unit_map() and pcpul_lpage_dump_cfg() upward
>> percpu: add @align to pcpu_fc_alloc_fn_t
>> percpu: make @dyn_size mandatory for pcpu_setup_first_chunk()
>> percpu: drop @static_size from first chunk allocators
>> percpu: generalize first chunk allocator selection
>> percpu: build first chunk allocators selectively
>> percpu: rename 4k first chunk allocator to page
>> percpu: improve boot messages
>> percpu: fix pcpu_reclaim() locking
>>
> The previous commit (5579fd7e6aed8860ea0c8e3f11897493153b10ad) does not
> this problem. FYI, this problem only occurs when oprofile is active.
>
> Any idea what in this commit might be the issue?
>
>
5579 is not the preceding commit, it is the merged branch:
commit ada3fa15057205b7d3f727bba5cd26b5912e350f
Merge: 2f82af0 5579fd7
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue Sep 15 09:39:44 2009 -0700
Merge branch 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu
What happens with 2f82af0?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-10-31 15: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 [this message]
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
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=4AEC5C24.9080506@redhat.com \
--to=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).