From: Joe Korty <joe.korty@ccur.com>
To: Dan Aloni <da-x@monatomic.org>
Cc: Keith Owens <kaos@sgi.com>, Nathan Scott <nathans@sgi.com>,
kdb@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Announce: kdb v4.4 is available for kernel 2.6.16
Date: Sat, 1 Apr 2006 18:43:13 -0500 [thread overview]
Message-ID: <20060401234313.GA22482@tsunami.ccur.com> (raw)
In-Reply-To: <20060401170430.GA14715@localdomain>
On Sat, Apr 01, 2006 at 08:04:30PM +0300, Dan Aloni wrote:
> > Current versions are :-
> >
> > kdb-v4.4-2.6.16-common-1.bz2
> > kdb-v4.4-2.6.16-i386-1.bz2
> > kdb-v4.4-2.6.16-ia64-1.bz2
>
> Thanks for this new version, however I'm looking forward to see
> kdb maintained also for the x86_64 architecture. Currently I have
> got as far as forward-porting it to a level where it "works" except
> for one annoying issue where setjmp/longjmp looks to be broken:
Problem is due to the mixed C/asm implementation of setjmp/longjmp.
Replace that with one written entirely in assemply and it will work.
Here's mine:
/* setjmp / longjmp for the kernel.
* Inspired by the glibc version.
*/
.text
.globl __kernel_setjmp
.p2align 4
__kernel_setjmp:
movq %rbx,0x0(%rdi)
movq %rbp,0x8(%rdi)
movq %r12,0x10(%rdi)
movq %r13,0x18(%rdi)
movq %r14,0x20(%rdi)
movq %r15,0x28(%rdi)
leaq 0x8(%rsp),%rdx
movq %rdx,0x30(%rdi)
movq (%rsp),%rax
movq %rax,0x38(%rdi)
xorq %rax,%rax
ret
.globl __kernel_longjmp
__kernel_longjmp:
movq 0x0(%rdi),%rbx
movq 0x8(%rdi),%rbp
movq 0x10(%rdi),%r12
movq 0x18(%rdi),%r13
movq 0x20(%rdi),%r14
movq 0x28(%rdi),%r15
test %esi,%esi
mov $1,%eax
cmove %eax,%esi
mov %esi,%eax
movq 0x38(%rdi),%rdx
movq 0x30(%rdi),%rsp
jmpq *%rdx
next prev parent reply other threads:[~2006-04-01 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 5:59 Keith Owens
2006-03-24 6:21 ` Keith Owens
2006-04-01 17:04 ` Dan Aloni
2006-04-01 20:37 ` Hugh Dickins
2006-04-01 23:43 ` Joe Korty [this message]
2006-04-02 10:23 ` Dan Aloni
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=20060401234313.GA22482@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=da-x@monatomic.org \
--cc=kaos@sgi.com \
--cc=kdb@oss.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/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
Powered by JetHome