From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [patch 3/6] prefetch bottom of kernel rbs stack at syscall exit path
Date: Tue, 31 Jan 2006 09:13:24 +0000 [thread overview]
Message-ID: <200601310913.k0V9DWg13193@unix-os.sc.intel.com> (raw)
Kernel knows where the register backing store is corresponding
to user dirty stack registers. Prefetch those cache lines as
early as possible in ia64_leave_syscall path.
Signed-off-by: Ken Chen <kenneth.w.chen@intel.com>
--- ./arch/ia64/kernel/entry.S.orig 2006-01-02 19:21:10.000000000 -0800
+++ ./arch/ia64/kernel/entry.S 2006-01-30 13:26:41.161634409 -0800
@@ -715,10 +715,11 @@ ENTRY(ia64_leave_syscall)
;;
(p6) ld4 r31=[r18] // load current_thread_info()->flags
ld8 r19=[r2],PT(B6)-PT(LOADRS) // load ar.rsc value for "loadrs"
- nop.i 0
+ add r17=IA64_RBS_OFFSET,r13
;;
mov r16=ar.bsp // M2 get existing backing store pointer
ld8 r18=[r2],PT(R9)-PT(B6) // load b6
+ shr r22=r19,16
(p6) and r15=TIF_WORK_MASK,r31 // any work other than TIF_SYSCALL_TRACE?
;;
ld8 r23=[r3],PT(R11)-PT(AR_BSPSTORE) // load ar.bspstore (may be garbage)
@@ -729,6 +730,12 @@ ENTRY(ia64_leave_syscall)
ld8 r9=[r2],PT(CR_IPSR)-PT(R9)
ld8 r11=[r3],PT(CR_IIP)-PT(R11)
(pNonSys) break 0 // bug check: we shouldn't be here if pNonSys is TRUE!
+1:
+(pUStk) lfetch [r17],128
+ add r22=-128,r22
+ ;;
+(pUStk) cmp.gt.unc p7,p0=r22,r0
+(p7) br.dptk.few 1b
;;
invala // M0|1 invalidate ALAT
rsm psr.i | psr.ic // M2 turn off interrupts and interruption collection
next reply other threads:[~2006-01-31 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 9:13 Chen, Kenneth W [this message]
2006-01-31 17:44 ` [patch 3/6] prefetch bottom of kernel rbs stack at syscall exit path David Mosberger-Tang
2006-01-31 19:27 ` Chen, Kenneth W
2006-02-07 2:56 ` Chen, Kenneth W
2006-02-07 21:19 ` David Mosberger-Tang
2006-02-07 21:27 ` Chen, Kenneth W
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=200601310913.k0V9DWg13193@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