From: Andi Kleen <ak@suse.de>
To: Terje Eggestad <terje.eggestad@scali.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Q] was the SYSENTER/SYSCALL fast system calls completed or discared in the end??
Date: 22 Nov 2001 16:26:15 +0100 [thread overview]
Message-ID: <p73snb6x1wo.fsf@amdsim2.suse.de> (raw)
In-Reply-To: <1006184327.19902.2.camel@pc-16.office.scali.no.suse.lists.linux.kernel> <20011121225402.A175@elf.ucw.cz.suse.lists.linux.kernel> <1006440069.22598.4.camel@pc-16.office.scali.no.suse.lists.linux.kernel>
In-Reply-To: Terje Eggestad's message of "22 Nov 2001 15:46:31 +0100"
Terje Eggestad <terje.eggestad@scali.no> writes:
> ons, 2001-11-21 kl. 22:54 skrev Pavel Machek:
> >
> > On Mon 19-11-01 16:38:45, Terje Eggestad wrote:
> > > subject says it all....
> > >
> > > I remember there was a discussion and a patch floating around that
> > > implemented SYSCALL/SYSRET, just want to know what happened to it....
> >
> > discarded
>
> Because there was no perf benefit or because the patch was in poor
> quality?
The x86-64 port uses SYSCALL/SYSRET as the native call method for 64bit
programs.
Before x86-64 it turned out that SYSCALL is not really usable because
of some builtin limitations (which are fixed in x86-64). This is only
a problem for the K6, K7 should have support for SYSENTER/SYSEXIT (the
Intel equivalent), which seems to be better designed. There is a patch
to use SYSENTER/SYSEXIT.
-Andi
next parent reply other threads:[~2001-11-22 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1006184327.19902.2.camel@pc-16.office.scali.no.suse.lists.linux.kernel>
[not found] ` <20011121225402.A175@elf.ucw.cz.suse.lists.linux.kernel>
[not found] ` <1006440069.22598.4.camel@pc-16.office.scali.no.suse.lists.linux.kernel>
2001-11-22 15:26 ` Andi Kleen [this message]
2001-11-23 13:54 ` Terje Eggestad
2001-11-23 13:57 ` Andi Kleen
2001-11-19 15:38 Terje Eggestad
2001-11-21 21:54 ` Pavel Machek
2001-11-22 14:41 ` Terje Eggestad
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=p73snb6x1wo.fsf@amdsim2.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=terje.eggestad@scali.no \
/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
all inboxes | Powered by JetHome®