From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Gall <tom_gall@vnet.ibm.com>
Cc: linuxppc64-dev@ozlabs.org, munroesj@us.ibm.com,
libc-alpha@sources.redhat.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] glibc vDSO bits for ppc/ppc64 update
Date: Sat, 12 Nov 2005 09:13:28 +1100 [thread overview]
Message-ID: <1131747209.24637.255.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.64.0511111555580.6838@triton>
> Additional hp_timer_t is now declared as unsigned long long int
> to match up with benh's get_tbfreq on 32 bit ppc. (ppc64 is already
> 64 bit)
I'm not sure having hp_timer_t be 64 bits on 32 bits libraries is the
right thing to do. I suppose it's a matter of performances tradeoff. The
fact that the vDSO __kernel_get_tbfreq() returns a long long doesn't
force you to use a long long hp_timer_t, the vDSO doesn't have to return
a value of type hp_timer_t :)
I did that on the vDSO to avoid having to change the vDSO interface if
we ever have to deal with >4Ghz time sources.
Ben.
next prev parent reply other threads:[~2005-11-11 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 22:11 [PATCH] glibc vDSO bits for ppc/ppc64 update Tom Gall
2005-11-11 22:13 ` Benjamin Herrenschmidt [this message]
2005-11-11 22:32 ` Steve Munroe
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=1131747209.24637.255.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=munroesj@us.ibm.com \
--cc=tom_gall@vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).