From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Marcelo Tosatti" <marcelo@kvack.org>
Cc: "Jiri Kosina" <jkosina@suse.cz>, "Avi Kivity" <avi@qumranet.com>,
linux-kernel@vger.kernel.org
Subject: Re: Qemu & KVM bug
Date: Wed, 13 Feb 2008 17:38:06 +0100 [thread overview]
Message-ID: <c4e36d110802130838r88c6151kcc058f1f0806ee29@mail.gmail.com> (raw)
In-Reply-To: <20080213160905.GA8559@dmt>
2008/2/13, Marcelo Tosatti <marcelo@kvack.org>:
> On Wed, Feb 13, 2008 at 04:24:53PM +0100, Jiri Kosina wrote:
> > On Wed, 13 Feb 2008, Zdenek Kabelac wrote:
> >
> > > I get this bug in my log whenever I start qemu-kvm - I do not use kqemu
> > > module - so it's with plain kernel modules. If more details are needed -
> > > just ask. (Cpu; C2D)
> > > BUG: sleeping function called from invalid context at kernel/rwsem.c:48
> > > in_atomic():1, irqs_disabled():0
> > > INFO: lockdep is turned off.
> > > Pid: 26600, comm: qemu-kvm Not tainted 2.6.25-rc1 #29
> >
> > This has been obviously caused by Marcelo's (added to CC) commit
> > 10589a4699b, which added down_write(mmap_sem) to alloc_apic_access_page(),
> > which is called with preempt disabled from vmx_create_vcpu().
>
> alloc_apic_access_page() called mutex_lock, so the warning would trigger
> before that change.
>
> I think it's fine to allocate the APIC page after put_cpu(), since no vcpu
> state is required.
>
> Avi?
>
>
> --- linux-2.6.orig/arch/x86/kvm/vmx.c
> +++ linux-2.6/arch/x86/kvm/vmx.c
> @@ -1601,9 +1601,6 @@ static int vmx_vcpu_setup(struct vcpu_vm
Hi
I've checked the patch myself - and looks like there is no BUG message
now - nice
thanks.
Zdenek
next prev parent reply other threads:[~2008-02-13 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 14:38 Zdenek Kabelac
2008-02-13 15:24 ` Jiri Kosina
2008-02-13 16:09 ` Marcelo Tosatti
2008-02-13 16:38 ` Zdenek Kabelac [this message]
2008-02-13 16:57 ` Avi Kivity
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=c4e36d110802130838r88c6151kcc058f1f0806ee29@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=avi@qumranet.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.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
Powered by JetHome