From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Kenerl Entry/Exit optimization patch for your bk tree
Date: Wed, 30 Jul 2003 22:13:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105960328604158@msgid-missing> (raw)
On Tuesday 10 June 2003 3:26 pm, Seth, Rohit wrote:
> Please find attached the Kernel entry/exit patch against your latest
> 2.4.20-bk tree. This is derived from (now settled) 2.5 kernel patch
> that David has in his tree. One major change from 2.5 is that
> ia64_execve still has the same old hack to support IA-32 apps (that is
> currently broken on 2.5).
>
> This patch also has the support for 16-bytes instructions that are
> mentioned in SDM2.1
I applied this patch to the 2.4 tree, with the following edit:
diff -Nru a/arch/ia64/kernel/entry.h b/arch/ia64/kernel/entry.h
--- a/arch/ia64/kernel/entry.h Wed Jul 30 16:51:44 2003
+++ b/arch/ia64/kernel/entry.h Wed Jul 30 16:51:44 2003
@@ -14,7 +14,7 @@
#define SW(f) (IA64_SWITCH_STACK_##f##_OFFSET)
#define PT_REGS_SAVES(off) \
- .unwabi @svr4, 'i'; \
+ .unwabi 3, 'i'; \
.fframe IA64_PT_REGS_SIZE+16+(off); \
.spillsp rp, PT(CR_IIP)+16+(off); \
.spillsp ar.pfs, PT(CR_IFS)+16+(off); \
reply other threads:[~2003-07-30 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105960328604158@msgid-missing \
--to=bjorn.helgaas@hp.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