* sysenter on x86
@ 2003-04-12 13:54 Felix von Leitner
2003-04-12 14:15 ` Arjan van de Ven
0 siblings, 1 reply; 3+ messages in thread
From: Felix von Leitner @ 2003-04-12 13:54 UTC (permalink / raw)
To: linux-kernel
I just added sysenter support for linux-2.5 on x86 to the diet libc, but
I noted that the original patch said user space should jump to
0xfffff000, which segfaults. Jumping to 0xffffe000 works.
I suggest adding a comment somewhere in the kernel about the proper
calling convention, because the glibc code is frankly not readable in
this regard.
Also, I suggest adding this interface to kernel 2.4 to easy binary
compatibility.
Felix
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sysenter on x86
2003-04-12 13:54 sysenter on x86 Felix von Leitner
@ 2003-04-12 14:15 ` Arjan van de Ven
2003-04-14 18:14 ` H. Peter Anvin
0 siblings, 1 reply; 3+ messages in thread
From: Arjan van de Ven @ 2003-04-12 14:15 UTC (permalink / raw)
To: Felix von Leitner; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Sat, 2003-04-12 at 15:54, Felix von Leitner wrote:
> I just added sysenter support for linux-2.5 on x86 to the diet libc, but
> I noted that the original patch said user space should jump to
> 0xfffff000, which segfaults. Jumping to 0xffffe000 works.
>
> I suggest adding a comment somewhere in the kernel about the proper
> calling convention, because the glibc code is frankly not readable in
> this regard.
you HAVE to use the location as specified with the AT_SYSINFO elf flag.
The kernel is free to move this address around between builds, as long
as AT_SYSINFO gives the address for the location.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sysenter on x86
2003-04-12 14:15 ` Arjan van de Ven
@ 2003-04-14 18:14 ` H. Peter Anvin
0 siblings, 0 replies; 3+ messages in thread
From: H. Peter Anvin @ 2003-04-14 18:14 UTC (permalink / raw)
To: linux-kernel
Followup to: <1050156926.1449.2.camel@laptop.fenrus.com>
By author: Arjan van de Ven <arjanv@redhat.com>
In newsgroup: linux.dev.kernel
>
>
> --=-EFK+Hzuvs0Z6BUNjBVGk
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
>
> On Sat, 2003-04-12 at 15:54, Felix von Leitner wrote:
> > I just added sysenter support for linux-2.5 on x86 to the diet libc, but
> > I noted that the original patch said user space should jump to
> > 0xfffff000, which segfaults. Jumping to 0xffffe000 works.
> >=20
> > I suggest adding a comment somewhere in the kernel about the proper
> > calling convention, because the glibc code is frankly not readable in
> > this regard.
>
> you HAVE to use the location as specified with the AT_SYSINFO elf flag.
> The kernel is free to move this address around between builds, as long
> as AT_SYSINFO gives the address for the location.
>
... which quite frankly kind of bites :(
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-04-14 18:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-12 13:54 sysenter on x86 Felix von Leitner
2003-04-12 14:15 ` Arjan van de Ven
2003-04-14 18:14 ` H. Peter Anvin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).