From: Richard Henderson <rth7680@gmail.com>
To: Matt Turner <mattst88@gmail.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Carlos O'Donell <carlos@systemhalted.org>,
debian-alpha@lists.debian.org, debian-glibc@lists.debian.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
linux-alpha@vger.kernel.org
Subject: Re: Help on memchr() EGLIBC assembly code
Date: Wed, 15 Jul 2009 12:48:02 -0700 [thread overview]
Message-ID: <4A5E3272.4040904@gmail.com> (raw)
In-Reply-To: <b4198de60907131516t384446e6na6cf15e7ebb1fc83@mail.gmail.com>
On 07/13/2009 03:16 PM, Matt Turner forwarded:
>>>> The problem is that the memchr() function on alpha uses prefetch, which
>>>> can cause a page boundary to be crossed, while the standards (POSIX and
>>>> C99) says it should stop when a match is found.
That's not supposed to matter -- faults from prefetch are supposed to be
ignored; see do_page_fault:
/* As of EV6, a load into $31/$f31 is a prefetch, and never faults
(or is suppressed by the PALcode). Support that for older CPUs
by ignoring such an instruction. */
if (cause == 0) {
unsigned int insn;
__get_user(insn, (unsigned int __user *)regs->pc);
if ((insn >> 21 & 0x1f) == 0x1f &&
/* ldq ldl ldt lds ldg ldf ldwu ldbu */
(1ul << (insn >> 26) & 0x30f00001400ul)) {
regs->pc += 4;
return;
}
}
Can you figure out why that kernel code isn't working? I no longer have
working alpha hw...
r~
next prev parent reply other threads:[~2009-07-15 19:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090713173104.GA13883@hall.aurel32.net>
[not found] ` <119aab440907131124r3fd333d3n967cdde2cf3c2e1b@mail.gmail.com>
[not found] ` <20090713211723.GE10110@hall.aurel32.net>
2009-07-13 22:16 ` Help on memchr() EGLIBC assembly code Matt Turner
2009-07-13 22:24 ` Aurelien Jarno
2009-07-15 19:48 ` Richard Henderson [this message]
2009-07-19 14:29 ` Aurelien Jarno
2009-07-26 23:45 ` Aurelien Jarno
2009-07-27 9:29 ` Aurelien Jarno
2009-07-30 0:24 ` Richard Henderson
2009-07-30 16:29 ` Aurelien Jarno
2009-07-31 23:25 ` Richard Henderson
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=4A5E3272.4040904@gmail.com \
--to=rth7680@gmail.com \
--cc=aurelien@aurel32.net \
--cc=carlos@systemhalted.org \
--cc=debian-alpha@lists.debian.org \
--cc=debian-glibc@lists.debian.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.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 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.