From: Andi Kleen <andi@firstfloor.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Robert Hancock <hancockr@shaw.ca>,
Christian Kujau <lists@nerdbynature.de>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH] common implementation of iterative div/mod
Date: Wed, 14 May 2008 10:33:01 +0200 [thread overview]
Message-ID: <482AA3BD.1030600@firstfloor.org> (raw)
In-Reply-To: <482A95BB.1000001@goop.org>
Jeremy Fitzhardinge wrote:
>
> arch/x86/vdso/vclock_gettime.c has its own copies of other kernel
> functions which it can't directly call. We could add
> timespec_add_ns()/iter_div_u64_rem() to that list, though its pretty
> hacky. Could we link lib/div64.o into the vdso?
You would need to annotate it and have a separate object file for the
different sections. Also it would need to be compiled PIC.
Inlining is better.
-Andi
next prev parent reply other threads:[~2008-05-14 8:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.QTbvQYXhEm5VNP5dvkl5JG7NHYQ@ifi.uio.no>
2008-05-04 17:35 ` undefined reference to __udivdi3 (gcc-4.3) Robert Hancock
2008-05-04 22:19 ` Segher Boessenkool
2008-05-07 9:29 ` Jeremy Fitzhardinge
2008-05-08 15:16 ` [PATCH] common implementation of iterative div/mod Jeremy Fitzhardinge
2008-05-08 20:26 ` Andrew Morton
2008-05-08 22:00 ` Jeremy Fitzhardinge
2008-05-08 20:52 ` Segher Boessenkool
2008-05-08 21:57 ` Jeremy Fitzhardinge
2008-05-09 11:45 ` Christian Kujau
2008-05-14 6:46 ` Andrew Morton
2008-05-14 7:33 ` Jeremy Fitzhardinge
2008-05-14 8:33 ` Andi Kleen [this message]
2008-05-14 9:55 ` Jeremy Fitzhardinge
2008-05-14 10:50 ` Andi Kleen
2008-05-14 10:52 ` Jeremy Fitzhardinge
2008-05-14 11:21 ` Andi Kleen
2008-05-14 12:58 ` Jeremy Fitzhardinge
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=482AA3BD.1030600@firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=jeremy@goop.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mingo@elte.hu \
--cc=segher@kernel.crashing.org \
--cc=tglx@linutronix.de \
/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.