From: Avi Kivity <avi@qumranet.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: kvm-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] kvm: fix GFP_KERNEL alloc in atomic section bug
Date: Thu, 28 Dec 2006 14:44:10 +0200 [thread overview]
Message-ID: <4593BC1A.9080503@qumranet.com> (raw)
In-Reply-To: <20061228123219.GA27387@elte.hu>
Ingo Molnar wrote:
> Subject: [patch] kvm: fix GFP_KERNEL alloc in atomic section bug
> From: Ingo Molnar <mingo@elte.hu>
>
> KVM does kmalloc() in an atomic section while having preemption disabled
> via vcpu_load(). Fix this by moving the ->*_msr setup from the
> vcpu_setup method to the vcpu_create method.
>
> (This is also a small speedup for setting up a vcpu, which can in theory
> be more frequent than the vcpu_create method).
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2006-12-28 12:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 9:45 [PATCH 0/5] KVM: Updates Avi Kivity
2006-12-21 9:45 ` Avi Kivity
2006-12-21 9:46 ` [PATCH 1/5] KVM: Use more traditional error handling in kvm_mmu_init() Avi Kivity
2006-12-21 9:47 ` [PATCH 2/5] KVM: Do not export unsupported msrs to userspace Avi Kivity
2006-12-21 9:47 ` Avi Kivity
2006-12-21 9:48 ` [PATCH 3/5] KVM: Force real-mode cs limit to 64K Avi Kivity
2006-12-21 9:48 ` Avi Kivity
2006-12-21 9:49 ` [PATCH 4/5] KVM: Handle p5 mce msrs Avi Kivity
2006-12-21 9:49 ` Avi Kivity
2006-12-21 9:50 ` [PATCH 5/5] KVM: API versioning Avi Kivity
2006-12-21 9:50 ` Avi Kivity
2006-12-28 12:32 ` [patch] kvm: fix GFP_KERNEL alloc in atomic section bug Ingo Molnar
2006-12-28 12:32 ` Ingo Molnar
2006-12-28 12:44 ` 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=4593BC1A.9080503@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.