From: Ralf Baechle <ralf@linux-mips.org>
To: Gary Smith <gary.smith@3phoenix.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Question About Timers for Performance Analysis on BCM1480/1250 Systems
Date: Thu, 21 Jun 2007 18:06:01 +0100 [thread overview]
Message-ID: <20070621170601.GD21938@linux-mips.org> (raw)
In-Reply-To: <005a01c7b28b$ed279120$8facaac0@3PiGAS>
On Tue, Jun 19, 2007 at 12:07:21PM -0400, Gary Smith wrote:
> The following message thread is present in the Linux-Mips archives regarding
> the use of gettimeofday on Broadcom MIPS systems.
> http://www.linux-mips.org/archives/linux-mips/2006-01/msg00144.html The
> message thread specifically addresses the Dual-core Broadcom 1250 system,
> and the kernel version mentioned in the message thread is 2.6.12. I looked
> at the files mentioned in the message thread in the 2.6.17 kernel, and the
> changes suggested for arch/mips/dec/time.c were present in 2.6.17. However,
> the subsequent patches suggested in the message thread were not present in
> the version of the 2.6.17 kernel I checked. We'd like to ask if the patches
> suggested in the message thread have been observed to influence performance
> numbers obtained by other Linux system developers for Quad-core Broadcom
> 1480 systems? If so, do the Linux-Mips developers suggest that we apply the
> patches suggested in the message thread for our Broadcom 1480 MIPS specific
> Linux 2.6.17 system implementation?
The patch never went in.
I'm currently turning the entire time code upside down which will also solve
this issue.
Ralf
prev parent reply other threads:[~2007-06-21 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 16:07 Question About Timers for Performance Analysis on BCM1480/1250 Systems Gary Smith
2007-06-19 16:07 ` Gary Smith
2007-06-21 17:06 ` Ralf Baechle [this message]
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=20070621170601.GD21938@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=gary.smith@3phoenix.com \
--cc=linux-mips@linux-mips.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