mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@lst.de>
Cc: Frederic Weisbecker <fweisbec@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: types for storing instruction pointers
Date: Sun, 7 Jun 2009 15:25:16 +0200	[thread overview]
Message-ID: <20090607132516.GB12088@elte.hu> (raw)
In-Reply-To: <20090604131400.GA31596@lst.de>


* Christoph Hellwig <hch@lst.de> wrote:

> Currently the _THIS_IP_ and _RET_IP_ macros aded for lockdep but 
> now available from kernel.org case the instruction pointer to an 
> unsigned long.  But the %pf/%pF format for printing them want a 
> pointer of some sort.  That's a pretty nasty situation for tracers 
> - can we standardize on one type for it?

Yes but what's the practical problem exactly? Could you cite an 
example?

Thanks,

	Ingo

  reply	other threads:[~2009-06-07 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 13:14 Christoph Hellwig
2009-06-07 13:25 ` Ingo Molnar [this message]
2009-06-08 13:51   ` Christoph Hellwig
2009-06-08 14:12     ` 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=20090607132516.GB12088@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®