From: "Andrew Chew" <AChew@nvidia.com>
To: "Ingo Molnar" <mingo@elte.hu>, "Andrew Morton" <akpm@osdl.org>
Cc: "Zwane Mwaikambo" <zwane@fsmlabs.com>,
<linux-kernel@vger.kernel.org>, <ak@suse.de>,
<wli@holomorphy.com>
Subject: RE: [PATCH] remove LOCK_SECTION from x86_64 spin_lock asm
Date: Wed, 15 Sep 2004 15:42:19 -0700 [thread overview]
Message-ID: <DBFABB80F7FD3143A911F9E6CFD477B03F96E2@hqemmail02.nvidia.com> (raw)
> > If you enable profiling and frame pointers, profile_pc() goes splat
> > dereferencing the `regs' argument when it decides that the
> pc refers
> > to a lock section. Ingo said `regs' had a value of 0x2, iirc.
> > Consider this a bug report ;)
I've been seeing this as well, although I'm pretty sure I have profiling
disabled. Are you sure it isn't the combination of SMP support and
frame pointers that causes this bug to occur? (It looks like
profile_pc() takes on a different implementation only if both CONFIG_SMP
and CONFIG_FRAME_POINTER is defined.)
next reply other threads:[~2004-09-15 22:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 22:42 Andrew Chew [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 16:01 Zwane Mwaikambo
2004-09-15 21:45 ` Andrew Morton
2004-09-15 17:55 ` Zwane Mwaikambo
2004-09-15 21:47 ` Ingo Molnar
2004-09-16 6:13 ` Andi Kleen
2004-09-16 6:27 ` Ingo Molnar
2004-09-16 6:44 ` Andi Kleen
2004-09-16 6:51 ` Ingo Molnar
2004-09-16 6:53 ` Andi Kleen
2004-09-16 6:58 ` Ingo Molnar
2004-09-16 7:09 ` Andi Kleen
2004-09-16 7:19 ` Ingo Molnar
2004-09-16 7:29 ` Andi Kleen
2004-09-16 7:44 ` Ingo Molnar
2004-09-16 7:53 ` Andi Kleen
2004-09-16 9:01 ` Andi Kleen
2004-09-16 12:44 ` Zwane Mwaikambo
2004-09-16 19:30 ` Ingo Molnar
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=DBFABB80F7FD3143A911F9E6CFD477B03F96E2@hqemmail02.nvidia.com \
--to=achew@nvidia.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wli@holomorphy.com \
--cc=zwane@fsmlabs.com \
/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
all inboxes | Powered by JetHome®