From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alexander Graf <agraf-l3A5Bk7waGM@public.gmane.org>
Cc: kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm list <kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] KVM: PPC: Destory timer on vcpu destruction
Date: Wed, 24 Feb 2010 12:22:04 +0200 [thread overview]
Message-ID: <4B84FDCC.3050703@redhat.com> (raw)
In-Reply-To: <1266853934-31883-1-git-send-email-agraf-l3A5Bk7waGM@public.gmane.org>
On 02/22/2010 05:52 PM, Alexander Graf wrote:
> When we destory a vcpu, we should also make sure to kill all pending
> timers that could still be up. When not doing this, hrtimers might
> dereference null pointers trying to call our code.
>
> This patch fixes spontanious kernel panics seen after closing VMs.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-02-24 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 15:52 [PATCH] KVM: PPC: Destory timer on vcpu destruction Alexander Graf
[not found] ` <1266853934-31883-1-git-send-email-agraf-l3A5Bk7waGM@public.gmane.org>
2010-02-24 10:22 ` Avi Kivity [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=4B84FDCC.3050703@redhat.com \
--to=avi-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=agraf-l3A5Bk7waGM@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.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