From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: 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>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] common implementation of iterative div/mod
Date: Wed, 14 May 2008 08:33:15 +0100 [thread overview]
Message-ID: <482A95BB.1000001@goop.org> (raw)
In-Reply-To: <20080513234627.30476c20.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 08 May 2008 16:16:41 +0100 Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>
>> We have a few instances of the open-coded iterative div/mod loop, used
>> when we don't expcet the dividend to be much bigger than the divisor.
>> Unfortunately modern gcc's have the tendency to strength "reduce" this
>> into a full mod operation, which isn't necessarily any faster, and
>> even if it were, doesn't exist if gcc implements it in libgcc.
>>
>> The workaround is to put a dummy asm statement in the loop to prevent
>> gcc from performing the transformation.
>>
>> This patch creates a single implementation of this loop, and uses it
>> to replace the open-coded versions I know about.
>>
>
> Believe it or not, this patch causes one of my test machines to fail to
> find its disk.
>
> good dmesg: http://userweb.kernel.org/~akpm/dmesg-t61p.txt
> bad dmesg: http://userweb.kernel.org/~akpm/dmesg-t61p-dead.txt
> config: http://userweb.kernel.org/~akpm/config-t61p.txt
Uh, OK. Do your other test machines work with it? Are there any
relevant config differences (x86-64 vs 32?).
Hm, it's not that it can't find its disk, I think it's this:
init[1]: segfault at ffffffffff7008d2 ip ffffffffff7008d2 sp 7fff86e67488 error 14
init[1]: segfault at ffffffffff7008d2 ip 311ac07628 sp 7fff86e66cb0 error 4 in libgcc_s-4.1.2-20070925.so.1[311ac00000+d000]
Is it that the vsyscall page is trying to call into the kernel?
notrace static noinline int do_realtime(struct timespec *ts)
{
unsigned long seq, ns;
do {
seq = read_seqbegin(>od->lock);
ts->tv_sec = gtod->wall_time_sec;
ts->tv_nsec = gtod->wall_time_nsec;
ns = vgetns();
} while (unlikely(read_seqretry(>od->lock, seq)));
timespec_add_ns(ts, ns);
return 0;
}
timespec_add_ns() used to be entirely inlined, but now it contains the
call to iter_div_u64_rem().
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?
J
next prev parent reply other threads:[~2008-05-14 7: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 [this message]
2008-05-14 8:33 ` Andi Kleen
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=482A95BB.1000001@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hancockr@shaw.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox