From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Matt Mackall <mpm@selenic.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jeremy Fitzhardinge <jeremy@xensource.com>
Subject: Re: [PATCH] Fix lguest w/ lockdep
Date: Thu, 28 Jun 2007 09:51:46 -0400 [thread overview]
Message-ID: <4683BCF2.2080502@goop.org> (raw)
In-Reply-To: <1183037519.6211.2.camel@localhost.localdomain>
Rusty Russell wrote:
> On Wed, 2007-06-27 at 19:14 -0500, Matt Mackall wrote:
>
>> lguest: unhandled trap 14 at 0xc01362f7 (0x0)
>> Dump of assembler code for function __lock_acquire:
>>
>
> Thanks for the bug report Matt! I wonder if other
> paravirt_disable_iospace users have the same issue...
>
I call it a little later (from arch_setup), and I think lockdep_init
will have already been called at that point. Hm, yes, it gets called at
the top of start_kernel.
J
prev parent reply other threads:[~2007-06-28 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070628001425.GR11115@waste.org>
2007-06-28 13:31 ` [PATCH] Fix lguest w/ lockdep Rusty Russell
2007-06-28 13:51 ` Jeremy Fitzhardinge [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=4683BCF2.2080502@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rusty@rustcorp.com.au \
/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