From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Patch 1/1] 4-level page tables v4.
Date: Thu, 10 Nov 2005 23:54:37 +0000 [thread overview]
Message-ID: <200511102354.jAANsbg21726@unix-os.sc.intel.com> (raw)
In-Reply-To: <20051110161915.GA3630@lnx-holt.americas.sgi.com>
Robin Holt wrote on Thursday, November 10, 2005 8:19 AM
> --- linux-2.6.orig/arch/ia64/kernel/ivt.S 2005-11-10 06:49:03.399350630 -0600
> +++ linux-2.6/arch/ia64/kernel/ivt.S 2005-11-10 10:06:49.272116003 -0600
> @@ -114,7 +114,7 @@ ENTRY(vhpt_miss)
> @@ -192,14 +207,23 @@ ENTRY(vhpt_miss)
> * between reading the pagetable and the "itc". If so, flush the entry we
> * inserted and retry.
> */
> - ld8 r25=[r21] // read L3 PTE again
> - ld8 r26=[r17] // read L2 entry again
> + ld8 r26=[r30] // read L3 entry again
> +#ifdef CONFIG_PGTABLE_4
> + ld8 r30=[r28] // read L2 entry again
> ;;
> - cmp.ne p6,p7=r26,r20 // did L2 entry change
> + cmp.ne p6,p7=r30,r29 // did L2 entry change
> mov r27=PAGE_SHIFT<<2
> ;;
> +(p7) cmp.ne.or.andcm p6,p7=r26,r20 // did L3 entry change
> +#else
You can shave off one cycle here by using parallel cmp. Initialize
p6,p7 in the load bundle. Something like:
+#ifdef CONFIG_PGTABLE_4
+ ld8 r30=[r28] // read L2 entry again
+ cmp.ne p6,p7=r0,r0
;;
- cmp.ne p6,p7=r26,r20 // did L2 entry change
+ cmp.ne.or.andcm p6,p7=r30,r29
+ cmp.ne.or.andcm p6,p7=r26,r20
mov r27=PAGE_SHIFT<<2
+#else
next prev parent reply other threads:[~2005-11-10 23:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 16:19 [Patch 1/1] 4-level page tables v4 Robin Holt
2005-11-10 21:49 ` Luck, Tony
2005-11-10 22:38 ` Robin Holt
2005-11-10 23:03 ` Luck, Tony
2005-11-10 23:30 ` Chen, Kenneth W
2005-11-10 23:54 ` Chen, Kenneth W [this message]
2005-11-11 0:13 ` Chen, Kenneth W
2005-11-11 0:24 ` Jack Steiner
2005-11-11 0:58 ` Chen, Kenneth W
2005-11-11 1:19 ` Robin Holt
2005-11-11 2:06 ` Chen, Kenneth W
2005-11-11 2:11 ` Robin Holt
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=200511102354.jAANsbg21726@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.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