All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64 oprofile support for 2.6.0-test4
Date: Tue, 26 Aug 2003 20:58:46 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106193176908925@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106193081107734@msgid-missing>

>>>>> On Tue, 26 Aug 2003 16:42:27 -0400, Will Cohen <wcohen@redhat.com> said:

  Will> +	eip = instruction_pointer(regs);

eip?  How about calling it "ip", which is the register name and what's
used everywhere else in the ia64 tree.

  Will> +/*
  Will> + * We use the ia64_psr(regs)->ri to determine which of the three
  Will> + * instructions in bundle took the sample. The instructions in the
  Will> + * ia64 do not fall on nice four byte boundaries, so there is no point
  Will> + * in multiplying ia64_psr(regs)->ri by 4.
  Will> + */
  Will> +#define instruction_pointer(regs) ((regs)->cr_iip + ia64_psr(regs)->ri)

How are you going to get instruction-level precision with this?

Given this:

  Will> -	ip >>= prof_shift;

you'd have to use a prof_shift of 0, which is wasteful.  If you
multiply ri by 4, you can use a prof_shift of 2, reducing the
histogram size by a factor of 4 while still getting instruction-level
accuracy.

I can see why you don't want to do the multiply-by-four in
instruction_pointer(), but if that's what you want to avoid, I think
ia64_do_profile() should should do it so we can get the desired
effect.

	--david

  reply	other threads:[~2003-08-26 20:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 20:42 [PATCH] ia64 oprofile support for 2.6.0-test4 Will Cohen
2003-08-26 20:58 ` David Mosberger [this message]
2003-08-26 21:19 ` Will Cohen
2003-08-26 21:51 ` Will Cohen
2003-08-26 21:58 ` David Mosberger
2003-08-26 22:02 ` Will Cohen
2003-08-26 22:05 ` David Mosberger
2003-08-27 13:57 ` Will Cohen
2003-08-28 23:35 ` David Mosberger

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=marc-linux-ia64-106193176908925@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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 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.