All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Cohen <wcohen@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64 oprofile support for 2.6.0-test4
Date: Tue, 26 Aug 2003 22:02:58 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106193732314907@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106193081107734@msgid-missing>

David Mosberger wrote:
>>>>>>On Tue, 26 Aug 2003 17:19:14 -0400, Will Cohen <wcohen@redhat.com> said:
>>>>>
> 
>   Will> For OProfile it didn't make a difference, but for the
>   Will> histograms it is wasteful. I didn't think about the impact on
>   Will> the traditional histogram.
> 
> You can't just break existing data formats for absolutely no reason.
> 
>   Will> Do the histogram analysis tools currently handle
> 
> Yes.  For example, I use "readprofile -b" from time to time to get
> instruction-level histograms.
> 
>   Will> the fiction of bundle instruction 0 at address ending in 0,
>   Will> bundle instruction 1 ending in 4, and bundle instruction 2 in
>   Will> 8? GDB doesn't.
> 
> And encoding the slot number in bits 0 and 1 is somehow less
> fictitious? ;-)

They are equally fictitious. I just happen to pick the wrong one. I 
changed the patch to be compatible with the existing data format used 
for the kernel profiling.

-Will




  parent reply	other threads:[~2003-08-26 22:02 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
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 [this message]
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-106193732314907@msgid-missing \
    --to=wcohen@redhat.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.