From: Avi Kivity <avi@qumranet.com>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net
Subject: Re: [KVM][PATCH] smp_processor_id() and sleeping functions used in invalid context
Date: Sun, 31 Dec 2006 19:50:09 +0200 [thread overview]
Message-ID: <4597F851.8060800@qumranet.com> (raw)
In-Reply-To: <20061231170147.GA8695@dreamland.darkstar.lan>
Luca Tettamanti wrote:
> Hello,
> I'm testing KVM on a Core2 CPU. I'm running kernel 2.6.20-git (pulled
> few hours ago), configured with SMP and PREEMPT.
>
> I'm hitting 2 different warnings:
> BUG: using smp_processor_id() in preemptible [00000001] code: kvm/7726
> caller is vmx_create_vcpu+0x9/0x2f [kvm_intel]
>
>
[...]
> vmx_create_vcpu calls alloc_vmcs which uses smp_processor_id() in
> preemptible context and pass the result to alloc_vmcs_cpu(); at a later
> point the function may be running on a different CPU (hence the result
> of cpu_to_node may be meaningless).
>
> Second one:
> BUG: sleeping function called from invalid context at
> /home/kronos/src/linux-2.6.git/mm/slab.c:3034
> in_atomic():1, irqs_disabled():0
> 1 lock held by kvm/12706:
> #0: (&vcpu->mutex){--..}, at: [<f1b68d02>] kvm_dev_ioctl+0x113/0xf97
> [kvm]
> [<b015c32a>] kmem_cache_alloc+0x1b/0x6f
>
[...]
There are patches for both (I think) flying around. They should land in
Linus' tree in a few days.
Thanks,
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Luca Tettamanti <kronos.it-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [KVM][PATCH] smp_processor_id() and sleeping functions used in invalid context
Date: Sun, 31 Dec 2006 19:50:09 +0200 [thread overview]
Message-ID: <4597F851.8060800@qumranet.com> (raw)
In-Reply-To: <20061231170147.GA8695-sTXFmx6KbOnUXq0IF5SVAZ4oGUkBHcCu@public.gmane.org>
Luca Tettamanti wrote:
> Hello,
> I'm testing KVM on a Core2 CPU. I'm running kernel 2.6.20-git (pulled
> few hours ago), configured with SMP and PREEMPT.
>
> I'm hitting 2 different warnings:
> BUG: using smp_processor_id() in preemptible [00000001] code: kvm/7726
> caller is vmx_create_vcpu+0x9/0x2f [kvm_intel]
>
>
[...]
> vmx_create_vcpu calls alloc_vmcs which uses smp_processor_id() in
> preemptible context and pass the result to alloc_vmcs_cpu(); at a later
> point the function may be running on a different CPU (hence the result
> of cpu_to_node may be meaningless).
>
> Second one:
> BUG: sleeping function called from invalid context at
> /home/kronos/src/linux-2.6.git/mm/slab.c:3034
> in_atomic():1, irqs_disabled():0
> 1 lock held by kvm/12706:
> #0: (&vcpu->mutex){--..}, at: [<f1b68d02>] kvm_dev_ioctl+0x113/0xf97
> [kvm]
> [<b015c32a>] kmem_cache_alloc+0x1b/0x6f
>
[...]
There are patches for both (I think) flying around. They should land in
Linus' tree in a few days.
Thanks,
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-12-31 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 17:01 [KVM][PATCH] smp_processor_id() and sleeping functions used in invalid context Luca Tettamanti
2006-12-31 17:01 ` Luca Tettamanti
2006-12-31 17:50 ` Avi Kivity [this message]
2006-12-31 17:50 ` Avi Kivity
2006-12-31 17:58 ` Luca
2006-12-31 17:58 ` Luca
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=4597F851.8060800@qumranet.com \
--to=avi@qumranet.com \
--cc=kronos.it@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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.