From: Zachary Amsden <zamsden@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: list_add corruption?
Date: Fri, 26 Feb 2010 10:13:38 -1000 [thread overview]
Message-ID: <4B882B72.9070406@redhat.com> (raw)
In-Reply-To: <4B87F76B.90608@redhat.com>
On 02/26/2010 06:31 AM, Zachary Amsden wrote:
> On 02/26/2010 01:18 AM, Avi Kivity wrote:
>> On 02/26/2010 06:57 AM, Zachary Amsden wrote:
>>> Anyone seeing list_add corruption running qemu-kvm with -smp 2 on
>>> Intel hardware?
>>>
>>> Debugging some local changes, which don't appear related. Running
>>> module from latest git on F12.
>>>
>>
>> Can you post a trace? Which list appears to be involved?
>>
>
> It's the per-cpu activated vcpu list, I'm guessing, which is why I
> only see it on Intel. I'm starting a bisect. I get a reliable system
> crash upon release of kvm instance. :(
>
> Hopefully it is just a bug in my patches :)
Alas, 'twere my botch.
prev parent reply other threads:[~2010-02-26 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 4:57 list_add corruption? Zachary Amsden
2010-02-26 11:18 ` Avi Kivity
2010-02-26 16:31 ` Zachary Amsden
2010-02-26 20:13 ` Zachary Amsden [this message]
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=4B882B72.9070406@redhat.com \
--to=zamsden@redhat.com \
--cc=avi@redhat.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