From: Chris Friesen <cfriesen@nortel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ingo Oeser <ioe-lkml@axxeo.de>, linux-kernel@vger.kernel.org
Subject: Re: [rfc] [patch] consolidate/clean up spinlock.h files
Date: Thu, 02 Jun 2005 10:34:58 -0600 [thread overview]
Message-ID: <429F3532.80907@nortel.com> (raw)
In-Reply-To: <20050602161633.GA12616@elte.hu>
Ingo Molnar wrote:
> the real call site info comes from dump_stack(). Maybe i should remove
> the __FILE__,__LINE__ info altogether. (albeit a bit redundancy wont
> hurt) I dont think we want to pass in __FILE__,__LINE__ all the way from
> the main APIs.
Couldn't you make it a macro and hide the complexity? Or is it just a
performance issue due to register starvation?
Chris
next prev parent reply other threads:[~2005-06-02 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 14:40 [rfc] [patch] consolidate/clean up spinlock.h files Ingo Molnar
2005-06-02 15:49 ` Ingo Oeser
2005-06-02 16:16 ` Ingo Molnar
2005-06-02 16:30 ` Ingo Oeser
2005-06-02 16:34 ` Chris Friesen [this message]
2005-06-02 19:34 ` Zwane Mwaikambo
2005-06-02 17:26 ` Andi Kleen
2005-06-02 19:16 ` Roman Zippel
2005-06-03 5:16 ` Ingo Molnar
2005-06-03 11:56 ` Roman Zippel
2005-06-02 19:59 ` Zwane Mwaikambo
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=429F3532.80907@nortel.com \
--to=cfriesen@nortel.com \
--cc=ioe-lkml@axxeo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.