From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Roland McGrath <roland@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Various x86 syscall mechanisms
Date: Sat, 21 Jun 2008 09:51:49 -0700 [thread overview]
Message-ID: <485D31A5.80001@zytor.com> (raw)
In-Reply-To: <87bq1uyjgi.fsf@basil.nowhere.org>
Andi Kleen wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>
>> There is no reason we couldn't do syscall for 32-bit native, but the
>> only processor that would benefit would be K7, and that's far enough
>
> K6 actually. K7 has sysenter AFAIK. The K6 syscall was also slightly different
> and would need special case code.
Sorry, yes, K6. Even more historic.
-hpa
next prev parent reply other threads:[~2008-06-21 16:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 22:00 Various x86 syscall mechanisms Jeremy Fitzhardinge
2008-06-20 23:39 ` Roland McGrath
2008-06-27 21:45 ` Jeremy Fitzhardinge
2008-06-27 21:52 ` Roland McGrath
2008-06-28 5:00 ` Andi Kleen
2008-06-30 0:07 ` Bill Davidsen
2008-06-21 0:27 ` H. Peter Anvin
2008-06-21 2:00 ` Jeremy Fitzhardinge
2008-06-21 14:02 ` Andi Kleen
2008-06-21 16:51 ` H. Peter Anvin [this message]
2008-07-01 12:06 ` Jan Engelhardt
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=485D31A5.80001@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.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