From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: GLIBC IA64 HP_TIMING fixes for SMP systems with unsynchronized
Date: Thu, 03 Jun 2004 21:52:56 +0000 [thread overview]
Message-ID: <je1xkwe2br.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0406031313420.32412@server.home>
Christoph Lameter <christoph@lameter.com> writes:
> On Thu, 3 Jun 2004, Andreas Schwab wrote:
>
>> That needs to be libmemusage-sysdep_routines.
>
>>
>> > + int fd = open ("/proc/sal/itc_drift", O_RDONLY);
>>
>> This is Linux-specific, isn't it? Thus it belongs under
>> sysdeps/.../linux/ia64.
>
> Quite a bit of the code is linux specific. Do I leave the generic code
> broken?
The generic code has to be adjusted for the specific target anyway, if and
when someone ports it to a non-Linux system.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-06-03 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 20:28 GLIBC IA64 HP_TIMING fixes for SMP systems with unsynchronized ITC Christoph Lameter
2004-06-03 20:51 ` GLIBC IA64 HP_TIMING fixes for SMP systems with unsynchronized Andreas Schwab
2004-06-03 21:21 ` Christoph Lameter
2004-06-03 21:52 ` Andreas Schwab [this message]
2004-06-04 6:04 ` GLIBC IA64 HP_TIMING fixes for SMP systems with unsynchronized ITC David Mosberger
2004-06-04 6:12 ` GLIBC IA64 HP_TIMING fixes for SMP systems with unsynchronized Ulrich Drepper
2004-06-04 6:58 ` David Mosberger
2004-06-04 14:29 ` Christoph Lameter
2004-06-04 15:06 ` Christoph Lameter
2004-06-04 22:06 ` GLIBC IA64 HP_TIMING fixes for SMP systems with unsynchronized ITC Peter Chubb
2004-06-04 22:25 ` Luck, Tony
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=je1xkwe2br.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox