public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] new ia64 patch (relative to 2.5.69)
Date: Thu, 22 May 2003 01:33:16 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705980@msgid-missing> (raw)

An updated 2.5.69 patch is now available at:

 ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/v2.5/

in linux-2.5.69-ia64-030521.diff.gz.

Warning: I pushed a patch of the same name earlier today, just to find
that core-dumps were broken.  I fixed that now and updated the patch.
If you don't have the latest version, the attached patch will be
missing.

This kernel should be fairly stable (at least it has been for me).

I'm planning to apply a patch next a patch by Rohit Seth and some
other folks at Intel.  This patch restructures struct pt_regs and
optimizes the syscall path not to save/restore scratch registers.
Most definitely non-trivial stuff and will need a lot of testing.  But
if things break unexpectedly, we can easily fall back to the current
snapshot.

	--david

diff -Nru a/arch/ia64/kernel/unwind.c b/arch/ia64/kernel/unwind.c
--- a/arch/ia64/kernel/unwind.c	Wed May 21 18:24:17 2003
+++ b/arch/ia64/kernel/unwind.c	Wed May 21 18:24:17 2003
@@ -239,7 +239,10 @@
 	if (!info->pt) {
 		/* This should not happen with valid unwind info.  */
 		UNW_DPRINT(0, "unwind.%s: bad unwind info: resetting info->pt\n", __FUNCTION__);
-		info->pt = info->sp - 16;
+		if (info->flags & UNW_FLAG_INTERRUPT_FRAME)
+			info->pt = (unsigned long) ((struct pt_regs *) info->psp - 1);
+		else
+			info->pt = info->sp - 16;
 	}
 	UNW_DPRINT(3, "unwind.%s: sp 0x%lx pt 0x%lx\n", __FUNCTION__, info->sp, info->pt);
 	return (struct pt_regs *) info->pt;


             reply	other threads:[~2003-05-22  1:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22  1:33 David Mosberger [this message]
2003-05-22 15:39 ` [Linux-ia64] new ia64 patch (relative to 2.5.69) Luck, Tony

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-105590723705980@msgid-missing \
    --to=davidm@napali.hpl.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