From: Joel Becker <Joel.Becker@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Jody Belka <lists-lkml@pimb.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Ian Campbell <ijc@hellion.org.uk>,
"H. Peter Anvin" <hpa@zytor.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andi Kleen <andi@firstfloor.org>,
Mika Penttila <mika.penttila@kolumbus.fi>
Subject: Re: 2.6.25-rc1 xen pvops regression
Date: Sat, 16 Feb 2008 22:39:04 -0800 [thread overview]
Message-ID: <20080217063904.GE26206@mail.oracle.com> (raw)
In-Reply-To: <47B6CD0F.4020202@goop.org>
On Sat, Feb 16, 2008 at 10:46:23PM +1100, Jeremy Fitzhardinge wrote:
>>> What does this EIP correspond to in your kernel? Also:
>>>
>>> c01687f0 c0417ab6 c040288f c040299a c0403270
>>>
>>> (as guesses of potential callers to try and work out a stack trace).
>>>
>>
> (My usual technique is use "gdb vmlinux" and "x/i 0x...." to do the
> lookup.)
Ok, my objdump didn't do a good job. With gdb I get:
0xc04040bd <xen_set_pte_at+185>: mov %edi,(%eax)
0xc01687f0: Cannot access memory at address 0xc01687f0
0xc0417ab6 <__set_fixmap+326>: pop %ecx
0xc040288f <xen_alloc_ptpage+41>: lock btsl $0x8,(%eax)
0xc040299a <xen_load_idt+74>: lock incb 0xc0766148
0xc0403270 <xen_set_pte_atomic+26>: lock cmpxchg8b (%edi)
Joel
--
Life's Little Instruction Book #139
"Never deprive someone of hope; it might be all they have."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2008-02-17 6:40 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 23:54 2.6.25-rc1 xen pvops regression Jody Belka
2008-02-13 11:59 ` Jeremy Fitzhardinge
2008-02-13 12:13 ` Jody Belka
2008-02-13 12:23 ` Ingo Molnar
2008-02-14 2:27 ` Joel Becker
2008-02-14 7:50 ` Jeremy Fitzhardinge
2008-02-15 20:23 ` Joel Becker
2008-02-16 2:44 ` Jeremy Fitzhardinge
2008-02-16 8:54 ` Joel Becker
2008-02-16 11:46 ` Jeremy Fitzhardinge
2008-02-17 6:29 ` Joel Becker
2008-02-17 12:09 ` Jeremy Fitzhardinge
2008-02-17 6:39 ` Joel Becker [this message]
2008-02-17 18:49 ` Ian Campbell
2008-02-18 10:40 ` Joel Becker
2008-02-19 21:50 ` Ian Campbell
2008-02-19 21:59 ` Ian Campbell
2008-02-20 7:43 ` H. Peter Anvin
2008-02-20 8:51 ` Ian Campbell
2008-02-20 21:42 ` Joel Becker
2008-02-20 22:30 ` Ian Campbell
2008-02-20 21:58 ` Jeremy Fitzhardinge
2008-02-20 22:29 ` Ian Campbell
2008-02-21 21:16 ` Jeremy Fitzhardinge
2008-02-21 21:21 ` H. Peter Anvin
2008-02-21 21:37 ` Jeremy Fitzhardinge
2008-02-21 21:44 ` H. Peter Anvin
2008-02-21 22:12 ` Ian Campbell
2008-02-21 22:23 ` H. Peter Anvin
2008-02-21 22:49 ` Jeremy Fitzhardinge
2008-02-21 22:58 ` H. Peter Anvin
2008-02-22 7:25 ` Ian Campbell
2008-02-22 9:28 ` Alan Cox
2008-02-22 9:55 ` Andi Kleen
2008-02-22 10:00 ` Alan Cox
2008-02-22 10:15 ` Andi Kleen
2008-02-22 16:27 ` H. Peter Anvin
2008-02-22 19:25 ` Pavel Machek
2008-02-26 17:06 ` Mark McLoughlin
2008-02-26 20:05 ` Jeremy Fitzhardinge
2008-02-21 22:58 ` Joel Becker
2008-02-21 22:04 ` Eric W. Biederman
2008-02-21 23:14 ` Jeremy Fitzhardinge
2008-02-21 23:26 ` H. Peter Anvin
2008-02-21 23:46 ` Jeremy Fitzhardinge
2008-02-21 23:57 ` H. Peter Anvin
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=20080217063904.GE26206@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=andi@firstfloor.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=ijc@hellion.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists-lkml@pimb.org \
--cc=mika.penttila@kolumbus.fi \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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