From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] lfetch.fault [NULL] speedup
Date: Sat, 26 Mar 2005 00:47:30 +0000 [thread overview]
Message-ID: <32451.1111798050@ocs3.ocs.com.au> (raw)
In-Reply-To: <16964.41018.199600.952301@napali.hpl.hp.com>
On Fri, 25 Mar 2005 15:35:22 -0800,
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>=== arch/ia64/kernel/ivt.S 1.34 vs edited ==>--- 1.34/arch/ia64/kernel/ivt.S 2005-03-24 14:06:40 -08:00
>+++ edited/arch/ia64/kernel/ivt.S 2005-03-25 15:13:07 -08:00
>@@ -1235,6 +1235,25 @@
> // 0x5600 Entry 26 (size 16 bundles) Nat Consumption (11,23,37,50)
> ENTRY(nat_consumption)
> DBG_FAULT(26)
>+
>+ mov r16=cr.ipsr
>+ mov r17=cr.isr
>+ mov r31=pr // save PR
>+ cmp.ne p6=r0,r0 // p6 = FALSE
>+ ;;
>+ and r18=0xf,r17 // r18 = cr.ipsr.code{3:0}
>+ tbit.z.or p6,p0=r17,IA64_ISR_NA_BIT
>+ ;;
>+ cmp.ne.or p6,p0=IA64_ISR_CODE_LFETCH,r18
Why use tbit.*.or and cmp.*.or? The normal form works just as well in
this case (r17 cannot be NaT) and the normal form does not need cmp.ne
p6=r0,r0 first.
next prev parent reply other threads:[~2005-03-26 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 23:35 [patch] lfetch.fault [NULL] speedup David Mosberger
2005-03-26 0:47 ` Keith Owens [this message]
2005-03-26 0:59 ` David Mosberger
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=32451.1111798050@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--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