From: Avi Kivity <avi@redhat.com>
To: michael@ellerman.id.au
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Avoid NULL dereference in kvm_apic_accept_pic_intr()
Date: Sun, 04 Mar 2012 12:14:30 +0200 [thread overview]
Message-ID: <4F534086.7040607@redhat.com> (raw)
In-Reply-To: <4F533B3A.40905@redhat.com>
On 03/04/2012 11:51 AM, Avi Kivity wrote:
> However kvm_arch_vcpu_init(), which creates the lapic, _is_ called
> without either the vcpu->mutex or kvm->lock held.
This is irrelevant, the important bit is when it becomes visible.
> Patch coming up.
I'll add explicit variables for irqchip_in_kernel. They'll be useful
for non-x86 as well.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-03-04 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 6:32 [PATCH] KVM: x86: Avoid NULL dereference in kvm_apic_accept_pic_intr() Michael Ellerman
2012-02-07 19:38 ` Marcelo Tosatti
2012-02-08 10:41 ` Michael Ellerman
2012-02-08 12:13 ` Michael Ellerman
2012-03-04 9:51 ` Avi Kivity
2012-03-04 10:14 ` 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=4F534086.7040607@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=mtosatti@redhat.com \
/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).