Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Tres Melton <tres@mindspring.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [Testers wanted] New glibc with profiling fixed.
Date: Tue, 26 Jul 2005 07:37:16 -0600	[thread overview]
Message-ID: <1122385036.10644.146.camel@thor.tres.org> (raw)
In-Reply-To: <20050726132402.GA32722@colo.lackof.org>

On Tue, 2005-07-26 at 07:24 -0600, Grant Grundler wrote:
> I can do that in August...thanks for pointing that out.
> I read the first parts of the report but don't recall seeing
> the kernel patch.

http://bugs.gentoo.org/show_bug.cgi?id=90090#c21
It is not a patch file just in the comment.

> Right. That's why jiffies exported to user space has to be "normalized"
> for whatever rate user space *thinks* the kernel is running.

I'm advocating a way for user space to *know* what the kernel is
running.  It is this thinking crap that is messing things up.

> > You spoke of another kernel
> > dev, could you ask him if he is opposed to exporting the correct value
> > in the elf header (or /proc) and to give a quick justification for his
> > response, pro or con.  Thanks.
> 
> He's already flown back to germany and it was just incidental that
> he was available. I'd rather not pester him about this since it
> seems to be a fairly well understood issue...at least to some people.

If you happen to speak to him again I would still like any extra info.
Don't bother him explicitly for this though.  The issue will be taken to
the LKML by the end of the week.

> thanks,
> grant
-- 
Tres

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-07-26 13:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22 12:56 [parisc-linux] [Testers wanted] New glibc with profiling fixed Tres Melton
2005-07-25  0:09 ` Grant Grundler
     [not found]   ` <1122272788.10644.71.camel@thor.tres.org>
2005-07-26 13:24     ` Grant Grundler
2005-07-26 13:37       ` Tres Melton [this message]
2005-07-26 14:18         ` Matthew Wilcox
2005-07-26 14:25           ` Randolph Chung
2005-07-26 17:01             ` Carlos O'Donell
2005-07-26 17:09               ` Matthew Wilcox
2005-07-26 18:08                 ` Carlos O'Donell
2005-07-26 15:26           ` Tres Melton
2005-07-26 17:16           ` Carlos O'Donell
     [not found] <no.id>
2004-01-07 21:14 ` John David Anglin
2004-01-07 21:14 ` John David Anglin
  -- strict thread matches above, loose matches on Subject: below --
2004-01-05 19:48 Carlos O'Donell
2004-01-05 19:48 ` Carlos O'Donell
2004-01-11  4:09   ` Grant Grundler
2004-01-11 20:43     ` Carlos O'Donell
2004-01-11 20:43     ` Carlos O'Donell
2004-01-12 16:38       ` Grant Grundler
2004-01-12 16:38       ` Grant Grundler
2004-01-13  5:42       ` Grant Grundler
2004-01-13  5:42       ` Grant Grundler
2004-01-13  8:46       ` Joel Soete
2004-01-13  8:46       ` Joel Soete
2004-01-11  4:09   ` Grant Grundler
2004-01-05 19:48 ` Carlos O'Donell
2004-01-05 20:45 ` Grant Grundler
2004-01-05 20:45 ` Grant Grundler
2004-01-05 22:00   ` Carlos O'Donell
2004-01-05 22:00   ` Carlos O'Donell
2004-01-07 21:04 ` John David Anglin
2004-01-07 21:04 ` John David Anglin
2004-01-05 19:48 Carlos O'Donell

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=1122385036.10644.146.camel@thor.tres.org \
    --to=tres@mindspring.com \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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